-
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
Test failure: ProcessStart_UseShellExecute_OnUnix_SuccessWhenProgramInstalled(isFolder: False) #29375
Comments
This should be fixed by dotnet/corefx#37144. |
@danmosemsft that PR actually reintroduced these test failures. The timeline goes: dotnet/corefx#36913 - caused the intial set of failures (this is the current state in |
Oh... @tmds |
These are outerloop tests, which is why we missed them in CI. You can see the failures from this PR: dotnet/corefx#37197 |
I need to investigate further, but on first sight, these may be things we need to update in the tests:
|
I'm disabling this test temporarily, as it's causing all outerloop linux runs to fail. |
https://github.com/dotnet/corefx/issues/37198 Regression caused by #37144
I'm also disabling ProcessTests.LongProcessNamesAreSupported against this issue. |
And ProcessTests.ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList |
@stephentoub we need some input here: dotnet/corefx#37294 (comment) |
…#37294) * Linux: ProcessName: return script name instead of interpreter program Fixes https://github.com/dotnet/corefx/issues/37198 Regression by #37144 * Add ProcessNameMatchesScriptName test * ProcessNameMatchesScriptName: don't run on OSX * LongProcessNamesAreSupported: don't run on Alpine * Remove ActiveIssue attributes
The test is failing on Linux with:
There are a few related failures, such as
ProcessStart_OpenFileOnLinux_UsesSpecifiedProgramUsingArgumentList(programToOpenWith: \"vi\")
. These appear to have been introduced by dotnet/corefx@8b515ad#diff-c2151a182d9032ef4525c69b3569d024 & dotnet/corefx@4214b09#diff-c2151a182d9032ef4525c69b3569d024. The first change is in release/3.0, so we're seeing the failures inpreview5
as well.CC @stephentoub @tmds
The text was updated successfully, but these errors were encountered: