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/3364
forwarded 822325 https://github.com/rust-lang/rust/pull/33640
thanks
On Saturday, May 14, 2016 02:52:55 PM Santiago Vila wrote:
>
> In both cases the problem went away by setting
> DefaultTasksMax=infinity in /etc/systemd/system.conf.
Good catch! I was aware of it, but didn't come to my mind in
close 822325
severity 822325 important
affects 823530 rustc
thanks
> This looks like an artifact due to your build environment,
> [...]
>
> this looks like just some test instability on an emulated environment,
> [...]
I really think this was not the case here, as I have now a more than
likely
severity 822325 minor
tags 822325 + moreinfo
thanks
On Sat, 23 Apr 2016 14:33:48 +0200 (CEST) Santiago Vila
wrote:
> This package currently fails to build from source in stretch.
>
> --
> executing x86_64-unknown-linux-gnu/test/run-pass/tcp-stress.stage2
Package: src:rustc
Version: 1.8.0+dfsg1-1
Severity: serious
Dear maintainer:
This package currently fails to build from source in stretch.
--
executing
x86_64-unknown-linux-gnu/test/run-pass/tcp-stress.stage2-x86_64-unknown-linux-gnu
--stdout---
5 matches
Mail list logo