Skip to content

Catch failure to open Worker and write out port #195

Catch failure to open Worker and write out port

Catch failure to open Worker and write out port #195

Re-run triggered September 23, 2024 15:21
Status Failure
Total duration 47m 32s
Artifacts

test.yml

on: pull_request
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

18 errors and 3 notices
test (1.8, macOS-latest)
Process completed with exit code 1.
test (1.8, ubuntu-latest)
Process completed with exit code 1.
test (1.6, ubuntu-latest)
Process completed with exit code 1.
test (1.7, ubuntu-latest)
Process completed with exit code 1.
test (1.9, ubuntu-latest)
Process completed with exit code 1.
test (1.7, macOS-latest)
Process completed with exit code 1.
test (1.10, ubuntu-latest)
Process completed with exit code 1.
test (1.7, windows-latest)
Process completed with exit code 1.
test (1.8, windows-latest)
Process completed with exit code 1.
test (1.10, windows-latest)
Process completed with exit code 1.
test (1.6, macOS-latest)
Process completed with exit code 1.
test (1.9, windows-latest)
Process completed with exit code 1.
test (nightly, ubuntu-latest)
Process completed with exit code 1.
test (nightly, windows-latest)
Process completed with exit code 1.
test (nightly, macOS-latest)
Process completed with exit code 1.
test (1.6, windows-latest)
Process completed with exit code 1.
test (1.10, macOS-latest)
The job running on runner GitHub Actions 17 has exceeded the maximum execution time of 25 minutes.
test (1.9, macOS-latest)
The job running on runner GitHub Actions 3 has exceeded the maximum execution time of 25 minutes.
test (1.6, ubuntu-latest)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
test (1.6, macOS-latest)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.
test (1.6, windows-latest)
[setup-julia] If you are testing 1.6 as a Long Term Support (lts) version, consider using the new "lts" version specifier instead of "1.6" explicitly, which will automatically resolve the current lts.