Skip to content
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

Merged
merged 2 commits into from
Dec 1, 2023

Conversation

lxb007981
Copy link
Contributor

@lxb007981 lxb007981 commented Nov 30, 2023

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.

…tests there is already a pr opened but was closed by the developer in 2018. So I reopened a new one.
@darko-marinov
Copy link
Contributor

What made your fixes for ID tests also fix OD tests? It'd be quite an interesting case. Do you have logs showing OD tests failing before your changes (ideally just running polluter-victim pairs) and then passing after your changes?

@lxb007981
Copy link
Contributor Author

What made your fixes for ID tests also fix OD tests? It'd be quite an interesting case. Do you have logs showing OD tests failing before your changes (ideally just running polluter-victim pairs) and then passing after your changes?

Those 3 confirmed flaky tests and 4 newly found flaky tests in alibaba/spring-cloud-alibaba are OD, not ID. There are no ID tests involved in this pr?

@darko-marinov
Copy link
Contributor

Sorry I misread your fixing 3 flaky tests, and then found out the fix can apply to other 4 tests which are also OD flaky as if you wrote fixing 3 ID flaky tests. You didn't write ID. (As a general rule, it may be better to open separate PRs or at least commits for different issues to make reviewing easier.)

Where are the logs that show those 4 tests failing before your changes but passing after your changes?

@lxb007981
Copy link
Contributor Author

Sorry I misread your fixing 3 flaky tests, and then found out the fix can apply to other 4 tests which are also OD flaky as if you wrote fixing 3 ID flaky tests. You didn't write ID. (As a general rule, it may be better to open separate PRs or at least commits for different issues to make reviewing easier.)

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.

@darko-marinov
Copy link
Contributor

You claim that you fixed 4 tests. How do you show that if you can't run the tool?

@lxb007981
Copy link
Contributor Author

You claim that you fixed 4 tests. How do you show that if you can't run the tool?

Added a more detailed issue to explain it.

@darko-marinov
Copy link
Contributor

Thanks for clarifying! So each test is a brittle and fails alone. In what order do they pass -- even before you change?

@lxb007981
Copy link
Contributor Author

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.

@darko-marinov darko-marinov merged commit d1f25eb into TestingResearchIllinois:main Dec 1, 2023
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants