Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[wasm] Fix debugger tests run on CI/Windows #79124

Merged
merged 1 commit into from
Dec 2, 2022

Conversation

radical
Copy link
Member

@radical radical commented Dec 2, 2022

This broke recently, and can be see on a rolling build:

  'C:\Program' is not recognized as an internal or external command,
  operable program or batch file.
D:\a\_work\1\s\src\mono\wasm\debugger\DebuggerTestSuite\DebuggerTestSuite.csproj(57,5): error MSB3073: The command "C:\Program Files\dotnet\dotnet.exe test --no-build -s D:\a\_work\1\s\artifacts\bin\DebuggerTestSuite\x64\Debug\.runsettings -t --nologo -v:q" exited with code 9009.
  • this is breaking because we are running src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestSuite.csproj <Exec Command="$(DotNetTool) test ..." />

    • and DotNetTool here is c:\Program Files\dotnet\dotnet.exe, and the shell command breaks because of the space.
    • this broke because recently we moved to building with 7.0.100. And when the version used for building matches the version installed on the system, the system dotnet is used.
      • but when it doesn't, it gets installed in </repo/checkout>/.dotnet/dotnet
      • So, because of the recent update the path changed to C:\Program files, and broke the command. - The fix is to simply quote the path.

This broke recently:

```
  'C:\Program' is not recognized as an internal or external command,
  operable program or batch file.
D:\a\_work\1\s\src\mono\wasm\debugger\DebuggerTestSuite\DebuggerTestSuite.csproj(57,5): error MSB3073: The command "C:\Program Files\dotnet\dotnet.exe test --no-build -s D:\a\_work\1\s\artifacts\bin\DebuggerTestSuite\x64\Debug\.runsettings -t --nologo -v:q" exited with code 9009.
```

- this is breaking because we are running `src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestSuite.csproj`
    `<Exec Command="$(DotNetTool) test ..." />`

  - and `DotNetTool` here is `c:\Program Files\dotnet\dotnet.exe`, and
    the shell command breaks because of the space.
  - this broke because recently we moved to building with `7.0.100`. And
    when the version used for building matches the version installed on
    the system, the system dotnet is used.
    - but when it doesn't, it gets installed in
      `</repo/checkout>/.dotnet/dotnet`
    - So, because of the recent update the path changed to `C:\Program files`,
      and broke the command.
    - The fix is to simply quote the path.
@radical radical added arch-wasm WebAssembly architecture area-Debugger-mono labels Dec 2, 2022
@radical radical requested a review from thaystg as a code owner December 2, 2022 00:22
@ghost ghost assigned radical Dec 2, 2022
@ghost
Copy link

ghost commented Dec 2, 2022

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

This broke recently, and can be see on a rolling build:

  'C:\Program' is not recognized as an internal or external command,
  operable program or batch file.
D:\a\_work\1\s\src\mono\wasm\debugger\DebuggerTestSuite\DebuggerTestSuite.csproj(57,5): error MSB3073: The command "C:\Program Files\dotnet\dotnet.exe test --no-build -s D:\a\_work\1\s\artifacts\bin\DebuggerTestSuite\x64\Debug\.runsettings -t --nologo -v:q" exited with code 9009.
  • this is breaking because we are running src/mono/wasm/debugger/DebuggerTestSuite/DebuggerTestSuite.csproj <Exec Command="$(DotNetTool) test ..." />

    • and DotNetTool here is c:\Program Files\dotnet\dotnet.exe, and the shell command breaks because of the space.
    • this broke because recently we moved to building with 7.0.100. And when the version used for building matches the version installed on the system, the system dotnet is used.
      • but when it doesn't, it gets installed in </repo/checkout>/.dotnet/dotnet
      • So, because of the recent update the path changed to C:\Program files, and broke the command. - The fix is to simply quote the path.
Author: radical
Assignees: -
Labels:

arch-wasm, area-Debugger-mono

Milestone: -

@radical radical changed the title [wasm] Fix debugger tests run on Windows [wasm] Fix debugger tests run on CI/Windows Dec 2, 2022
@radical radical requested review from ilonatommy and lewing December 2, 2022 00:22
@stephentoub
Copy link
Member

Merging to unblock CI

@stephentoub stephentoub merged commit 9d7ffb5 into dotnet:main Dec 2, 2022
@radical radical deleted the fix-dbg-tests-win branch December 5, 2022 19:57
@ghost ghost locked as resolved and limited conversation to collaborators Jan 5, 2023
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
arch-wasm WebAssembly architecture area-Debugger-mono
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants