Skip to content

Commit 6b9719f

Browse files
authored
Fix an intermittent test failure in core test (#55973)
The test wants to assert that `Module` is not resolved in `Main`, but other tests do resolve this identifier, so the test can fail depending on test order (and I've been seeing such failures on CI recently). Fix that by running the test in a fresh subprocess.
1 parent be40163 commit 6b9719f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

test/core.jl

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1183,7 +1183,7 @@ end
11831183

11841184
# Make sure that `Module` is not resolved to `Core.Module` during sysimg generation
11851185
# so that users can define their own binding named `Module` in Main.
1186-
@test !Base.isbindingresolved(Main, :Module)
1186+
@test success(`$(Base.julia_cmd()) -e '@assert !Base.isbindingresolved(Main, :Module)'`)
11871187

11881188
# Module() constructor
11891189
@test names(Module(:anonymous), all = true, imported = true) == [:anonymous]

0 commit comments

Comments
 (0)