[Breaking Change] Make Mesh-Level Boundary Conditions Usable without "User" flag (now without bitrot) #2887
YurlungurAnnotations
9 errors and 3 warnings
|
integration (host)
Process completed with exit code 8.
|
|
integration (cuda)
The job was canceled because "host" failed.
|
|
integration (cuda)
The operation was canceled.
|
|
unit (host)
Canceling since a higher priority waiting request for 'CI short-jmm/global-boundaries-2' exists
|
|
unit (host)
The operation was canceled.
|
|
unit (cuda)
Canceling since a higher priority waiting request for 'CI short-jmm/global-boundaries-2' exists
|
|
unit (cuda)
The operation was canceled.
|
|
integration-amdgpu
Canceling since a higher priority waiting request for 'CI short-jmm/global-boundaries-2' exists
|
|
integration-amdgpu
The operation was canceled.
|
|
style
The following actions use a deprecated Node.js version and will be forced to run on node20: 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/
|
|
integration (host)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
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: "configure-log-style".
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 | |
|---|---|---|
|
configure-log-style
Expired
|
48.5 KB |
|