-
-
Notifications
You must be signed in to change notification settings - Fork 367
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
Fix flaky test by a test env setup refactor #4273
Conversation
It seems
|
That seems impossible to me, there must be another race condition :D |
Weird because |
The setup wasn't creating the |
definition.Imported symbol (reexported) fails without
|
This is good! Let's merge this as is, add the comment to the test case, create an issue containing the knowledge you have gained so far, and then accept the test case changes. E.g., update the assertions in the test. Even though we have discovered an interesting race (?) condition, the test case itself will be stable. @komikat Could you do that, please? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a comment to the test case that fails now and create a new tracking issue! LGTM otherwise
This is a bug in our code, It worth a seperate issue to fix this. |
The test has this condition which seems to be wrong if ghcVersion >= GHC94 && ghcVersion < GHC910 then mkL bar 3 5 3 8 else mkL bar 3 0 3 14 I've set it to just be |
Hm, still failing a few windows tests. |
Fixes #4200 by creating a separate temporary
.cache
directory for every test instead of having all tests share the same.cache
directory. This makes sure the testiface-error-test-1
is run with a clean directory — causing the diagnostic to be generated every time.