Skip to content

Multiprocessing Test Issue - signal.set_wakeup_fd errors #6700

@terryluan12

Description

@terryluan12

Summary

When running the test_multiprocessing_* suite, there are differences in test output that, while not impeding the tests, are output while running the suite, but are in CPython.

Details

For some tests, this error is popping up:

Exception ignored in: <function on_fork at 0x5607124ce900>
Exception ignored in: <function on_fork at 0x5607124ce900>
Exception ignored in: <function on_fork at 0x5607124ce900>
  File "RustPython/crates/pylib/Lib/asyncio/events.py", line 880, in on_fork
    signal.set_wakeup_fd(-1)
                          ^
ValueError: signal only works in main thread
  File "RustPython/crates/pylib/Lib/asyncio/events.py", line 880, in on_fork
    signal.set_wakeup_fd(-1)
                          ^
ValueError: signal only works in main thread
  File "RustPython/crates/pylib/Lib/asyncio/events.py", line 880, in on_fork
    signal.set_wakeup_fd(-1)
                          ^
ValueError: signal only works in main thread

These tests include (but are not limited to):

  • test.test_multiprocessing_fork.test_manager.WithManagerTestPool.test_async_timeout
  • test.test_multiprocessing_fork.test_manager.WithManagerTestPool.test_empty_iterable
  • test.test_multiprocessing_fork.test_manager.WithManagerTestPool.test_map_no_failfast
  • test.test_multiprocessing_fork.test_manager.WithManagerTestPool.test_terminate
  • test.test_multiprocessing_fork.test_manager.WithManagerTestPool.test_wrapped_exception

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions