Bug 651376

Summary:	app-portage/genlop not handling interruptions (suspend, hibernate etc) of emerge process
Product:	Portage Development	Reporter:	chaoscommander <40cb58f5>
Component:	Tools	Assignee:	Portage Tools Team <tools-portage>
Status:	UNCONFIRMED ---
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=441672
Whiteboard:
Package list:		Runtime testing required:	---

Description chaoscommander 2018-03-24 18:49:46 UTC

I often stretch out 'emerge world' or large compilations across multiple sessions on my computer (as in, I freeze the emerge process using CTRL+Z or put the machine into suspend/hibernate). genlop doesn't account for such interruptions, leading to completely unusable predictions. Large packages on my system usually have an ETA in the 10s of hours or even multiple days if I often pause their merge due to its execution time, when really they just need a few hours to complete. I know that this is due to the fact that emerge.log doesn't care about suspend/hibernate and stuff. But maybe genlop could, in some way?

Reproducible: Always

Steps to Reproduce:
1. emerge something big, like Firefox or qtwebengine or...
2. hit ctrl+z and/or suspend machine
3. wait until next day
4. bg or fg
5. genlop -c
Actual Results:  
current merge time is actual clock time passed since merge began

Expected Results:  
current merge time should show time the merge process was actively running