Add support for WASM backend #3320
Triggered via pull request
August 12, 2025 02:44
hamishmack
Status
Failure
Total duration
1h 22m 34s
Artifacts
–
pipeline.yml
on: pull_request
nix-build
50m 23s
unit-tests
45s
runghc
4m 36s
cabal
9m 10s
cabal-doExactConfig
5m 53s
tests-benchmarks
1m 23s
multi-target
5m 50s
shellFor-single-package
34m 27s
shellFor-multiple-package
32m 13s
shellFor-hoogle
5m 4s
shellFor-not-depends
2m 42s
maintainer-scripts
14s
plan-extra-hackages
15s
build-extra-hackages
2m 17s
hix
1h 9m
docs
1h 13m
hydra-ifdLevel-0-and-1
10m 52s
hydra-ifdLevel-2
20m 17s
hydra-ifdLevel-3
30m 18s
closure-size
38s
update-docs
12s
check-materialization-concurrency
26s
check-path-support
3m 28s
haskell-nix-roots-do-not-require-IFDs
1m 28s
hydra-without-remote-builders-ghc967
6m 19s
hydra-without-remote-builders-ghc9102
8m 20s
hix-cabal
11m 1s
check-nix-tools
12m 44s
Annotations
9 errors
|
hydra-without-remote-builders-ghc967
Process completed with exit code 1.
|
|
hydra-without-remote-builders-ghc9102
Process completed with exit code 1.
|
|
check-nix-tools
Process completed with exit code 1.
|
|
hydra-ifdLevel-2
The operation was canceled.
|
|
hydra-ifdLevel-2
The job has exceeded the maximum execution time of 20m0s
|
|
hydra-ifdLevel-3
The operation was canceled.
|
|
hydra-ifdLevel-3
The job has exceeded the maximum execution time of 30m0s
|
|
docs
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|
|
hix
The self-hosted runner lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
|