-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
WindowsBase tests seems to fail on CI randomly with x64 Debug/Release #10250
Comments
I was able to reproduce locally, this is caused by the build not building the projects in the right order and the test projects sometimes being built before the native projects. I have a fix ready that I'll send in a minute. I'm assigning this issue to myself. Thanks @h3xds1nz for opening this and FYI the reason you see the tests all passing was because the tests failed to start so it failed to detect the tests to run so it was like PresentationCore.Tests.dll in Release x64 had 0 tests and 0 tests either passing, failing or skipped. If you want to investigate issues like this in the future you can go to the artifacts tab and download the artifacts tab for the configuration that failed and check in the log file (There's one for each project). |
@ThomasGoulet73 Thanks Thomas for taking a look; great find. And thanks for englightening me with the artifacts, I had no idea I can download them haha. |
The issue
This is 4th time out of like 15 CI builds this week that the
WindowsBase
tests have randomly failed on CI inx64 Release
configuration only.It seems like the two tests we have at the moment (Size, SplashScreen) itself do not fail though, they appear to pass - https://dev.azure.com/dnceng-public/public/_build/results?buildId=912047&view=ms.vss-test-web.build-test-results-tab
Other information
It is not reproducible for me locally when I'm building for x64 in release mode at all given numerous builds, so I wonder whether it has something to do with the CI builds in general or there's actually an issue with splash screen.
Might be worth looking into.
The text was updated successfully, but these errors were encountered: