Run tests / Fix InvalidOperationException in DotMemoryDiagnoser If a DotMemoryDiagnoser instance is reused and previous AfterActualRun failed, we shouldn't throw on the second attempt to init the tool #883
AndreyAkinshinrun-tests.yaml
on: push
test-windows-core
33s
test-windows-full
35s
test-linux
52s
test-macos
59s
test-pack
49s
spellcheck-docs
13s
Annotations
10 errors and 4 warnings
|
test-windows-core
Canceling since a higher priority waiting request for 'run-tests-refs/heads/master' exists
|
|
test-windows-core
The operation was canceled.
|
|
test-windows-full
Canceling since a higher priority waiting request for 'run-tests-refs/heads/master' exists
|
|
test-windows-full
The operation was canceled.
|
|
test-pack
Canceling since a higher priority waiting request for 'run-tests-refs/heads/master' exists
|
|
test-pack
The operation was canceled.
|
|
test-linux
Canceling since a higher priority waiting request for 'run-tests-refs/heads/master' exists
|
|
test-linux
The operation was canceled.
|
|
test-macos
Canceling since a higher priority waiting request for 'run-tests-refs/heads/master' exists
|
|
test-macos
The operation was canceled.
|
|
test-windows-core
No files were found with the provided path: **/*.trx. No artifacts will be uploaded.
|
|
test-windows-full
No files were found with the provided path: **/*.trx. No artifacts will be uploaded.
|
|
test-linux
No files were found with the provided path: **/*.trx. No artifacts will be uploaded.
|
|
test-macos
No files were found with the provided path: **/*.trx. No artifacts will be uploaded.
|