On 11/2/19 6:54 PM, Santiago Vila wrote: > retitle 908862 neutron: FTBFS randomly (failing tests) > thanks > > Dear Thomas: Please don't put my name in the bug title like you did. > That's a gross mischaracterization of what's really happening.
I initially wrote "Santiago Vila + reproducible build" though it got cut at the plus ... :/ Sorry for this. > I believe this is a race condition of some sort. You can probably > reproduce the failure in your laptop by doing this: > > taskset -c 0 dpkg-buildpackage -uc -us -A > > I hope this should finally make moreinfo and unreproducible not to > apply anymore. I need to repair openvswitch first, as since it's missing, neutron build-dep can't be installed (I managed to break it, somehow...). > Disabling the tests in debian/rules if a single CPU is detected would > probably help, but, as I've shown, the problem is not limited to > single-CPU systems. I would bet that this also fails in your system > if you try enough times, but we might better stop here and let upstream > do their job at finding a proper fix. > > For the Debian package, I would just disable the failing tests, as > they do not seem to be trusted. Disabling tests is really not what I want to do. These tests are catching real world issues, and I do need to detect the problems. Thomas Goirand (zigo)
