On Tue, May 19, 2015 at 12:06:48PM -0400, RD Thrush wrote: > I realize dpb is undergoing rapid development so if the following anomaly is > old news, please disregard. > > Using -current(amd64) dpb and multiple chrooted remote hosts, I notice that > rerunning some failed jobs result in success while others still fail. > > In my partial build, the following jobs failed (dpb still running): > multimedia/gstreamer-0.10/plugins-base > graphics/clutter/core > x11/gnome/gedit > x11/kde/games3 > x11/gnome/libcryptui > x11/gnome/gvfs > x11/xfce4/xfce4-panel > > I saved the log and lockfile and reran each by removing their lockfile. > 3 failed again but the following succeeded: > multimedia/gstreamer-0.10/plugins-base > graphics/clutter/core > x11/gnome/gedit > x11/xfce4/xfce4-panel > > Why did reruns succeed? Or, better yet, why did the original job fail? I > will have full dpb logs once the dpb run completes if useful to help analyze.
This is fairly unlikely to be linked to dpb development. There's some random aspect to the first runs of dpb, and it tends to catch "hidden" dependencies. Keep in mind that while you build, other jobs may pkg_delete stuff that's not explicitly declared as run-dependencies... This happens routinely in bulk-builds. If you were doing a "fresh" run with no previous stats, you're very likely to have hit some new ones.
