-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test failures in i386 #3665
Comments
I think the CPU is messing with the NaN values. Do we even support 32bit for 2.0? Given we're mmapping, the address space would be too small. |
|
At least it seems to work in other 32 bit arches, like armel: https://buildd.debian.org/status/package.php?p=prometheus |
|
I'd suspect a floating point issue here, something is changing the signalling NaN to a quiet NaN. Prometheus isn't going to be very useful on a 32bit machine. |
|
If you guys decide to stop supporting 32 bits at all, please let me know, as I should request removal from the archive for all these arches. |
|
@fabxc We don't support 2.0 for 32-bit, right? |
|
Not really. So far we said "if it runs, it runs" but no guarantees or
effort beyond that from our side.
…On Mon, Jan 8, 2018 at 7:05 PM Brian Brazil ***@***.***> wrote:
@fabxc <https://github.com/fabxc> We don't support 2.0 for 32-bit, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3665 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEuA8inVVd_KSqF6xq9v1IhNHz3NfaQUks5tIljRgaJpZM4RWq9y>
.
|
|
Well, at least for i386 it is not working at all. I will ask the Debian ftp-masters to remove that arch. In any case, are you guys sure this is not a hidden bug somewhere? |
|
I would guess that the value is being passed through the FPU at some point, which it shouldn't be. |
|
Hello from the bug scrub. We doubt that anyone will ever look into this issue, so we are closing it. As a side note, it would be interesting if this test failure actually still happens. (Maybe it was a problem in the Go runtime or we changed the relevant code in the last 6 years?) |
Hi,
Prometheus 2.0 entered Debian a few days ago, and it passes tests correctly in most architectures, except for i386. I checked it is using the exact same versions of packages as amd64.
Looking at the build logs, it seems to me it is an issue with staleness calculations, as I see NaNs where there should be numbers, and viceversa.
The full log is here: https://buildd.debian.org/status/fetch.php?pkg=prometheus&arch=i386&ver=2.0.0%2Bds3-1&stamp=1515102582&raw=0
The relevant errors are as follows:
The text was updated successfully, but these errors were encountered: