OSOE-928: Check if moving the .NET SDK install dir to the D drive on Windows makes the builds faster in Lombiq.GitHub.Actions #2324
Piedonebuild-and-test-windows.yml
on: pull_request
Matrix: Build and Test Windows - root solution (standard runners) 0 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 1 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 2 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 3 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 4 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 5 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 6 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 7 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 8 / Build and Test
Matrix: Build and Test Windows - root solution (standard runners) 9 / Build and Test
Annotations
1 error and 4 warnings
|
Build and Test Windows - root solution (standard runners) 3 / Build and Test (windows-2022)
The hosted runner: GitHub Actions 4 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
UI test may be flaky
The Lombiq.Tests.UI.Samples.Tests.InteractiveModeTests.EnteringInteractiveModeShouldWait test failed 1 time(s) and will be retried. This may indicate it being flaky.
|
|
UI test may be flaky
The Lombiq.Tests.UI.Samples.Tests.InteractiveModeTests.EnteringInteractiveModeShouldWait test failed 1 time(s) and will be retried. This may indicate it being flaky.
|
|
UI test may be flaky
The Lombiq.Tests.UI.Samples.Tests.InteractiveModeTests.EnteringInteractiveModeShouldWait test failed 2 time(s) and will be retried. This may indicate it being flaky.
|
|
UI test may be flaky
The Lombiq.Tests.UI.Samples.Tests.InteractiveModeTests.EnteringInteractiveModeShouldWait test failed 1 time(s) and will be retried. This may indicate it being flaky.
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
build-binary-log-.-Windows-X64-GitHub Actions 26.binlog
|
14.2 MB |
|
|
build-binary-log-.-Windows-X64-GitHub Actions 4.binlog
|
14.3 MB |
|
|
build-binary-log-.-Windows-X64-GitHub Actions 43.binlog
|
14.2 MB |
|
|
build-binary-log-.-Windows-X64-GitHub Actions 51.binlog
|
14.2 MB |
|
|
ui-test-failure-dump-.-Windows-X64-GitHub Actions 43
|
12 MB |
|
|
ui-test-failure-dump-.-Windows-X64-GitHub Actions 51
|
20.9 MB |
|