Skip to content
This repository has been archived by the owner on May 4, 2018. It is now read-only.

Threadpool related crashes on OSX #637

Closed
saghul opened this issue Nov 29, 2012 · 1 comment
Closed

Threadpool related crashes on OSX #637

saghul opened this issue Nov 29, 2012 · 1 comment

Comments

@saghul
Copy link
Contributor

saghul commented Nov 29, 2012

Every test relying on the thread pool seems to fail on OSX now, 24 of them:

=============================================================
[%   5|+  10|-   0]: consumer_producer
`consumer_producer` failed: timeout
Output from process `consumer_producer`:
finished_consumers: 31
Assertion failed in test/test-condvar-consumer-producer.c on line 87: finished_consumers == MAX_CONSUMERS
=============================================================
[%  44|+  76|-   1]: fs_poll_ref
`fs_poll_ref` failed: exit code 134
Output from process `fs_poll_ref`: (no output)
=============================================================
[%  59|+ 102|-   2]: process_title
`process_title` failed: exit code 134
Output from process `process_title`:
Assertion failed in test/test-process-title.c on line 35: UV_OK == err.code
=============================================================
[%  62|+ 106|-   3]: getaddrinfo_basic
`getaddrinfo_basic` failed: exit code 134
Output from process `getaddrinfo_basic`: (no output)
=============================================================
[%  62|+ 106|-   4]: getaddrinfo_concurrent
`getaddrinfo_concurrent` failed: exit code 134
Output from process `getaddrinfo_concurrent`: (no output)
=============================================================
[%  74|+ 125|-   5]: fs_poll
`fs_poll` failed: exit code 134
Output from process `fs_poll`: (no output)
=============================================================
[%  77|+ 130|-   6]: fs_file_noent
`fs_file_noent` failed: exit code 134
Output from process `fs_file_noent`: (no output)
=============================================================
[%  78|+ 130|-   7]: fs_file_nametoolong
`fs_file_nametoolong` failed: timeout
Output from process `fs_file_nametoolong`: (no output)
=============================================================
[%  78|+ 130|-   8]: fs_file_loop
`fs_file_loop` failed: timeout
Output from process `fs_file_loop`: (no output)
=============================================================
[%  79|+ 130|-   9]: fs_file_async
`fs_file_async` failed: timeout
Output from process `fs_file_async`: (no output)
=============================================================
[%  80|+ 131|-  10]: fs_async_dir
`fs_async_dir` failed: timeout
Output from process `fs_async_dir`: (no output)
=============================================================
[%  81|+ 131|-  11]: fs_async_sendfile
`fs_async_sendfile` failed: timeout
Output from process `fs_async_sendfile`: (no output)
=============================================================
[%  81|+ 131|-  12]: fs_fstat
`fs_fstat` failed: timeout
Output from process `fs_fstat`: (no output)
=============================================================
[%  82|+ 131|-  13]: fs_chmod
`fs_chmod` failed: timeout
Output from process `fs_chmod`: (no output)
=============================================================
[%  82|+ 131|-  14]: fs_chown
`fs_chown` failed: timeout
Output from process `fs_chown`: (no output)
=============================================================
[%  83|+ 131|-  15]: fs_utime
`fs_utime` failed: exit code 134
Output from process `fs_utime`: (no output)
=============================================================
[%  84|+ 131|-  16]: fs_futime
`fs_futime` failed: timeout
Output from process `fs_futime`: (no output)
=============================================================
[%  84|+ 131|-  17]: fs_readlink
`fs_readlink` failed: timeout
Output from process `fs_readlink`: (no output)
=============================================================
[%  85|+ 131|-  18]: fs_symlink
`fs_symlink` failed: exit code 134
Output from process `fs_symlink`: (no output)
=============================================================
[%  92|+ 143|-  19]: fs_readdir_empty_dir
`fs_readdir_empty_dir` failed: timeout
Output from process `fs_readdir_empty_dir`: (no output)
=============================================================
[%  93|+ 143|-  20]: fs_readdir_file
`fs_readdir_file` failed: exit code 134
Output from process `fs_readdir_file`: (no output)
=============================================================
[%  93|+ 143|-  21]: fs_open_dir
`fs_open_dir` failed: timeout
Output from process `fs_open_dir`: (no output)
=============================================================
[%  94|+ 144|-  22]: threadpool_queue_work_simple
`threadpool_queue_work_simple` failed: timeout
Output from process `threadpool_queue_work_simple`: (no output)
=============================================================
[%  96|+ 145|-  23]: threadpool_multiple_event_loops
`threadpool_multiple_event_loops` failed: timeout
Output from process `threadpool_multiple_event_loops`: (no output)
=============================================================
[% 100|+ 151|-  24]: Done.
make: *** [test] Error 24

Here is the backtrace of a crash I caught on pyuv: https://gist.github.com/4167503

@bnoordhuis
Copy link
Contributor

Thanks, silly bug fixed in 2be240d.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants