Use DifferentiationInterface for the jacobian #77
Triggered via pull request
November 22, 2024 14:04
ErikQQY
Status
Failure
Total duration
1h 20m 48s
Artifacts
–
CI_BoundaryValueDiffEqFIRK.yml
on: pull_request
Matrix: downgrade
Matrix: tests
Annotations
12 errors
|
downgrade (1.10, EXPANDED)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
downgrade (1.10, EXPANDED)
The operation was canceled.
|
|
tests (lts, EXPANDED, ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (lts, EXPANDED, ubuntu-latest)
The operation was canceled.
|
|
tests (1, EXPANDED, ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (1, EXPANDED, ubuntu-latest)
The operation was canceled.
|
|
tests (pre, EXPANDED, ubuntu-latest)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
tests (pre, EXPANDED, ubuntu-latest)
The operation was canceled.
|
|
downgrade (1.10, NESTED)
The hosted runner: GitHub Actions 16 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
tests (lts, NESTED, ubuntu-latest)
The hosted runner: GitHub Actions 22 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
tests (pre, NESTED, ubuntu-latest)
The hosted runner: GitHub Actions 51 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
tests (1, NESTED, ubuntu-latest)
The hosted runner: GitHub Actions 41 lost communication with the server. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|