Jenkins build failed? about class_loader

[eacousineau]

Looks like a similar thing happened here: http://jenkins.ros.org/job/devel-groovy-class_loader/ARCH_PARAM=amd64,UBUNTU_PARAM=precise,label=devel/52/console

[dirk-thomas]

GitHub does not have a 100% availability. Therefore occasionally accessing data from GitHub will fail / time out.

I just retriggered the job and it passed fine.

[eacousineau]

Ah, thanks!
Do you know how long it usually takes for the packages to make into the ros Debian apt repositories?

[dirk-thomas]

The Debian package is scheduled to build into the building repo withing an hour after the release (or later when the buildfarm is busy). After no builds are running anymore for a specific architecture (and no big breakage has happened) the Debians are synced to shadow-fixed. After that it requires manual syncing to public - that can take from hours to several days. It highly depends when "enough" changes have accumulated, no regressions are there and that people have used the packages from shadow-fixed for some time to catch regressions.

[eacousineau]

That makes sense. Thank you for letting me know!
(We were able to resolve an issue with our segfaults by finding the root cause of the warning itself so we're not dependent on this bugfix)