Skip to content

Nightly CLI Execution Tests (Published + BMDB) #473

Nightly CLI Execution Tests (Published + BMDB)

Nightly CLI Execution Tests (Published + BMDB) #473

Triggered via schedule August 17, 2024 07:03
Status Failure
Total duration 6h 7m 13s
Artifacts 2

NightlyBMDB_CLI.yml

on: schedule
Matrix: bmdb
Matrix: published
bmdb_results
0s
bmdb_results
published_results
0s
published_results
Fit to window
Zoom out
Zoom in

Annotations

90 errors and 16 warnings
published (1)
System.IO.IOException: No space left on device : '/home/runner/runners/2.319.1/_diag/Worker_20240817-071013-utc.log' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.BufferedFileStreamStrategy.FlushWrite() at System.IO.StreamWriter.Flush(Boolean flushStream, Boolean flushEncoder) at System.Diagnostics.TextWriterTraceListener.Flush() at GitHub.Runner.Common.HostTraceListener.WriteHeader(String source, TraceEventType eventType, Int32 id) at GitHub.Runner.Common.HostTraceListener.TraceEvent(TraceEventCache eventCache, String source, TraceEventType eventType, Int32 id, String message) at System.Diagnostics.TraceSource.TraceEvent(TraceEventType eventType, Int32 id, String message) at GitHub.Runner.Worker.Worker.RunAsync(String pipeIn, String pipeOut) at GitHub.Runner.Worker.Program.MainAsync(IHostContext context, String[] args)
published (17)
The job was canceled because "_1" failed.
published (17)
Process completed with exit code 1.
published (17)
The operation was canceled.
published (13)
The job was canceled because "_1" failed.
published (13)
The operation was canceled.
published (13)
Process completed with exit code 1.
published (5)
The job was canceled because "_1" failed.
published (5)
Process completed with exit code 1.
published (5)
The operation was canceled.
published (18)
The job was canceled because "_1" failed.
published (18)
The operation was canceled.
published (7)
The job was canceled because "_1" failed.
published (7)
The operation was canceled.
published (0)
The job was canceled because "_1" failed.
published (0)
The operation was canceled.
published (4)
The job was canceled because "_1" failed.
published (4)
The operation was canceled.
published (16)
The job was canceled because "_1" failed.
published (16)
The operation was canceled.
published (3)
The job was canceled because "_1" failed.
published (3)
The operation was canceled.
published (6)
The job was canceled because "_1" failed.
published (6)
The operation was canceled.
published (8)
The job was canceled because "_1" failed.
published (8)
The operation was canceled.
published (19)
The job was canceled because "_1" failed.
published (19)
The operation was canceled.
published (2)
The job was canceled because "_1" failed.
published (2)
The operation was canceled.
bmdb (0)
The job running on runner GitHub Actions 28 has exceeded the maximum execution time of 360 minutes.
bmdb (0)
Process completed with exit code 1.
bmdb (0)
The operation was canceled.
bmdb (15)
The job running on runner GitHub Actions 24 has exceeded the maximum execution time of 360 minutes.
bmdb (15)
The operation was canceled.
bmdb (15)
Process completed with exit code 1.
bmdb (4)
The job running on runner GitHub Actions 9 has exceeded the maximum execution time of 360 minutes.
bmdb (4)
Process completed with exit code 1.
bmdb (4)
The operation was canceled.
bmdb (1)
The job running on runner GitHub Actions 50 has exceeded the maximum execution time of 360 minutes.
bmdb (1)
Process completed with exit code 1.
bmdb (1)
The operation was canceled.
bmdb (10)
The job running on runner GitHub Actions 4 has exceeded the maximum execution time of 360 minutes.
bmdb (10)
The operation was canceled.
bmdb (10)
Process completed with exit code 1.
bmdb (12)
The job running on runner GitHub Actions 41 has exceeded the maximum execution time of 360 minutes.
bmdb (12)
Process completed with exit code 1.
bmdb (12)
The operation was canceled.
bmdb (11)
The job running on runner GitHub Actions 22 has exceeded the maximum execution time of 360 minutes.
bmdb (11)
The operation was canceled.
bmdb (11)
Process completed with exit code 1.
bmdb (16)
The job running on runner GitHub Actions 32 has exceeded the maximum execution time of 360 minutes.
bmdb (16)
The operation was canceled.
bmdb (16)
Process completed with exit code 1.
bmdb (7)
The job running on runner GitHub Actions 49 has exceeded the maximum execution time of 360 minutes.
bmdb (7)
Process completed with exit code 1.
bmdb (7)
The operation was canceled.
bmdb (18)
The job running on runner GitHub Actions 42 has exceeded the maximum execution time of 360 minutes.
bmdb (18)
Process completed with exit code 1.
bmdb (18)
The operation was canceled.
bmdb (8)
The job running on runner GitHub Actions 21 has exceeded the maximum execution time of 360 minutes.
bmdb (8)
Process completed with exit code 1.
bmdb (8)
The operation was canceled.
bmdb (13)
The job running on runner GitHub Actions 48 has exceeded the maximum execution time of 360 minutes.
bmdb (13)
The operation was canceled.
bmdb (13)
Process completed with exit code 1.
bmdb (9)
The job was canceled because "_0" failed.
bmdb (9)
The operation was canceled.
bmdb (9)
Process completed with exit code 1.
bmdb (14)
The job running on runner GitHub Actions 40 has exceeded the maximum execution time of 360 minutes.
bmdb (14)
Process completed with exit code 1.
bmdb (14)
The operation was canceled.
bmdb (19)
The job running on runner GitHub Actions 46 has exceeded the maximum execution time of 360 minutes.
bmdb (19)
Process completed with exit code 1.
bmdb (19)
The operation was canceled.
bmdb (17)
The job running on runner GitHub Actions 31 has exceeded the maximum execution time of 360 minutes.
bmdb (17)
Process completed with exit code 1.
bmdb (17)
The operation was canceled.
bmdb (5)
The job running on runner GitHub Actions 59 has exceeded the maximum execution time of 360 minutes.
bmdb (5)
The operation was canceled.
bmdb (5)
Process completed with exit code 1.
bmdb (2)
The job running on runner GitHub Actions 45 has exceeded the maximum execution time of 360 minutes.
bmdb (2)
Process completed with exit code 1.
bmdb (2)
The operation was canceled.
bmdb (3)
The job running on runner GitHub Actions 17 has exceeded the maximum execution time of 360 minutes.
bmdb (3)
The operation was canceled.
bmdb (3)
Process completed with exit code 1.
bmdb (6)
The job running on runner GitHub Actions 5 has exceeded the maximum execution time of 360 minutes.
bmdb (6)
Process completed with exit code 1.
bmdb (6)
The operation was canceled.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/upload-artifact@v3, actions/setup-python@v4, actions/setup-java@v2, docker/setup-buildx-action@v2, docker/build-push-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (9)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (9)
No files were found with the provided path: /home/runner/work/vcell/vcell/errors.report. No artifacts will be uploaded.
published (10)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (10)
No files were found with the provided path: /home/runner/work/vcell/vcell/errors.report. No artifacts will be uploaded.
published (15)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (15)
No files were found with the provided path: /home/runner/work/vcell/vcell/errors.report. No artifacts will be uploaded.
published (14)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (14)
No files were found with the provided path: /home/runner/work/vcell/vcell/errors.report. No artifacts will be uploaded.
published (11)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (11)
No files were found with the provided path: /home/runner/work/vcell/vcell/errors.report. No artifacts will be uploaded.
published (12)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/download-artifact@v3, actions/checkout@v3, actions/upload-artifact@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
published (12)
No files were found with the provided path: /home/runner/work/vcell/vcell/errors.report. No artifacts will be uploaded.
published (1)
You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 0 MB
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "docker-image", "github_hash". Please update your workflow to use v4 of the artifact actions. Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Artifacts

Produced during runtime
Name Size
docker-image
775 MB
github_hash
18 Bytes