-
Notifications
You must be signed in to change notification settings - Fork 75
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
Alpine build (musl) fails on determinism checks #707
Comments
CC @pepedocs |
Alpine build is now provided by our Dockerfile |
ExactOutput failing also on Arm (on Alpine using musl C)
So apparently our C++-fu is not yet 100% deterministically secure. |
With a great deal of difficulty... I first located the point (the cycle number) when they started to diverge. Then I inserted debug trace statements to try and identify the function in which they diverged in that cycle number (actually it turned out to be in the previous cycle). Lots of debug trace statements into a log file and performed a diff. Then I had some good luck in that I hit on the cause. |
hmm.. this will be pain, could be a bug in libstdc, compiler,... I'm not sure how far do we want to pursue the multiplatform deterministic builds (well, identical builds, we could just have "deterministic results per platform") I suspect the problem in glibc/musl C, as the same err happens on amd64/arm64 on musl |
With #736 all tests (incl. determinism) are passing on CI for MUSL (added its custom results), but the results are not the same for GLIBC and MUSL libc. |
I have briefly tested Alpine build on Docker (alpine:amd64-latest-stable) and
SpatialPoolerTest.ExactOutput
Related #659
The text was updated successfully, but these errors were encountered: