chore(flake/nixpkgs): 5a77c45f -> 5eb361ee
#3190
Triggered via pull request
September 24, 2023 01:41
phillip-ground[bot]
Status
Failure
Total duration
53m 16s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci.yml
on: pull_request
Matrix: conda-ubuntu-macos
Matrix: conda-windows
Matrix: nix
pre-commit
40m 30s
docker-image
39m 50s
tensorflow
46m 27s
dry-release
59s
commitlint
42s
release
0s
Annotations
8 errors and 15 warnings
|
docker-image
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
|
|
docker-image
Process completed with exit code 143.
|
|
pre-commit
The hosted runner encountered an error while running your job. (Error Type: Disconnect).
|
|
nix (ubuntu-latest, 311)
The hosted runner: GitHub Actions 28 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.
|
|
nix (ubuntu-latest, 38)
The hosted runner: GitHub Actions 33 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.
|
|
nix (ubuntu-latest, 310)
The hosted runner: GitHub Actions 38 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.
|
|
nix (ubuntu-latest, 39)
The hosted runner: GitHub Actions 4 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.
|
|
tensorflow
The hosted runner: GitHub Actions 5 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.
|
|
conda-ubuntu-macos (ubuntu-latest, 3.8, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (ubuntu-latest, 3.11, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (ubuntu-latest, 3.10, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-windows (3.10, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-windows (3.9, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (ubuntu-latest, 3.9, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-windows (3.8, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (macos-latest, 3.10, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-windows (3.11, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (ubuntu-latest, 3.9, no-buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (macos-latest, 3.8, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (macos-latest, 3.9, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-windows (3.9, no-buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (macos-latest, 3.11, buf)
Mamba support is still experimental and can result in differently solved environments!
|
|
conda-ubuntu-macos (macos-latest, 3.9, no-buf)
Mamba support is still experimental and can result in differently solved environments!
|