tags 835107 - moreinfo unreproducible severity 835107 serious thanks On Sat, 25 Feb 2017, Daniel Schepler wrote:
> On Sun, Jan 8, 2017 at 11:57 AM, Balint Reczey <bal...@balintreczey.hu> wrote: > > The package builds fine for me in sbuild. The issue may be specific to > > pbuilder/local configuration or is gone. > > > > Is the build still failing for you? > > I just tried it 10 times in a row, and it failed 2 of those times. Hi. Two years later, this is now failing for me since 2018-12-22 (using sbuild) all the time in buster: Status: successful libpthread-workqueue_0.9.1-1_amd64-20181008T225156Z Status: successful libpthread-workqueue_0.9.1-1_amd64-20181019T222807Z Status: successful libpthread-workqueue_0.9.1-1_amd64-20181130T125351Z Status: successful libpthread-workqueue_0.9.1-1_amd64-20181210T191003.426Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20181222T101429.311Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20181225T195645.010Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20181225T195649.094Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20181225T200045.285Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20181226T205914.785Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20190114T030911.386Z Status: failed libpthread-workqueue_0.9.1-1_amd64-20190206T104525.863Z [...] and it's also making reproducible-builds autobuilders (using pbuilder) to hang in unstable since 2018-12-09: https://tests.reproducible-builds.org/debian/history/libpthread-workqueue.html So I bet that this should now be easy to reproduce for everybody, but if not, please contact me privately and I will gladly offer ssh access to a machine where it happens all the time. Thanks.
