Skip to content

Do we assume that there is just 1 runtime_sequence per device? #3085

Do we assume that there is just 1 runtime_sequence per device?

Do we assume that there is just 1 runtime_sequence per device? #3085

Triggered via pull request August 17, 2024 23:11
Status Success
Total duration 15m 35s
Artifacts 1

ci.yml

on: pull_request
Build and Test (Linux, ASSERTIONS)
8m 57s
Build and Test (Linux, ASSERTIONS)
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Build and Test (Linux, ASSERTIONS)
This self-hosted runner is currently using runner version 2.317.0. This version is out of date. Please update to the latest version 2.319.1
Build and Test (Linux, ASSERTIONS)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@8f4b7f84864484a7bf31766abe9204da3cbe65b3, actions/cache/restore@v3, actions/cache/save@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test_linux
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@8f4b7f84864484a7bf31766abe9204da3cbe65b3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

Artifacts

Produced during runtime
Name Size
linux_x86_64_release_packages Expired
81 MB