-
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
Hosting DirectSettingsOverrideConfigurationSetting and ConfigurationSettingCanInfluenceEnvironment test failures in CI #79453
Comments
Tagging subscribers to this area: @dotnet/area-extensions-configuration Issue DetailsIt looks like #79242 introduced a flakey test. From reading the test and the logs, it appears that a bad We should update the test to control the temp directory being used so the test runs deterministically. cc @halter73
|
Tagging subscribers to this area: @dotnet/area-extensions-hosting Issue DetailsIt looks like #79242 introduced a flakey test. From reading the test and the logs, it appears that a bad We should update the test to control the temp directory being used so the test runs deterministically. cc @halter73
|
Ensure the temp directory used is always empty, so it doesn't pick up appsettings.json files randomly. Fix dotnet#79453
Ensure the temp directory used is always empty, so it doesn't pick up appsettings.json files randomly. Fix #79453
Ensure the temp directory used is always empty, so it doesn't pick up appsettings.json files randomly. Fix #79453
* Do not override content root with default * Address PR feedback * Add more test coverage for custom HostApplicationBuilderSettings * Make package authoring changes * Fix failing Hosting tests (#79455) Ensure the temp directory used is always empty, so it doesn't pick up appsettings.json files randomly. Fix #79453 * Add reference to System.Diagnostics.DiagnosticSource Co-authored-by: Stephen Halter <[email protected]> Co-authored-by: Eric Erhardt <[email protected]> Co-authored-by: Eric StJohn <[email protected]>
It looks like #79242 introduced a flakey test. From reading the test and the logs, it appears that a bad
appsettings.json
file is getting written to the %TEMP% directory while this test is running, causing the test to fail.We should update the test to control the temp directory being used so the test runs deterministically.
cc @halter73
Logs:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=106763&view=logs&j=bc8f69e2-91b3-518c-84f8-466a04c1af40&t=0864dbdb-cb3f-5f82-b0b6-057b78db53e2&l=101
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-79425-merge-95c0735a07484698ac/Microsoft.Extensions.Hosting.Unit.Tests/1/console.bbd2f5df.log?helixlogtype=result
https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-79425-merge-95c0735a07484698ac/Microsoft.Extensions.Hosting.Unit.Tests/1/console.bbd2f5df.log?helixlogtype=result
Error Message
Fill the error message using known issues guidance.
Report
Summary
The text was updated successfully, but these errors were encountered: