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
This may not be important, but it looks a bit spicy:
Running target/debug/deps/brotli-69525ecfc53fa34c
running 93 tests
1 Iterations; Time 0.002088729
test integration_tests::test_10x_10y_one_out_byte ... ok
1 Iterations; Time 0.002077081
test integration_tests::test_10x_10y_byte_by_byte ... ok
thread 'integration_tests::test_10x_10y' has overflowed its stack
fatal runtime error: stack overflow
thread 'integration_tests::test_64x' has overflowed its stack
fatal runtime error: stack overflow
1 Iterations; Time 0.625489011
test integration_tests::test_alice1 ... ok
thread 'integration_tests::test_alice29' has overflowed its stack
fatal runtime error: stack overflow
thread 'integration_tests::test_1024k' has overflowed its stack
fatal runtime error: stack overflow
test integration_tests::test_1024k ... test integration_tests::test_1024k has been running for over 60 seconds
test integration_tests::test_10x_10y ... test integration_tests::test_10x_10y has been running for over 60 seconds
test integration_tests::test_64x ... test integration_tests::test_64x has been running for over 60 seconds
test integration_tests::test_alice29 ... test integration_tests::test_alice29 has been running for over 60
Poking at the instance with strace shows one process waiting with
futex(5fe7288da9c, FUTEX_WAIT_PRIVATE, 0, NULL
And its parent is doing
wait4(17733,
So there seems to be some sort of thread mess happening.
( NB: in case you wonder why the checksum changed, the first one was built with --features 'seccomp', and the second was with an added --no-default-features just in case std or something was to blame )
This may not be important, but it looks a bit spicy:
Poking at the instance with strace shows one process waiting with
And its parent is doing
So there seems to be some sort of thread mess happening.
And annoyingly, when you invoke the program with
It panics after printing:
And you get a nice notice in dmesg:
Running with strace and --test-threads=2 gives this:
strace -f target/debug/deps/brotli-2390a973bcc44b8e --test-threads=2
Failing binary attached
brotli-2390a973bcc44b8e.gz
The text was updated successfully, but these errors were encountered: