On 08/02/18 05:25, Andreas Tille wrote: > > I can confirm that the problem is somehow randomized. I tried the > following patch which sometimes helps for non-reproducable issues > > $ git diff > diff --git a/debian/rules b/debian/rules > index 6b7ed6a..e677071 100755 > --- a/debian/rules > +++ b/debian/rules > @@ -21,7 +21,7 @@ override_dh_clean: > > override_dh_auto_test: > mkdir -p $(BUILDHOME) > - HOME=$(BUILDHOME) dh_auto_test > + HOME=$(BUILDHOME) dh_auto_test --no-parallel > > %: > dh $@ --buildsystem=cmake >
The no parallel is good idea. Thanks, I added it to the package. > > but this just led to a different problem: > > ... > [ RUN ] WorkerPool.ThingsRunInParallel > /build/ignition-common-1.0.1/src/WorkerPool_TEST.cc:136: Failure > Value of: pool.WaitForResults(time) > Actual: false > Expected: true > /build/ignition-common-1.0.1/src/WorkerPool_TEST.cc:137: Failure > Expected: 2 > To be equal to: sentinel > Which is: 1 > [ FAILED ] WorkerPool.ThingsRunInParallel (12 ms) > [----------] 6 tests from WorkerPool (37 ms total) > > [----------] Global test environment tear-down > [==========] 6 tests from 1 test case ran. (37 ms total) > [ PASSED ] 5 tests. > [ FAILED ] 1 test, listed below: > [ FAILED ] WorkerPool.ThingsRunInParallel > > Unfortunately I have no idea how to deal with this. I'd recommend > you ask about this problem at debian-scie...@lists.debian.org and/or > debian-ment...@lists.debian.org. > I've been in contact with upstream and seems like it is a flaky test so they recommend me to disable it since it highly depend on time. I did that: https://salsa.debian.org/science-team/ignition-common/commit/6aa2abd28993a131a99b1004af8c7eccea82cb2e Let me know if this finally works for you or I need to keep working on it. Thanks a lot. -- Jose Luis Rivero <jriv...@openrobotics.org>
