[Bug debuginfod/25394] groom vs. scan race condition

2020-01-20 Thread fche at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=25394 Frank Ch. Eigler changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

Buildbot failure in Wildebeest Builder on whole buildset

2020-01-20 Thread buildbot
The Buildbot has detected a failed build on builder whole buildset while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/11/builds/417 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: fedora-ppc64le Build Reaso

Buildbot failure in Wildebeest Builder on whole buildset

2020-01-20 Thread buildbot
The Buildbot has detected a failed build on builder whole buildset while building elfutils. Full details are available at: https://builder.wildebeest.org/buildbot/#builders/1/builds/462 Buildbot URL: https://builder.wildebeest.org/buildbot/ Worker for this Build: centos-x86_64 Build Reason:

Re: PR25394 patch: debuginfod groom vs. scan race condition

2020-01-20 Thread Mark Wielaard
Hi Frank, On Mon, 2020-01-20 at 12:10 -0500, Frank Ch. Eigler wrote: > > Nice work. And I think I almost understand it. I am just a little > > confused about thread_main_fts_source_paths also being an "idler": > > Yup, it's a bit subtle. > > > > while (! interrupted) > > > { > > > -

Re: PR25394 patch: debuginfod groom vs. scan race condition

2020-01-20 Thread Frank Ch. Eigler
Hi - > Nice work. And I think I almost understand it. I am just a little > confused about thread_main_fts_source_paths also being an "idler": Yup, it's a bit subtle. > > while (! interrupted) > > { > > - set_metric("thread_timer", "role","traverse", rescan_timer); > > - // set_

Re: PR25394 patch: debuginfod groom vs. scan race condition

2020-01-20 Thread Mark Wielaard
Hi Frank, On Sun, 2020-01-19 at 20:43 -0500, Frank Ch. Eigler wrote: > This was a doozie. As the commit text hints, I haven't found a way > of > testing this on an elfutils/tests snack-sized data set (except perhaps > by injecting long sleeps?), but the changes work on the larger > archives such