Open IainNZ opened 10 years ago
I filed this because it basically means there are still random segfaults with this pacakge even on Julia 0.3.1 - something about this package triggers them that I don't really see in any other package. @JeffBezanson, if you are feeling like digging around in memory, running this until it fails could be fun.
I just ran the tests 8 times on my OSX machine though, with no issues, so ¯(ツ)/¯
... and 8 times on the test machine, no issues... Maybe there is something only triggered by running it in PkgEval
so I ran it on the testing machine like so:
for i = 1:100
@show i
@time run(`timeout 300s ./julia -e 'Pkg.test("Dates")'`)
end
and the following happened
[idunning@che julia03]$ ./julia tester.jl
i => 1
INFO: Testing Dates
INFO: Dates tests passed
INFO: No packages to install, update or remove
elapsed time: 25.481404997 seconds (686340 bytes allocated)
i => 2
INFO: Testing Dates
INFO: Dates tests passed
INFO: No packages to install, update or remove
elapsed time: 25.306174062 seconds (2048 bytes allocated)
i => 3
INFO: Testing Dates
signal (15): Terminated
signal (15): Terminated
syscall at /usr/lib/libc.so.6 (unknown line)
unknown function (ip: -1248907776)
unknown function (ip: -1248851714)
uv__epoll_wait at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
jl_apply_generic at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
uv__io_poll at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
uv_run at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
abstract_call_gf at ./inference.jl:704
jl_apply_generic at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
abstract_call at ./inference.jl:819
jl_apply_generic at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
abstract_eval_call at ./inference.jl:903
abstract_eval at ./inference.jl:935
jl_apply_generic at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
process_events at ./stream.jl:537
abstract_eval_arg at ./inference.jl:866
jl_apply_generic at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
wait at ./task.jl:273
....
unknown function (ip: 4200466)
julia_trampoline at /home/idunning/julia03/usr/bin/../lib/libjulia.so (unknown line)
unknown function (ip: 4199453)
__libc_start_main at /usr/lib/libc.so.6 (unknown line)
unknown function (ip: 4199507)
unknown function (ip: 0)
ERROR: failed process: Process(`timeout 300s ./julia -e 'Pkg.test("Dates")'`, ProcessExited(124)) [124]
in pipeline_error at process.jl:502
in anonymous at no file:3
in include at ./boot.jl:245
in include_from_node1 at loading.jl:128
in process_options at ./client.jl:285
in _start at ./client.jl:354
in _start_3B_1712 at /home/idunning/julia03/usr/bin/../lib/julia/sys.so
while loading /home/idunning/julia03/tester.jl, in expression starting on line 1
So not the same error, but a sign something is wrong. It isn't always the 3rd iteration, but it was the 3rd iteration twice in a row. On another time it was the 6th...
Thanks for digging into this @IainNZ. I've been a little slammed and haven't been able to really dig in myself since the end of the summer. I would appreciate some help if anyone is willing to dig in. The test in question has been disable in Base to prevent travis segfaults. As far as I can tell, the offending method is here.
PackageEvaluator.jl is a script that runs nightly. It attempts to load all Julia packages and run their tests (if available) on both the stable version of Julia (0.3) and the nightly build of the unstable version (0.4). The results of this script are used to generate a package listing enhanced with testing results.
On Julia 0.3
Tests pass.
Tests fail, but package loads.
Tests pass.
means that PackageEvaluator found the tests for your package, executed them, and they all passed.Tests fail, but package loads.
means that PackageEvaluator found the tests for your package, executed them, and they didn't pass. However, trying to load your package withusing
worked.This issue was filed because your testing status became worse. No additional issues will be filed if your package remains in this state, and no issue will be filed if it improves. If you'd like to opt-out of these status-change messages, reply to this message saying you'd like to and @IainNZ will add an exception. If you'd like to discuss PackageEvaluator.jl please file an issue at the repository. For example, your package may be untestable on the test machine due to a dependency - an exception can be added.
Test log: