You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running the randomized jn tests of our lib against musl the following was produced
'INPUT: [140, 4603707074953425158] EXPECTED: [24658263201] ACTUAL 0.0'
However, since the test data is randomly generated, the following build batch didn't generate that particular input and then passed. So there's some sort of small edge case lurking in there.
The bug was discovered during #224, but since we re-started the build I guess it cleared the log that contained the failure and overwrite it with the restarted build log.
The text was updated successfully, but these errors were encountered:
When running the randomized
jn
tests of our lib against musl the following was producedHowever, since the test data is randomly generated, the following build batch didn't generate that particular input and then passed. So there's some sort of small edge case lurking in there.
The bug was discovered during #224, but since we re-started the build I guess it cleared the log that contained the failure and overwrite it with the restarted build log.
The text was updated successfully, but these errors were encountered: