| Hi Jeen,
Yes I’ve added the benchmarks to jenkins, but not all of them and also only for verification. I had a case a while ago where I managed to break the benchmarks without noticing, so I made a junit test that runs one iteration of each benchmark (except for the particularly slow ones).
I will look at that build, might be a rare race condition type bug in the SHACL engine.
Pretty cool that jenkins doesn’t have any timeouts, shouldn’t it have a 1 hour or maybe 4 hour max runtime before the build is killed?
Håvard
Fwiw I don't know for sure that it's the benchmarks that caused this or something else, it's just the first thing I noticed when looking at the console output. Fingers crossed that the next build goes through normally and this was just a temporary glitch.
Jeen
Havard, can you take a closer look please?
It seems that for some reason, your SHACL benchmarks have suddenly started being picked up and executed by Jenkins.
I don't know if it's something I changed in the config or some change you made, but we need this sorted ASAP, so I'd appreciate any insights :)
Cheers,
Jeen
_______________________________________________ rdf4j-dev mailing list rdf4j-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/rdf4j-dev
|
