Bug 62210
Summary: | Anaconda gets time to completion wrong | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | Jeremy Sanders <jss> |
Component: | anaconda | Assignee: | Michael Fulbright <msf> |
Status: | CLOSED WONTFIX | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | skipjack-beta1 | CC: | billc |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-03-28 14:17:00 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jeremy Sanders
2002-03-28 14:16:55 UTC
The time is only an estimate and is roughly correct once enough packages have been installed to smooth out differnces between large and small package install times. I think there is still a bug in the time estimation code. The time doesn't settle down after a few packages, but just continually increases. This didn't happen with RedHat 6. I'll have to do some timing tests to be sure. Similar experience here with FTP install on a laptop ... it consistently starts out with about half the right amount and steadily builds up. It is an issue; you get excited, and then disappointed. If it started off showing a larger value, you think "I'll go make a cup of tea" (or fetch a Molson, if your name's Mike Harris :o) Perhaps something could be done to alleviate this? I remember many versions back a hard-drive install consistently *over*-estimated to begin with. |