-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Upgraded SIL.BuildTasks used in .proj file. Removed dependency on it from SIL.Windows.Forms #1363
Conversation
…from SIL.Windows.Forms
LibPalaso Tests 36 files - 9 36 suites - 9 8m 47s ⏱️ - 3m 8s For more details on these failures, see this check. Results for commit 75bb705. ± Comparison against base commit de37405. This pull request removes 698 tests.
|
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.
I see a single failing test here that I haven't seen be flaky before. Have you looked into this? I wonder if that would alleviate the problem of all the missing tests.
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.
Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @tombogle)
I didn't even bother looking. I figured I'd wait until the flaky test issue was resolved for good first. |
We can hope it gets fixed, but we're still seeing flaky tests, even when running each framework on its own machine. At the very least, my PR reduces server build time. It should also help with flakiness, but it won't go away. Some of these tests are just inherently flaky, unrelated to framework, e.g. testing the clipboard. In their case, we just need to mark them with |
Neither this text DLL nor the SUT reference SIL.BuildTasks, and this test passes for me locally, so it feels unlikely that it could be caused by this change. I did a tiny code simplification. Let's see if it magically passes this time. |
After merging master, all the tests pass. However, I'm also seeing a similar failure in #1364, so I suspect it is another instance of flakiness. Not 100% sure, but it seems to be coming from tests of LocateInProgramFilesFolder. I would think that if we're running up against a permissions problem, it would be failing consistently. But those tests do seem at least somewhat susceptible to failures on build agents. |
This change is