[Bug]: SIGTRAP on Jest v27 + Node 16.9 in GH?

[milesj]

Version

27.1.0

Steps to reproduce

I haven't been able to reproduce this locally, but it fails in GitHub CI:

https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571895050

Expected behavior

It should not fail on a SIGTRAP.

Actual behavior

Jest hard fails in GitHub CI with a SIGTRAP (I've never seen this before).

#
# Fatal error in , line 0
# Check failed: !holder_map.has_named_interceptor().
#
#
#
#FailureMessage Object: 0x7ffe44ff40e0
 1: 0xb691f1  [node]
 2: 0x1bf3094 V8_Fatal(char const*, ...) [node]
 3: 0x10ac4a1 v8::internal::ConcurrentLookupIterator::TryGetPropertyCell(v8::internal::Isolate*, v8::internal::LocalIsolate*, v8::internal::Handle<v8::internal::JSGlobalObject>, v8::internal::Handle<v8::internal::Name>) [node]
 4: 0x1c5aa55  [node]
 5: 0x1c5b9eb v8::internal::compiler::JSGlobalObjectRef::GetPropertyCell(v8::internal::compiler::NameRef const&, v8::internal::compiler::SerializationPolicy) const [node]
 6: 0x1e61ba3 v8::internal::compiler::JSNativeContextSpecialization::ReduceNamedAccess(v8::internal::compiler::Node*, v8::internal::compiler::Node*, v8::internal::compiler::NamedAccessFeedback const&, v8::internal::compiler::AccessMode, v8::internal::compiler::Node*) [node]
 7: 0x1e623c4 v8::internal::compiler::JSNativeContextSpecialization::ReducePropertyAccess(v8::internal::compiler::Node*, v8::internal::compiler::Node*, v8::base::Optional<v8::internal::compiler::NameRef>, v8::internal::compiler::Node*, v8::internal::compiler::FeedbackSource const&, v8::internal::compiler::AccessMode) [node]
 8: 0x1e62f0c v8::internal::compiler::JSNativeContextSpecialization::ReduceJSLoadProperty(v8::internal::compiler::Node*) [node]
 9: 0x1df5e0a v8::internal::compiler::Reducer::Reduce(v8::internal::compiler::Node*, v8::internal::compiler::ObserveNodeManager*) [node]
10: 0x1c92604  [node]
11: 0x1df60be v8::internal::compiler::GraphReducer::Reduce(v8::internal::compiler::Node*) [node]
12: 0x1df7895 v8::internal::compiler::GraphReducer::ReduceTop() [node]

 ERROR

 Failed to execute pipeline. The following errors have occurred:

 Command was killed with SIGTRAP (Debugger breakpoint): jest --coverage --colors
  --logHeapUsage
13: 0x1df7c48 v8::internal::compiler::GraphReducer::ReduceNode(v8::internal::compiler::Node*) [node]
14: 0x1ca03fd v8::internal::compiler::InliningPhase::Run(v8::internal::compiler::PipelineData*, v8::internal::Zone*) [node]
15: 0x1ca1291 v8::internal::compiler::PipelineImpl::CreateGraph() [node]
16: 0x1ca1668 v8::internal::compiler::PipelineCompilationJob::PrepareJobImpl(v8::internal::Isolate*) [node]
17: 0xd94f5d v8::internal::OptimizedCompilationJob::PrepareJob(v8::internal::Isolate*) [node]
18: 0xd96358  [node]
19: 0xd97e70 v8::internal::Compiler::CompileOptimized(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSFunction>, v8::internal::ConcurrencyMode, v8::internal::CodeKind) [node]
20: 0x11f4463 v8::internal::Runtime_CompileOptimized_Concurrent(int, unsigned long*, v8::internal::Isolate*) [node]
21: 0x15e67f9  [node]

 ERROR

 Failed to execute pipeline. The following errors have occurred:

 Command was killed with SIGTRAP (Debugger breakpoint): jest --coverage --colors
  --logHeapUsage

Additional context

I've hit this on multiple PRs now, so reporting here for others to see.

I'm trying to reproduce this locally with no luck, so I have to keep pushing to trigger CI.

I will attempt different versions and combinations and report back:

FAILS:

• node 16.9, jest 27.1 --logHeapUsage --coverage - https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571895050
• node 16.9, jest 27.1 --logHeapUsage
• node 16.9, jest 27.1 - https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571950244
• node 16.9, jest 27.0 - https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571997318

Environment

This is my local machine and not GitHub CI.

  System:
    OS: macOS 11.5.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.9.1 - ~/.nvm/versions/node/v16.9.1/bin/node
    Yarn: 3.0.0 - ~/.nvm/versions/node/v16.9.1/bin/yarn
    npm: 7.21.1 - ~/.nvm/versions/node/v16.9.1/bin/npm
  npmPackages:
    jest: 27.1.0

[milesj]

I wonder if this fixes it: nodejs/node@1b335d4

[milesj]

Yeah seems like it: nodejs/node#40030

[SimenB]

yup

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.