Closed ryanbrandenburg closed 6 years ago
Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:
Is this actually a flaky test?
Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)
Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
HelloWorld failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
@Tratcher - please take a look at this high priority flaky test issue.
ResponseCompression_HostCompression failed with about the same error. ResponseCompression_Nginx_NoCompression failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
HelloWorldTests.HelloWorld(variant: Server: Nginx, TFM: netcoreapp2.2, Type: Standalone, Arch: x64)
HelloWorldTests.HelloWorld(variant: Server: Nginx, TFM: netcoreapp2.2, Type: Portable, Arch: x64)
ResponseCompressionTests.ResponseCompression_Nginx_NoCompression(serverType: Nginx, runtimeFlavor: CoreClr, architecture: x64, applicationType: Standalone)
All of the above have two interesting errors:
1) [warn] 30990#30990: the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /mnt/temp/buildTmp/tmp2zylcu.tmp:2
@natemcmaster didn't you just make changes to nginx user profiles? Is this warning concerning? https://github.com/aspnet/Hosting/commit/fed2eb1cdfef598b5315da045f741403fad89e05
2) nginx start stderr: nginx: [emerg] bind() to 0.0.0.0:33636 failed (98: Address already in use)
- Transient port conflict. This happened once per test, all on the same agent. This port was selected by TestPortHelper.GetNextPort() which binds to 0 and lets the OS choose. This may be a temporary resource issue on this agent. Recommend waiting for additional repros.
the "user" directive makes sense only if the master process runs with super-user privileges, ignored in /mnt/temp/buildTmp/tmp2zylcu.tmp
I didn't change userprofiles, just made the logic for figuring out the current username stronger. It was a fix for VSTS tests which failed to boot because the LOGNAME
env var was empty.
ResponseCompression_HostCompression failed with about the same error. ResponseFormats_Nginx_ContentLength failed again.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
HelloWorld failed with about the same error. HelloWorld failed with about the same error.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Hmm, these new failures are all the same port conflict on different tests for the same OS (Ubuntu). There's no history of flakiness here, it's become flaky in the last two weeks.
ResponseFormats_ManuallyChunk failed with about the same error.
This comment was made automatically. If there is a problem contact @ryanbrandenburg.
Resolved by https://github.com/aspnet/Hosting/pull/1515
This test fails occasionally with the following error:
Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.
CC @Eilon,@muratg,@mkArtakMSFT
This issue was made automatically. If there is a problem contact @ryanbrandenburg.