-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Intermittent failure in replcompletions test #10875
Comments
I first saw this when testing the tupopocalypse branch on my Mac on c3bbbb3, but I couldn't reproduce it. Was that the first sighting? Perhaps I should have said something then. |
Found a reduced set of tests for this (also on win32), and it looks like whatever's causing this is probably the same underlying bug as what's causing the other two new failures since the tuple merge. Type comparison to I added Lines 367 to 368 in a49ae53
and I get the following:
@JeffBezanson I wonder if maybe SimpleVector is getting mixed up with |
7ec501d is a possible fix. |
Apparently not, bummer https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.4054/job/6apo08twe807nxbl |
The failures we've seen seem to indicate at least two bugs. @vtjnash & I fixed a definite bug in the type cache, but there have also been assertion failures that seem more like memory corruption. The failure described in this issue could be a third bug. |
@vtjnash I checked the ordering of entries in Array's cache. Everything is fine on startup, and then after running core.jl there are many pairs of mis-ordered entries. I tried using only object_id and never dt->uid in typekey_compare and the problem went away. I'm not totally sure why this happens. I don't believe a uid ever changes. |
my 32 bit dockerfile running at commit 5e99f74 reproduces this on my machine, if there's anything you want me to try |
- add a linearly-searched part of the type cache for more difficult types - assign UIDs earlier so they can't change after cache insertion
let's call this tentatively fixed by b993658 and reopen if it happens again |
- add a linearly-searched part of the type cache for more difficult types - assign UIDs earlier so they can't change after cache insertion
…0875) - add a linearly-searched part of the type cache for more difficult types - assign UIDs earlier so they can't change after cache insertion
from https://travis-ci.org/JuliaLang/julia/jobs/59003679, commit 3abc13e on 64 bit Linux
other occurrences:
http://buildbot.e.ip.saba.us:8010/builders/build_ubuntu12.04-x86/builds/1176/steps/shell_2/logs/stdio
http://buildbot.e.ip.saba.us:8010/builders/build_ubuntu14.04-x86/builds/1118/steps/shell_2/logs/stdio
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3896/job/riq6yjykne09kt02
http://buildbot.e.ip.saba.us:8010/builders/build_ubuntu14.04-x64/builds/1166/steps/shell_2/logs/stdio
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3906/job/vjlfoq2r2stpb3dn
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3917/job/egkj811th386i2lo
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3919/job/ows2ywtlbq36o2yd
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3920/job/oo3t5vlxqdns34a4
http://buildbot.e.ip.saba.us:8010/builders/build_ubuntu12.04-x86/builds/1178/steps/shell_2/logs/stdio
http://buildbot.e.ip.saba.us:8010/builders/build_ubuntu12.04-x86/builds/1181/steps/shell_2/logs/stdio
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3924/job/1av04y9419v0tjcc
https://travis-ci.org/JuliaLang/julia/jobs/59102646
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3939/job/4n4h7uyvyt2xdb7s
https://ci.appveyor.com/project/StefanKarpinski/julia/build/1.0.3941/job/y8mcyorudtpb7x99
(I think you get the point)
The text was updated successfully, but these errors were encountered: