Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upTest failure in armel: parser panic: runtime error: integer divide by zero #2058
Comments
This comment has been minimized.
This comment has been minimized.
|
Unfortunately, neither the stack trace nor the test log tell us which query was evaluated when the error occurred. And it's happening only on that platform, I assume. Is there any way to reproduce this locally on x86_64 hardware? (I'm not familiar with the Debian crossbuild environment and how it runs the tests on those platforms. I guess it's some emulated hardware, or do you have the physical hardware hooked up?) |
This comment has been minimized.
This comment has been minimized.
|
Hi! Yes, this is only happening in armel right now. We use real hardware, and I can log in to one of the porter boxes if you want me to try something. |
This comment has been minimized.
This comment has been minimized.
|
The problem here is that the testing code doesn't spit out the expression it was testing if an unexpected panic happens. If the test ran (and failed) on my local machine, I'd insert some Println statements to interactively find out what's going on. But that requires a quick roundtrip. Ideally, we would improve the test to better report in the case of that kind of error. But it looks like a really weird error, quite possible a Go compile issue on that platform. |
brian-brazil
added
the
kind/bug
label
Oct 26, 2016
This comment has been minimized.
This comment has been minimized.
|
This seems to be the failing code block, so it does not make any sense to have a div0 error...
|
This comment has been minimized.
This comment has been minimized.
|
Oh yes, it does. This is actually a real bug. The fact that it only happens on some architectures has to do with rounding precision depending on size of an int or something. Brilliant, I'll have a fix ready in 5m and merge it into 1.2. One more reason to cut 1.2.3. ;-/ |
This comment has been minimized.
This comment has been minimized.
|
I'm pretty sure #2156 solves this. |
beorn7
closed this
Nov 3, 2016
This comment has been minimized.
This comment has been minimized.
|
It did fix it, but immediately I've got a similar issue, also in armel:
|
This comment has been minimized.
This comment has been minimized.
|
yeah, that's when the float overflows the int (it would even overflow int64 here, just coincidence again that it only throws up on a particular architecture). I'll file a separate bug. |
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
TheTincho commentedOct 6, 2016
Hi,
I am getting build failures in armel due to a test failing with an "unexpected error", that turns out to be a division by zero in the parser:
Full test log output: