I am encountering the following build failure on nixos-unstable:

Building library for nix-output-monitor-2.1.6...
[ 1 of 25] Compiling Data.Sequence.Strict ( lib/Data/Sequence/Strict.hs, dist/build/Data/Sequence/Strict.o, dist/build/Data/Sequence/Strict.dyn_o )
[ 2 of 25] Compiling NOM.Builds       ( lib/NOM/Builds.hs, dist/build/NOM/Builds.o, dist/build/NOM/Builds.dyn_o )
[ 3 of 25] Compiling NOM.Error        ( lib/NOM/Error.hs, dist/build/NOM/Error.o, dist/build/NOM/Error.dyn_o )
[ 4 of 25] Compiling NOM.NixMessage.JSON ( lib/NOM/NixMessage/JSON.hs, dist/build/NOM/NixMessage/JSON.o, dist/build/NOM/NixMessage/JSON.dyn_o )
[ 5 of 25] Compiling NOM.NixMessage.OldStyle ( lib/NOM/NixMessage/OldStyle.hs, dist/build/NOM/NixMessage/OldStyle.o, dist/build/NOM/NixMessage/OldStyle.dyn_o )
[ 6 of 25] Compiling NOM.Parser       ( lib/NOM/Parser.hs, dist/build/NOM/Parser.o, dist/build/NOM/Parser.dyn_o )
[ 7 of 25] Compiling NOM.Parser.JSON  ( lib/NOM/Parser/JSON.hs, dist/build/NOM/Parser/JSON.o, dist/build/NOM/Parser/JSON.dyn_o )
[ 8 of 25] Compiling NOM.Print.Table  ( lib/NOM/Print/Table.hs, dist/build/NOM/Print/Table.o, dist/build/NOM/Print/Table.dyn_o )
[ 9 of 25] Compiling NOM.Print.Tree   ( lib/NOM/Print/Tree.hs, dist/build/NOM/Print/Tree.o, dist/build/NOM/Print/Tree.dyn_o )
[10 of 25] Compiling NOM.State.CacheId ( lib/NOM/State/CacheId.hs, dist/build/NOM/State/CacheId.o, dist/build/NOM/State/CacheId.dyn_o )
[11 of 25] Compiling NOM.State.CacheId.Set ( lib/NOM/State/CacheId/Set.hs, dist/build/NOM/State/CacheId/Set.o, dist/build/NOM/State/CacheId/Set.dyn_o )
[12 of 25] Compiling NOM.State.CacheId.Map ( lib/NOM/State/CacheId/Map.hs, dist/build/NOM/State/CacheId/Map.o, dist/build/NOM/State/CacheId/Map.dyn_o )
[13 of 25] Compiling NOM.State.Tree   ( lib/NOM/State/Tree.hs, dist/build/NOM/State/Tree.o, dist/build/NOM/State/Tree.dyn_o )
[14 of 25] Compiling NOM.StreamParser ( lib/NOM/StreamParser.hs, dist/build/NOM/StreamParser.o, dist/build/NOM/StreamParser.dyn_o )
[15 of 25] Compiling NOM.Update.Monad.CacheBuildReports ( lib/NOM/Update/Monad/CacheBuildReports.hs, dist/build/NOM/Update/Monad/CacheBuildReports.o, dist/build/NOM/Update/Monad/CacheBuildReports.dyn_o )
[16 of 25] Compiling NOM.Update.Monad ( lib/NOM/Update/Monad.hs, dist/build/NOM/Update/Monad.o, dist/build/NOM/Update/Monad.dyn_o )
[17 of 25] Compiling NOM.Util         ( lib/NOM/Util.hs, dist/build/NOM/Util.o, dist/build/NOM/Util.dyn_o )
[18 of 25] Compiling NOM.State        ( lib/NOM/State.hs, dist/build/NOM/State.o, dist/build/NOM/State.dyn_o )
[19 of 25] Compiling NOM.State.Sorting ( lib/NOM/State/Sorting.hs, dist/build/NOM/State/Sorting.o, dist/build/NOM/State/Sorting.dyn_o )
[20 of 25] Compiling NOM.Update       ( lib/NOM/Update.hs, dist/build/NOM/Update.o, dist/build/NOM/Update.dyn_o )
lib/NOM/Update.hs:172:18: error: [GHC-30606] [-Wredundant-constraints, Werror=redundant-constraints]
    Redundant constraint: UpdateMonad m
    In the type signature for:
         processResult :: NixOldStyleMessage -> ProcessingT m Bool
    |
172 | processResult :: (UpdateMonad m) => NixOldStyleMessage -> ProcessingT m Bool
    |                  ^^^^^^^^^^^^^^^

wow, never knew this was a thing

asciinema-3.0.1 (buildPhase) ⏱ 4m21s (∅ 6m31s)

i.e the ETA. I recently came across some pr which fixes generation of build reports I guess that allows tracking this.

wow, never knew this was a thing

asciinema-3.0.1 (buildPhase) ⏱ 4m21s (∅ 6m31s)

i.e the ETA (6m31s). I recently came across some pr which fixes generation of build reports I guess that allows tracking this.