Skip to content

Fix flaky test: use int.MaxValue instead of PID 9999 #351

Fix flaky test: use int.MaxValue instead of PID 9999

Fix flaky test: use int.MaxValue instead of PID 9999 #351

Triggered via push April 1, 2026 15:20
Status Cancelled
Total duration 1m 23s
Artifacts

ci.yml

on: push
Backend Build
48s
Backend Build
Frontend Build
48s
Frontend Build
Matrix: unit-test-other
Frontend Test
48s
Frontend Test
Matrix: unit-test-linux
Integration Tests
Integration Tests
Automation Tests
Automation Tests
Build Complete
3s
Build Complete
Fit to window
Zoom out
Zoom in

Annotations

15 errors and 2 warnings
Unit Tests (windows-latest)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Unit Tests (windows-latest)
Process completed with exit code 1.
Unit Tests (windows-latest)
No test results found - tests did not run
Unit Tests (windows-latest)
The operation was canceled.
Frontend Test
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Frontend Test
The operation was canceled.
Backend Build
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Backend Build
The operation was canceled.
Frontend Build
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Frontend Build
The operation was canceled.
Unit Tests (macos-latest)
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Unit Tests (macos-latest)
Process completed with exit code 1.
Unit Tests (macos-latest)
No test results found - tests did not run
Unit Tests (macos-latest)
The operation was canceled.
CI
Canceling since a higher priority waiting request for CI-refs/heads/main exists
Unit Tests (windows-latest)
No files were found with the provided path: ./test-results. No artifacts will be uploaded.
Unit Tests (macos-latest)
No files were found with the provided path: ./test-results. No artifacts will be uploaded.