[Pkg-rust-maintainers] Bug#822325: Bug#822325: rustc: FTBFS in testing: test fail

Santiago Vila sanvila at unex.es
Mon May 16 11:36:04 UTC 2016

On Sat, 14 May 2016, Luca BRUNO wrote:

> I just reproduced it via `systemd-run --scope -p TasksMax=512
> ./tcp-stress`.  Part of it is due to the tcp-stress test not
> checking for spawned thread, I've just submitted a PR to make that
> failure explicit: https://github.com/rust-lang/rust/pull/33640

Thanks a lot! Even if this is officially more a bug in systemd than a
bug in rustc, it's always a good thing that error messages are helpful
and explain what's the problem.

> If your sbuild is running as a daemon or in any other dedicated way, I think 
> you should ask for its TasksMax setting to be increased.

Yes, or just wait for syetemd 229-6 to enter testing.

The old default for TasksMax was not good for everybody (this FTBFS
problem is an example) so they have set it to infinity in systemd.

So I did the same in my hand-made autobuilder (which is triggered by
cron) to avoid this happening again.


More information about the Pkg-rust-maintainers mailing list