[Fix] Support spawn workers in LiveCodeBench evaluation - #2603
Open
tandede wants to merge 2 commits into
Open
Conversation
tandede
marked this pull request as ready for review
August 20, 2026 08:35
Author
|
Hi maintainers, I’m following up on this PR in case it was missed. Both documentation builds have passed, and the LiveCodeBench spawn-worker support fix is ready for review. Please let me know if any changes or additional validation would be helpful. Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
codegen_check_correctnessdefines its multiprocessing target as a nested function. Process start methods that serialize the target, such asspawn, therefore fail before evaluating any generation withAttributeError: Can't pickle local object. This affects callers that selectspawnexplicitly and platforms where it is the default.Modification
spawn.forkcontext and add a regression test that launches the worker through a realspawnprocess.No public API or behavior changes for existing
forkusers.Local verification:
python -m pytest -q tests/openicl tests/prompt --disable-warnings(67 passed, 2 subtests passed)python -m pytest -q tests/partitioners tests/summarizers tests/evaluator tests/tasks tests/tools tests/utils --disable-warnings(107 passed, 15 subtests passed)python -m pytest -q tests/datasets/test_livecodebench_evaluator.py tests/datasets/test_code_execution.py tests/datasets/test_humaneval.py tests/datasets/test_taco.py --disable-warnings(17 passed, 1 platform-specific skip)flake8,isort,yapf, andcodespellpre-commit hooks passed for the changed files.BC-breaking (Optional)
No.
Checklist
Before PR:
After PR: