-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Many installer tests are failing because of Directory.Build.props file is missing #38530
Comments
From |
Looks like host tests, maybe only single-file host tests? @jeffschwMSFT @vitek-karas @swaroop-sridhar |
Looks like building the test fixture failed. It's strange, but there's nothing specific to single-file tests. |
Tagging subscribers to this area: @vitek-karas, @swaroop-sridhar, @agocke |
The following tests failed on my PR #45808 in the
|
10+ tests failed in https://dev.azure.com/dnceng/public/_build/results?buildId=1316373&view=ms.vss-test-web.build-test-results-tab&runId=38724840&resultId=100355&paneView=debug (rolling build) and there are numerous other reports that this is affecting both PR and rolling build runs. @agocke this is showing up on our reliability dashboard every week and hence impacts our ability to improve our reliability numbers. Can someone please take a look asap? |
Tests that fail because of the underlying infrastructure issue:
A few affected rolling builds that I found from the last two days:
The underlying infrastructure issue shouldn't be too hard to identify. I would start with uploading binlogs of the generated installer projects and inspecting the relevant infrastructure code (those are just a few lines). |
Sure, I've been investigating the "text file is busy" problem, but if this one is more severe I can switch focus. |
Failed again in: runtime 20210901.70 Failed test:
Error message:
|
Should be fixed by #59276 |
failed in job: runtime 20200628.29
failed tests:
Bundle_can_be_renamed_while_running
Bundled_Localized_App_Run_Succeeds
Can_Run_App_With_StatiHost
Can_Run_SingleFile_App_With_StatiHost
Error message
The text was updated successfully, but these errors were encountered: