-
Notifications
You must be signed in to change notification settings - Fork 248
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opened pr and found new tests #1134
Opened pr and found new tests #1134
Conversation
…tests there is already a pr opened but was closed by the developer in 2018. So I reopened a new one.
What made your fixes for |
Those 3 confirmed flaky tests and 4 newly found flaky tests in |
Sorry I misread your Where are the logs that show those 4 tests failing before your changes but passing after your changes? |
Since there are both junit 4 and junit 5 tests at the same time I can't simply run iDFlakies. I've created a issue providing some details about the situation. I could add more details if needed. |
You claim that you fixed 4 tests. How do you show that if you can't run the tool? |
… 4 tests which are also OD flaky.
Added a more detailed issue to explain it. |
Thanks for clarifying! So each test is a brittle and fails alone. In what order do they pass -- even before you change? |
If we run com.alibaba.cloud.nacos.configdata.NacosConfigDataLocationResolverTest.testCommonPropertiesHasLowerPriority first, then other tests can pass. This is because in this test it set up some necessary environment properties. |
In
apache/jackrabbit-oak
: Opened a pr fixing two flaky tests. For one of the tests there is already a pr opened but was closed by the developer in 2018. So I reopened a new one.In
alibaba/spring-cloud-alibaba
: Opened a pr fixing 3 OD flaky tests, and then found out the fix can apply to other 4 tests which are also OD flaky.