Abacn commented on PR #30322: URL: https://github.com/apache/beam/pull/30322#issuecomment-1946317935
> Do you know how to run a test 100x to verify it isn't flaky? I'm not sure if there is a gradle invocation to do that or not. Maybe @Abacn knows It's unit test and the command can be this first in https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/build.gradle add a line ``` test.outputs.upToDateWhen {false} ``` (ref: https://stackoverflow.com/questions/29427020/how-to-run-gradle-test-when-all-tests-are-up-to-date); then use a script like ``` for i in `seq 1 100`; do ./gradlew :runners:google-cloud-dataflow-java:worker:test --tests *someSpecificUnitTest* done ``` and see the result. The problem is the tests with racing condition tends to be more flaky on GitHub Action than on local machines. This may be because the GHA runner has different load each time run, which affects timing, but the local machine do not -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
