One more thing: there should be other builds running while the flaky check is being
executed (otherwise it will be "alone" on a 12 core system)
On 6/10/20 3:49 PM, Zoltan Haindrich wrote:
Hey All!
I've fiddled around to build this into the main test system or not; but in the end I've concluded that it will be more usefull as a standalone tool (this makes the job a
bit uglier - but well...it would have made the main one uglier as well - so it doesn't matter which finger I'll bite)
So...if you are suspecting that test is causing trouble for no good reason; you
could launch a run of this job which will run it a 100 times in a row...if it
fails...well:
* you could open a jira which references the check you executed which proves
that the test is low quality
* please also add the "flaky-test" label to the jira
* add an Ignore to the test referencing the jira ticket
* push the commit which disables the test...
The other use would be when enabling previously unreliable tests back:
* push your branch which supposed to stabilize the test to your own fork on
github
* visit http://130.211.9.232/job/hive-flaky-check/
* point the job to your user/repo/branch ; and configure to run the test in
question to validate it
cheers,
Zoltan
