nix-output-monitor icon indicating copy to clipboard operation
nix-output-monitor copied to clipboard

Published 20 hours ago • verified publisher icon maralorn

Sometimes nom doesn‘t update the displayed state after a first build failure

Open maralorn opened this issue 3 years ago • 6 comments

Relevant when using nom with --keep-going.

Encountered by me, @piegamesde and @andir

Apparently even going back quite a while.

First step would be to find a reliable reproducer.

maralorn avatar May 02 '22 10:05 maralorn

For reproducing, I suggest cross-compiling some larger package, for example aarch64-multiplatform.gtk4:

  • A large package tree
  • At least some of the packages are bound to fail straight away during configure phase
  • Large enough to give you multiple attempts before having to GC :)

piegamesde avatar May 02 '22 10:05 piegamesde

@piegamesde do you remember if the clock kept running after the error?

maralorn avatar Jun 27 '22 21:06 maralorn

I wouldn‘t be surprised if this issue does not happen with the new json based parsing, but we should keep an eye out for it.

maralorn avatar Jun 27 '22 21:06 maralorn

Not sure if the clock kept running for the failed task, but for the other (supposedly) running tasks it did

piegamesde avatar Jun 27 '22 21:06 piegamesde

This issue is very old and the code in question has seen a lot of refactoring since. I have not been able to reproduce it. I encourage anyone who encounters this again to reopen this issue.

maralorn avatar Nov 21 '22 05:11 maralorn

I just observed this issue again. Clock keeps running, logs still get printed but the displayed state goes stale. Like the thread responsible for updating the state hangs somehow.

maralorn avatar Nov 14 '23 17:11 maralorn