Repository navigation
Conversation
Match the JS: prefix that V8 has emitted for JavaScript functions since 6bd756d. The LazyCompile expectation caused the test to time out when profiling succeeded without UNKNOWN samples. Assisted-by: Codex Signed-off-by: Tamir Duberstein <tamird@gmail.com>
|
Welcome to Node.js, and thank you for your first contribution! Before review, please take a moment to read:
Please make sure every commit is signed off. For a first pull request, GitHub Actions require collaborator approval and Jenkins CI must be started by a collaborator or triager, so an initial wait is normal. Caution AgentScan found account activity patterns that may be consistent with automation. This is a heuristic, not proof that this pull request was opened by an agent or violates policy. AI-assisted contributions are permitted, but automated tooling must not open pull requests without advance approval, and contributors must personally understand, test, verify, and take responsibility for every submitted change. See the AgentScan analysis, AI use policy, and automation policy for additional context. |
Match the
JS:prefix that V8 has emitted for JavaScript functions since6bd756d7c. The
LazyCompileexpectation caused this test to time outwhen profiling succeeded without
UNKNOWNsamples.On Linux AMD64 with the official Node v26.12.0 binary, the existing test
timed out after 180 seconds. With this one-line correction, it passed in
1.19 seconds. Both captured profiles contained
JS: *f [eval]:1:11.The fixture is unchanged between v26.12.0 and current main; the full Node
test suite has not been run for this change.
Prepared by Codex on behalf of @tamird.