#55658: test: use runner timeout for DevTools indexing lifecycle waits
Merged
Description of Change
The cpp-heap DevTools indexing test could fail when waiting for DevTools to open or WebContents to be destroyed because each wait had a fixed 10-second deadline. These deadlines were shorter than the runner's overall test timeout and did not scale with the longer timeout used by sanitizer builds.
Remove those internal deadlines and let the runner enforce the test timeout. Both lifecycle events must still occur, and retries remain disabled for the entire cpp-heap suite.
Add stderr diagnostics before and after each wait so a stalled remote call identifies which lifecycle event is pending.
Checklist
- I have built and tested this change
- I have filled out the PR description
- I have reviewed and verified the changes
-
npm testpasses - tests are changed or added
- PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, past tense, and no longer than 80 characters.
Release Notes
Notes: none
Backports
44-x-y
PendingWaiting for a manual backport
45-x-y
PendingWaiting for a manual backport
Semver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron