| Summary: | app-portage/portage-utils-0.96.1: qlop -r to report as empty while building some packages | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | CaptainBlood <luc_pierard_de_maujouy> |
| Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | luc_pierard_de_maujouy, zuccavondille |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Insufficient information: please give emerge --info and the tail end of the summary log qlop parses (including the region where openjdk should be). There's really nothing the ebuild should be able to control here though. My guess is you used ebuild and not emerge. dev-java/openjdk:8[-jbootstrap] here. Cancellatop checked properly reported. I don't understand what that means, I'm sorry. Problem generated with Installed versions: 8.402_p06(8)(22:17:09 07/03/2024)(alsa -cups -debug -doc -examples -headless-awt -javafx -jbootstrap -selinux -source) 11.0.22_p7 USE=jbootstrap emerge -1 dev-java/openjdk:8 is properly reported as in progress when running qlop -r. However well reported once done: 2024-03-07T21:57:47 >>> dev-java/openjdk-8.402_p06: 20′59″ This isn't a bug in dev-java/openjdk. I face this same bug while emerging =hwinfo-23.2-r1. Note that it was the first time hwinfo was being emerged in that system. My guess is that qlop -r fails when there's no records in the emerge log for the package being emerged. I'll conduct tests and open a separate bug against app-portage/portage-utils if I can later reproduce this behavior. Title changed stable sci-physics/geant-4.11.2.0 isn't reported here. (In reply to CaptainBlood from comment #8) > stable sci-physics/geant-4.11.2.0 isn't reported here. It's not really anything to do with stable or not if it's a bug in portage-utils. I would really let Zucca do their testing first. I renamed my emerge.log and then test emerged firefox and 'qlop -r' showed that firefox was being emerged and correctly gave "unkown" ETA. This test was done with =app-portage/portage-utils-0.96.1 So far I haven't been able to reproduce the bug. The machine where I did encounter this bug while emerging =hwinfo-23.2-r1 is now in the middle of recompiling some packages. Meanwhile I tried to reproduce the bug on my laptop, but got the same result as with firefox. I'll try to reproduce the bug on the machine where I encountered it first as soon as I can, but my earlier guess of no records on emerge.log causing the bug seem to be wrong. Well... I've ran the test on the original box where I managed 'qlop -r' to print nothing while hwinfo was being compiled. However I'm (still) unable to reproduce the behavior. Note that I ran 'qlop -r' using 'watch'. Few _wild_ guesses: - some depency changed in the 'emerge queue' before it was hwinfo's turn - some package install changed some env.d file and chenges were not propagated into qlop being executed Whatever caused this must need some quite rare, conditions. |
In contrary of dev-java/openjdk:{11,17,21} which are properly reported. Reproducible: Always