tests: the emit-obj corpus test shares one temp directory, so two runs at the same time fail
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with the_backend_corpus_emits_object_files in tests/integration_test/emit_obj_produces_objects.rs. It writes every object into the fixed path std::env::temp_dir()/vx_emit_obj_gate and deletes the previous file before each compile, so concurrent runs collide. Reproduce by running the test in two checkouts at once. Done when each run uses its own directory (a tempfile::TempDir or a name that includes std::process::id()) and the concurrent runs both pass.
Written by the indexing model from the issue text.
Description
the_backend_corpus_emits_object_files in tests/integration_test/emit_obj_produces_objects.rs writes each object to one fixed directory, std::env::temp_dir()/vx_emit_obj_gate. Before each compile, it deletes that object file. Two checkouts that run the test at the same time use the same directory. So one run can delete the object of the other run, and the other run then reports ".vx: no object" for a file that compiles.
On 2026-11-14, three worktrees ran the pre-commit hook at the same time. The test failed in two of them, on bitwise_operators.vx and book_errors_question_mark.vx. Each file compiled to an object when the test ran alone, and each hook passed when it ran again.
Fix: give each run its own directory, for example a tempfile::TempDir, or a name that includes std::process::id().
Generated With Claude Code
- Dominant language
- Rust
- Stars
- 35
- Forks
- 5
- Avg merge
- 12h 26m
- Merged PRs (30d)
- 799
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from vx-lang/Vx
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
`pub struct` gives "Expected 'fn' after 'pub'": the error should say that a struct needs no `pub`Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug devex
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug stdlib
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
longbridge/gpui-kit#4031 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
neuralmagic/crucible#465 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
compiler P3
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
HerringtonDarkholme/hd-lang#2162 ·
Maintainers usually reply within 1 day
-
embedded SQL: pin correlated-guard behaviour when a closed variable is reassigned inside a branchOpenpriority: low
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
jonathanong/no-mistakes#3627 ·
Maintainers usually reply within 1 day