You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux 3.14.35-28.38.amzn1.x86_64 SSL #1 SMP Wed Mar 11 22:50:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
wrk @ a209691
I’m using the hello-world example from the examples dir. This only happens with release builds, and it only happens after a number of successful requests (~12,000+):
thread '<unnamed>' panicked at 'Vec::reserve: `usize` overflow', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libcore/option.rs:332
thread '<unnamed>' panicked at 'child thread None panicked', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/thread/mod.rs:797
thread '<main>' panicked at 'child thread None panicked', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/thread/mod.rs:797
The text was updated successfully, but these errors were encountered:
Linux 3.14.35-28.38.amzn1.x86_64 SSL #1 SSL #1 SMP Wed Mar 11 22:50:37
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
wrk @ a209691
I’m using the hello-world example from the examples dir. This only
happens with release builds, and it only happens after a number of
successful requests:
thread '' panicked at 'Vec::reserve: usize overflow', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libcore/option.rs:332
thread '' panicked at 'child thread None panicked', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/thread/mod.rs:797
thread '
' panicked at 'child thread None panicked', /home/rustbuild/src/rust-buildbot/slave/nightly-dist-rustc-linux/build/src/libstd/thread/mod.rs:797
—
Reply to this email directly or view it on GitHub #412.
I’m using the hello-world example from the
examples
dir. This only happens with release builds, and it only happens after a number of successful requests (~12,000+):The text was updated successfully, but these errors were encountered: