The deprecations triggered by some test is different (either they
get triggered in a different order or they don't trigger the same
amount of deprecations between multiple test runs).
By definition the test is flaky. Even if at the end the test passes,
the fact that sometime a method run and sometime it doesn't is the
sign of flakyness.
The deprecation toolkit can't deal with that.
This PR adds a way to mark a test as flaky so that the deprecations
triggered by the test will be ignored.
The syntax is like that:
Add a way to mark a test as flaky:
The deprecations triggered by some test is different (either they get triggered in a different order or they don't trigger the same amount of deprecations between multiple test runs).
By definition the test is flaky. Even if at the end the test passes, the fact that sometime a method run and sometime it doesn't is the sign of flakyness. The deprecation toolkit can't deal with that.
This PR adds a way to mark a test as flaky so that the deprecations triggered by the test will be ignored. The syntax is like that: