Stop relying on ChannelMonitor persistence after manager read #15439
Triggered via pull request
September 18, 2024 01:28
Status
Failure
Total duration
6h 0m 20s
Artifacts
–
build.yml
on: pull_request
coverage
3m 38s
benchmark
1m 13s
check_commits
10m 42s
check_release
2m 12s
fuzz
3m 41s
linting
53s
rustfmt
13s
incremental-mutants
2m 44s
Matrix: build
Annotations
16 errors
linting
Process completed with exit code 101.
|
benchmark
Process completed with exit code 101.
|
build (macos-latest, stable)
Process completed with exit code 101.
|
build (macos-latest, beta)
Process completed with exit code 101.
|
incremental-mutants
Process completed with exit code 4.
|
build (ubuntu-latest, beta)
Process completed with exit code 101.
|
build (ubuntu-latest, stable)
Process completed with exit code 101.
|
build (macos-latest, 1.63.0)
Process completed with exit code 101.
|
coverage
Process completed with exit code 1.
|
fuzz
Process completed with exit code 101.
|
build (windows-latest, beta)
Process completed with exit code 101.
|
build (ubuntu-latest, 1.63.0)
Process completed with exit code 101.
|
build (windows-latest, stable)
Process completed with exit code 101.
|
check_commits
Process completed with exit code 1.
|
build (windows-latest, 1.63.0)
The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes.
|
build (windows-latest, 1.63.0)
The operation was canceled.
|