!yxFWYdmeLrdzdoIrcE:maralorn.de

nix-output-monitor

93 Members
https://github.com/maralorn/nix-output-monitor30 Servers

Load older messages


SenderMessageTime
17 Nov 2025
@hexa:lossy.networkhexa5334.?21:44:39
@hexa:lossy.networkhexaimage.png
Download image.png
21:46:35
@hexa:lossy.networkhexacraaaazy numbers21:46:36
@maralorn:maralorn.demaralornOooookay21:50:54
@maralorn:maralorn.demaralornWhatever.21:50:57
@maralorn:maralorn.demaralornI’ll remove the progress for builds again.21:51:17
@hexa:lossy.networkhexahdcd: hexa@build1.darmstadt.ccc.de hcdd: hexa@build2.darmstadt.ccc.de πŸ€”21:54:08
@hexa:lossy.networkhexa* hdcd: hexa@build1.darmstadt.ccc.de hccd: hexa@build2.darmstadt.ccc.de πŸ€”21:54:12
@hexa:lossy.networkhexa* hdcd: hexa@build1.darmstadt.ccc.de hdcd: hexa@build2.darmstadt.ccc.de πŸ€”21:54:15
@maralorn:maralorn.demaralornYeah, I know. I plan to write a smart disambiguation there.21:56:46
@maralorn:maralorn.demaralorni.e. I would probably wan’t this to be b1dcd and b2dcd21:57:08
@hexa:lossy.networkhexaor bdcdN21:58:25
@hexa:lossy.networkhexa* or bdcd121:58:27
@hexa:lossy.networkhexadon't parse the number in the hostname, just enumerate them21:58:44
@maralorn:maralorn.demaralornHuh, that would be easier, true.21:59:07
18 Nov 2025
@hexa:lossy.networkhexathere are builds that log a percentage progress00:48:59
@hexa:lossy.networkhexa e.g. cmake builds go [ 23%] foobar [100%] every few lines 00:49:24
@hexa:lossy.networkhexa * e.g. cmake builds go [ 23%] foobar [100%] foobar every few lines 00:49:31
@hexa:lossy.networkhexathat would be a worthwhile thing to display, I think00:49:44
@hexa:lossy.networkhexaor bazel00:49:51
@hexa:lossy.networkhexa which logs [67/2202] (done/total) 00:50:53
@hexa:lossy.networkhexaalthough total can grow00:50:59
@hexa:lossy.networkhexaboth of these are logged at the start of a line00:51:10
@hexa:lossy.networkhexaso maybe just add build progress when you can derive it from the log00:51:35
@hexa:lossy.networkhexaand if you know phases you can even show build and test progress00:51:57
@hexa:lossy.networkhexa* and if you know phases you could even show build and test progress00:52:01
@hexa:lossy.networkhexa
requests> ........................................................................ [ 28%]
requests> ........................................................................ [ 56%]
requests> ..................................................sssssssssss.....s..... [ 84%]
00:52:30
@hexa:lossy.networkhexafor pytest00:52:33
@hexa:lossy.networkhexathis could compensate for fast scrolling logs πŸ™‚ 00:52:59
@vivekanandan_ks:matrix.orgvivekanandan_ks

U mean the overall progress in percentage instead of just numbers?

I mean like below for downloads, builds, overall progress?
downloads [50/100] 50%

Or u mean for individual package builds?πŸ€”

06:08:32

Show newer messages


Back to Room ListRoom Version: 9