Skip to content

test(lib): fix SIGSEGV on x86_64-unknown-linux-gnu targets#29794

Merged
nathanwhit merged 1 commit intodenoland:mainfrom
limwa:fix/sigsegv-unit-tests
Jun 18, 2025
Merged

test(lib): fix SIGSEGV on x86_64-unknown-linux-gnu targets#29794
nathanwhit merged 1 commit intodenoland:mainfrom
limwa:fix/sigsegv-unit-tests

Conversation

@limwa
Copy link
Contributor

@limwa limwa commented Jun 17, 2025

Fixes #29793.

This PR reapplies #22152 (see issue for further details).

Changes deno_core in tests to be built with the unsafe_use_unprotected_platform feature.

The issue is caused by two or more threads (in Deno's test suite, tests are spread out across worker threads) in the same process accessing v8's isolates (see denoland/deno_core#471 for further details).

@CLAassistant
Copy link

CLAassistant commented Jun 17, 2025

CLA assistant check
All committers have signed the CLA.

@limwa limwa force-pushed the fix/sigsegv-unit-tests branch from 1a32b04 to b99a81f Compare June 17, 2025 21:48
@limwa limwa changed the title fix: SIGSEGV in unit tests on x86_64-unknown-linux-gnu targets test(lib): fix SIGSEGV on x86_64-unknown-linux-gnu targets Jun 17, 2025
Copy link
Member

@nathanwhit nathanwhit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@nathanwhit nathanwhit merged commit 9dd0e9a into denoland:main Jun 18, 2025
18 checks passed
chrono = { workspace = true, features = ["now"] }
deno_bench_util.workspace = true
deno_cache_dir.workspace = true
deno_core = { workspace = true, features = ["unsafe_use_unprotected_platform"] }
Copy link
Member

@dsherret dsherret Jun 18, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This dependency isn't used by the tests crate. I'll do a follow-up pr to fix this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should it have gone into the dev_dependencies in cli/Cargo.toml?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that's what I did in #29806 which should cause the other crates to be built with that feature enabled without adding a dependency to deno_core for the tests crate.

dsherret added a commit that referenced this pull request Jun 18, 2025
…29806)

The tests crate doesn't have a dependency on deno_core.

Amendment to #29794
CyanChanges pushed a commit to CyanChanges/deno that referenced this pull request Jun 23, 2025
…29794)

Fixes denoland#29793.

This PR reapplies denoland#22152 (see issue
for further details).

Changes `deno_core` in tests to be built with the
`unsafe_use_unprotected_platform` feature.

The issue is caused by two or more threads (in Deno's test suite, tests
are spread out across worker threads) in the same process accessing v8's
isolates (see denoland/deno_core#471 for further
details).
CyanChanges pushed a commit to CyanChanges/deno that referenced this pull request Jun 23, 2025
…enoland#29806)

The tests crate doesn't have a dependency on deno_core.

Amendment to denoland#29794
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SIGSEGV when running cargo test --lib on x86_64-unknown-linux-gnu

4 participants