[jira] [Updated] (FLINK-33156) Remove flakiness from tests in OperatorStateBackendTest.java
[
https://issues.apache.org/jira/browse/FLINK-33156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asha Boyapati updated FLINK-33156:
--
Description:
This issue is similar to:
https://issues.apache.org/jira/browse/FLINK-32963
We are proposing to make the following tests stable:
{quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
The tests are currently flaky because the order of elements returned by
iterators is non-deterministic.
The following PR fixes the flaky test by making them independent of the order
of elements returned by the iterator:
https://github.com/apache/flink/pull/23464
We detected this using the NonDex tool using the following commands:
{quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
Please see the following Continuous Integration log that shows the flakiness:
https://github.com/asha-boyapati/flink/actions/runs/6193757385
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
https://github.com/asha-boyapati/flink/actions/runs/619409
was:
This issue is similar to:
https://issues.apache.org/jira/browse/FLINK-32963
We are proposing to make the following tests stable:
{quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
The tests are currently flaky because the order of elements returned by
iterators is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
https://github.com/apache/flink/pull/23464
We detected this using the NonDex tool using the following commands:
{quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
Please see the following Continuous Integration log that shows the flakiness:
https://github.com/asha-boyapati/flink/actions/runs/6193757385
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
https://github.com/asha-boyapati/flink/actions/runs/619409
> Remove flakiness from tests in OperatorStateBackendTest.java
>
>
> Key: FLINK-33156
> URL: https://issues.apache.org/jira/browse/FLINK-33156
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
>Affects Versions: 1.17.1
>Reporter: Asha Boyapati
>Priority: Minor
> Fix For: 1.17.1
>
>
> This issue is similar to:
> https://issues.apache.org/jira/browse/FLINK-32963
> We are proposing to make the following tests stable:
> {quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
> org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
> The tests are currently flaky because the order of elements returned by
> iterators is non-deterministic.
> The following PR fixes the flaky test by making them independent of the order
> of elements returned by the iterator:
> https://github.com/apache/flink/pull/23464
> We detected this using the NonDex tool using the following commands:
> {quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
> -DnondexRuns=10
> -Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
> mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
> -DnondexRuns=10
> -Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
> Please see the following Continuous Integration log that shows the flakiness:
> https://github.com/asha-boyapati/flink/actions/runs/6193757385
> Please see the following Continuous Integration log that shows that the
> flakiness is fixed by this change:
> https://github.com/asha-boyapati/flink/actions/runs/619409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-33156) Remove flakiness from tests in OperatorStateBackendTest.java
[
https://issues.apache.org/jira/browse/FLINK-33156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asha Boyapati updated FLINK-33156:
--
Description:
This issue is similar to:
https://issues.apache.org/jira/browse/FLINK-32963
We are proposing to make the following tests stable:
{quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
The tests are currently flaky because the order of elements returned by
iterators is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
https://github.com/apache/flink/pull/23464
We detected this using the NonDex tool using the following commands:
{quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
Please see the following Continuous Integration log that shows the flakiness:
https://github.com/asha-boyapati/flink/actions/runs/6193757385
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
https://github.com/asha-boyapati/flink/actions/runs/619409
was:
This issue is similar to:
https://issues.apache.org/jira/browse/FLINK-32963
We are proposing to make the following tests stable:
{quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
The tests are currently flaky because the order of elements returned by
iterators is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
https://github.com/asha-boyapati/flink/pull/2
We detected this using the NonDex tool using the following commands:
{quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
Please see the following Continuous Integration log that shows the flakiness:
https://github.com/asha-boyapati/flink/actions/runs/6193757385
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
https://github.com/asha-boyapati/flink/actions/runs/619409
> Remove flakiness from tests in OperatorStateBackendTest.java
>
>
> Key: FLINK-33156
> URL: https://issues.apache.org/jira/browse/FLINK-33156
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
>Affects Versions: 1.17.1
>Reporter: Asha Boyapati
>Priority: Minor
> Fix For: 1.17.1
>
>
> This issue is similar to:
> https://issues.apache.org/jira/browse/FLINK-32963
> We are proposing to make the following tests stable:
> {quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
> org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
> The tests are currently flaky because the order of elements returned by
> iterators is non-deterministic.
> The following PR fixes the flaky test by making it independent of the order
> of elements returned by the iterator:
> https://github.com/apache/flink/pull/23464
> We detected this using the NonDex tool using the following commands:
> {quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
> -DnondexRuns=10
> -Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
> mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
> -DnondexRuns=10
> -Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
> Please see the following Continuous Integration log that shows the flakiness:
> https://github.com/asha-boyapati/flink/actions/runs/6193757385
> Please see the following Continuous Integration log that shows that the
> flakiness is fixed by this change:
> https://github.com/asha-boyapati/flink/actions/runs/619409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-33156) Remove flakiness from tests in OperatorStateBackendTest.java
Asha Boyapati created FLINK-33156:
-
Summary: Remove flakiness from tests in
OperatorStateBackendTest.java
Key: FLINK-33156
URL: https://issues.apache.org/jira/browse/FLINK-33156
Project: Flink
Issue Type: Bug
Components: Runtime / State Backends
Affects Versions: 1.17.1
Reporter: Asha Boyapati
Fix For: 1.17.1
This issue is similar to:
https://issues.apache.org/jira/browse/FLINK-32963
We are proposing to make the following tests stable:
{quote}org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
The tests are currently flaky because the order of elements returned by
iterators is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
https://github.com/asha-boyapati/flink/pull/2
We detected this using the NonDex tool using the following commands:
{quote}mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreSync
mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.OperatorStateBackendTest#testSnapshotRestoreAsync{quote}
Please see the following Continuous Integration log that shows the flakiness:
https://github.com/asha-boyapati/flink/actions/runs/6193757385
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
https://github.com/asha-boyapati/flink/actions/runs/619409
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-32963) Make the test "testKeyedMapStateStateMigration" stable
[
https://issues.apache.org/jira/browse/FLINK-32963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asha Boyapati updated FLINK-32963:
--
Description:
We are proposing to make the following test stable:
{{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
The test is currently flaky because the order of elements returned by the
iterator is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
[https://github.com/apache/flink/pull/23298]
We detected this using the NonDex tool using the following command:
{{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
Please see the following Continuous Integration log that shows the flakiness:
[https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
[https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
was:
We are proposing to make the following test stable:
{{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
The test is currently flaky because the order of elements returned by the
iterator is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
[https://github.com/apache/flink/pull/23298|http://example.com]
We detected this using the NonDex tool using the following command:
{{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
Please see the following Continuous Integration log that shows the flakiness:
[https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
[https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
> Make the test "testKeyedMapStateStateMigration" stable
> --
>
> Key: FLINK-32963
> URL: https://issues.apache.org/jira/browse/FLINK-32963
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
>Affects Versions: 1.17.1
>Reporter: Asha Boyapati
>Priority: Minor
> Labels: pull-request-available
>
> We are proposing to make the following test stable:
> {{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
> The test is currently flaky because the order of elements returned by the
> iterator is non-deterministic.
> The following PR fixes the flaky test by making it independent of the order
> of elements returned by the iterator:
> [https://github.com/apache/flink/pull/23298]
> We detected this using the NonDex tool using the following command:
> {{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
> -DnondexRuns=10
> -Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
> Please see the following Continuous Integration log that shows the flakiness:
> [https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
> Please see the following Continuous Integration log that shows that the
> flakiness is fixed by this change:
> [https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-32963) Make the test "testKeyedMapStateStateMigration" stable
[
https://issues.apache.org/jira/browse/FLINK-32963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Asha Boyapati updated FLINK-32963:
--
Description:
We are proposing to make the following test stable:
{{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
The test is currently flaky because the order of elements returned by the
iterator is non-deterministic.
The following PR fixes the flaky test by making it independent of the order of
elements returned by the iterator:
[https://github.com/apache/flink/pull/23298|http://example.com]
We detected this using the NonDex tool using the following command:
{{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
Please see the following Continuous Integration log that shows the flakiness:
[https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
[https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
was:
We are proposing to make the following test stable:
{{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
The test is currently flaky because the order of elements returned by the
iterator is non-deterministic.
The following tentative PR fixes the flaky test by making it independent of the
order of elements returned by the iterator:
[https://github.com/asha-boyapati/flink/pull/1|http://example.com|http://example.com]
We detected this using the NonDex tool using the following command:
{{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
Please see the following Continuous Integration log that shows the flakiness:
[https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
[https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
> Make the test "testKeyedMapStateStateMigration" stable
> --
>
> Key: FLINK-32963
> URL: https://issues.apache.org/jira/browse/FLINK-32963
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
>Affects Versions: 1.17.1
>Reporter: Asha Boyapati
>Priority: Minor
> Labels: pull-request-available
>
> We are proposing to make the following test stable:
> {{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
> The test is currently flaky because the order of elements returned by the
> iterator is non-deterministic.
> The following PR fixes the flaky test by making it independent of the order
> of elements returned by the iterator:
> [https://github.com/apache/flink/pull/23298|http://example.com]
> We detected this using the NonDex tool using the following command:
> {{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
> -DnondexRuns=10
> -Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
> Please see the following Continuous Integration log that shows the flakiness:
> [https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
> Please see the following Continuous Integration log that shows that the
> flakiness is fixed by this change:
> [https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (FLINK-32963) Make the test "testKeyedMapStateStateMigration" stable
Asha Boyapati created FLINK-32963:
-
Summary: Make the test "testKeyedMapStateStateMigration" stable
Key: FLINK-32963
URL: https://issues.apache.org/jira/browse/FLINK-32963
Project: Flink
Issue Type: Bug
Components: Runtime / State Backends
Affects Versions: 1.17.1
Reporter: Asha Boyapati
We are proposing to make the following test stable:
{{org.apache.flink.runtime.state.FileStateBackendMigrationTest.testKeyedMapStateStateMigration}}
The test is currently flaky because the order of elements returned by the
iterator is non-deterministic.
The following tentative PR fixes the flaky test by making it independent of the
order of elements returned by the iterator:
[https://github.com/asha-boyapati/flink/pull/1|http://example.com|http://example.com]
We detected this using the NonDex tool using the following command:
{{mvn edu.illinois:nondex-maven-plugin:2.1.1:nondex -pl flink-runtime
-DnondexRuns=10
-Dtest=org.apache.flink.runtime.state.FileStateBackendMigrationTest#testKeyedMapStateStateMigration}}
Please see the following Continuous Integration log that shows the flakiness:
[https://github.com/asha-boyapati/flink/actions/runs/5909136145/job/16029377793]
Please see the following Continuous Integration log that shows that the
flakiness is fixed by this change:
[https://github.com/asha-boyapati/flink/actions/runs/5909183468/job/16029467973]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
