.Net Processes: fixing KernelProcessStateMetadata usage #20333
Triggered via pull request
November 7, 2024 17:59
Status
Cancelled
Total duration
3m 28s
Artifacts
–
dotnet-build-and-test.yml
on: pull_request
paths-filter
5s
Matrix: dotnet-build-and-test
dotnet-build-and-test-check
4s
Annotations
7 errors and 2 warnings
dotnet-build-and-test (8.0, windows-latest, Debug)
Canceling since a higher priority waiting request for 'dotnet-build-and-test-9598' exists
|
dotnet-build-and-test (8.0, windows-latest, Debug)
The operation was canceled.
|
dotnet-build-and-test (8.0, windows-latest, Release)
Canceling since a higher priority waiting request for 'dotnet-build-and-test-9598' exists
|
dotnet-build-and-test (8.0, windows-latest, Release)
The operation was canceled.
|
dotnet-build-and-test (8.0, ubuntu-latest, Release, true, integration)
Canceling since a higher priority waiting request for 'dotnet-build-and-test-9598' exists
|
dotnet-build-and-test (8.0, ubuntu-latest, Release, true, integration)
The operation was canceled.
|
dotnet-build-and-test-check
Integration Tests Cancelled!
|
paths-filter
The following actions use a deprecated Node.js version and will be forced to run on node20: dorny/paths-filter@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
dotnet-build-and-test-check
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/github-script@v6. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|