Skip to content

ci(threads): fix multiproces threads forks slow in ci #15263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 14, 2025
Merged

ci(threads): fix multiproces threads forks slow in ci #15263

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion tests/appsec/iast/taint_tracking/test_multiprocessing_tracer_iast_env.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ def _child_check(q: Queue):
q.put({"error": repr(e)})


@pytest.mark.skipif(os.name == "nt", reason="multiprocessing fork semantics differ on Windows")
@pytest.mark.skip(reason="multiprocessing fork doesn't work correctly in ddtrace-py 4.0")
def test_subprocess_has_tracer_running_and_iast_env(monkeypatch):
"""
Verify IAST is disabled in late fork multiprocessing scenarios.
Expand Down
3 changes: 3 additions & 0 deletions tests/appsec/iast/test_fork_handler_regression.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,7 @@ def test_fork_handler_with_active_context(iast_context_defaults):
asm_config._iast_enabled = original_state


@pytest.mark.skip(reason="multiprocessing fork doesn't work correctly in ddtrace-py 4.0")
def test_multiprocessing_with_iast_no_segfault(iast_context_defaults):
"""
Regression test: Verify that late forks (multiprocessing) safely disable IAST.
Expand Down Expand Up @@ -128,6 +129,7 @@ def child_process_work(queue):
assert result[3] is False, "Objects should not be tainted in child (IAST disabled)"


@pytest.mark.skip(reason="multiprocessing fork doesn't work correctly in ddtrace-py 4.0")
def test_multiple_fork_operations(iast_context_defaults):
"""
Test that multiple sequential fork operations don't cause segfaults.
Expand Down Expand Up @@ -266,6 +268,7 @@ def test_fork_handler_clears_state(iast_context_defaults):
asm_config._iast_enabled = original_state


@pytest.mark.skip(reason="multiprocessing fork doesn't work correctly in ddtrace-py 4.0")
def test_eval_in_forked_process(iast_context_defaults):
"""
Regression test: Verify that eval() doesn't crash in forked processes.
Expand Down
2 changes: 2 additions & 0 deletions tests/appsec/iast/test_multiprocessing_eval_integration.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,7 @@ class TestMultiprocessingEvalIntegration:
This reproduces the dd-source test scenario that was causing segfaults.
"""

@pytest.mark.skip(reason="multiprocessing fork doesn't work correctly in ddtrace-py 4.0")
def test_uvicorn_style_worker_with_eval(self):
"""
Simulate a uvicorn-style worker process that performs eval operations.
Expand Down Expand Up @@ -167,6 +168,7 @@ def test_direct_fork_with_eval_no_crash(self):
more_parent_result = eval(more_parent_tainted)
assert more_parent_result == 500

@pytest.mark.skip(reason="multiprocessing fork doesn't work correctly in ddtrace-py 4.0")
def test_sequential_workers_stress_test(self):
"""
Stress test: Multiple workers created sequentially.
Expand Down
Loading