| 1 |
On Thursday 30 November 2006 07:56, Vladimir G. Ivanovic wrote: |
| 2 |
|
| 3 |
> Let's take a poll. |
| 4 |
> |
| 5 |
> 1. Have you seen this error message in an emerge? |
| 6 |
|
| 7 |
Yes, several times. |
| 8 |
|
| 9 |
> 2. Have you subsequently identified a hardware problem, fixed the |
| 10 |
> hardware problem, and have not seen the message since? |
| 11 |
|
| 12 |
Yes. 99% of the times it was bad RAM (verified with memtest86). |
| 13 |
Of course, for trivial emerges a subsequent emerge completed fine, but |
| 14 |
the first failure put me on the alert. |
| 15 |
|
| 16 |
> 3. Have you re-run the emerge and not seen the message in a while |
| 17 |
> (please indicate how long "a while" is.) |
| 18 |
|
| 19 |
For me, "a while" is "since fixing the hardware problem". |
| 20 |
|
| 21 |
> BTW, do you know portage/emerge/make/whatever knows that the problem |
| 22 |
> is not reproducible? |
| 23 |
|
| 24 |
If, all other things being equal, a subsequent attempt at the same |
| 25 |
operation does not exhibit the problem, or fails differently, there's a |
| 26 |
good chance that the problem is not reproducible. |
| 27 |
-- |
| 28 |
gentoo-user@g.o mailing list |
Archives