You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you’re masochistic enough to run huge builds to test out breaking changes like I am lately, the bottom pane can fill up with failed builds without showing the current status:
┏━ 50 Errors:
⋮
┃ ├─ ⚠ angelfish-24.05.2 failed with exit code 1 after ⏱ 1m16s in configurePhase
┃ ├─ ⚠ olive-editor-unstable-2023-06-12 failed with exit code 2 after ⏱ 5m0s in buildPhase
┃ ├─ ⚠ octave-8.4.0-video-2.0.2 failed with exit code 1 after ⏱ 45s in buildPhase
┃ ├─ ⚠ openjfx-modular-sdk-21.0.3-ga failed with exit code 1 after ⏱ 20m48s in buildPhase
┃ ├─ ⚠ hedgewars-1.0.2 failed with exit code 2 after ⏱ 5m44s in buildPhase
┃ ├─ ⚠ openjfx-modular-sdk-22.0.1-ga failed with exit code 1 after ⏱ 15m31s in buildPhase
┃ ├─ ⚠ moc-2.5.2 failed with exit code 2 after ⏱ 6m31s in buildPhase
┃ ├─ ⚠ dvdstyler-3.2.1 failed with exit code 2 after ⏱ 4m30s in buildPhase
┃ ├─ ⚠ openjfx-modular-sdk-11.0.20-1 failed with exit code 1 after ⏱ 8m24s in buildPhase
┃ ├─ ⚠ electricsheep-3.0.2-2019-10-05 failed with exit code 2 after ⏱ 2m11s in buildPhase
┃ ├─ ⚠ tvheadend-4.2.8 failed with exit code 2 after ⏱ 1m13s in buildPhase
┃ ├─ ⚠ libqtav-unstable-2020-09-10 failed with exit code 2 after ⏱ 1m10s in buildPhase
┃ ├─ ⚠ febio-studio-1.6.1 failed with exit code 1 after ⏱ 21s in configurePhase
┃ ├─ ⚠ guacamole-server-1.5.5 failed with exit code 2 after ⏱ 3m25s in buildPhase
┃ ├─ ⚠ untrunc-anthwlock-0-unstable-2021-11-21 failed with exit code 2 after ⏱ 17s in buildPhase
┃ ├─ ⚠ simplescreenrecorder-0.4.4 failed with exit code 1 after ⏱ 25s in buildPhase
┃ ├─ ⚠ ccextractor-0.93 failed with exit code 2 after ⏱ 18s in buildPhase
┃ ├─ ⚠ attract-mode-2.6.2 failed with exit code 2 after ⏱ 1m55s in buildPhase
┃ ├─ ⚠ mediastreamer2-5.2.111 failed with exit code 2 after ⏱ 14s in buildPhase
┃ ├─ ⚠ musly-unstable-2017-04-26 failed with exit code 2 after ⏱ 11s in buildPhase
┃ ├─ ⚠ pipewire-0.2.7 failed with exit code 1 after ⏱ 24s in buildPhase
┃ ├─ ⚠ bombono-1.2.4 failed with exit code 2 after ⏱ 41s in buildPhase
┃ ├─ ⚠ oven-media-engine-0.16.6 failed with exit code 2 after ⏱ 1m15s in buildPhase
┃ ├─ ⚠ openrw-unstable-2021-10-14 failed with exit code 2 after ⏱ 22s in buildPhase
┃ ├─ ⚠ loudgain-0.6.8 failed with exit code 2 after ⏱ 9s in buildPhase
┃ ├─ ⚠ python3.12-ffmpeg-python-0.2.0 failed with exit code 1 after ⏱ 3s in pytestCheckPhase
┃ ├─ ⚠ python3.11-ffmpeg-python-0.2.0 failed with exit code 1 after ⏱ 3s in pytestCheckPhase
┃ ├─ ⚠ harvid-0.9.0 failed with exit code 2 after ⏱ 2s in buildPhase
┃ ├─ ⚠ pcsxr-1.9.94 failed with exit code 2 after ⏱ 21s in buildPhase
┃ ├─ ⚠ mplayer-unstable-2022-02-03 failed with exit code 2 after ⏱ 28s in buildPhase
┃ ├─ ⚠ libextractor-1.11 failed with exit code 2 after ⏱ 40s in buildPhase
┃ ├─ ⚠ guvcview-2.0.6 failed with exit code 2 after ⏱ 27s in buildPhase
┃ ├─ ⚠ bino-1.6.8 failed with exit code 2 after ⏱ 16s in buildPhase
┃ ├─ ⚠ alephone-1.8.1 failed with exit code 2 after ⏱ 34s in buildPhase
┃ ├─ ⚠ python3.11-torchaudio-2.3.1 failed with exit code 1 after ⏱ 5s in fixupPhase
┃ ┌─ ⏸ env
┃ ⏸ review-shell
┣━━━ Builds │ Downloads │ Host
┃ ⏵ 12 │ ✔ 161 │ │ │ │ │ localhost
┃ │ │ │ │ ↓ 3208 │ │ [1]: https://cache.nixos.org
┃ │ │ │ │ ↓ 21 │ │ [2]: https://nix-community.cachix.org
┗━ ∑ ⏵ 12 │ ✔ 161 │ ⏸ 429 │ ↓ 0 │ ↓ 3229 │ ⏸ 0 │ ⏱ 1h56m45s
I think that past a certain number of failures it is more valuable to see ongoing progress than yet another failure. Perhaps it could show only the the most recent 10–20 failures or something.
The text was updated successfully, but these errors were encountered:
I only started using nix-output-monitor because nixpkgs-review defaults to it on the community builder so I might have a very non-representative set of build graphs I've put through it :)
If you’re masochistic enough to run huge builds to test out breaking changes like I am lately, the bottom pane can fill up with failed builds without showing the current status:
I think that past a certain number of failures it is more valuable to see ongoing progress than yet another failure. Perhaps it could show only the the most recent 10–20 failures or something.
The text was updated successfully, but these errors were encountered: