[ 
https://issues.apache.org/jira/browse/FLINK-32963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17760699#comment-17760699
 ] 

Hangxiang Yu commented on FLINK-32963:
--------------------------------------

This is just a simple improvement to make this UT case more reasonable which 
doesn't affect the main code path and CI.

So I think it's fine that we just resolved it in the master.

> 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
>            Assignee: Asha Boyapati
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.19.0
>
>
> 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)

Reply via email to