chore: report active Harness context on timeout#3991
Draft
mrousavy wants to merge 1 commit into
Draft
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
@react-native-harness/jest@1.4.0-rc.1with the upstream Harness timeout-context change from fix: Report active context on device timeout callstackincubator/react-native-harness#137.Why
Latest main still fails Android with
visioncamera.controller.harness.tstiming out at file level. The controller file has 19 tests, and Android reports 118 total tests instead of 137, so that whole file produced no completed test cases. Current Harness output cannot tell whether this is stuck inbeforeAll/suite setup or in a specific controller test.This diagnostic patch should make the next Android failure name the active suite or test. If it only names
VisionCamera - Controller, the hang is before the first test starts. If it names an individual test, we can fix that specific native/app path.Verification
bun install --frozen-lockfilegit diff --checkDeviceNotRespondingErroraftersuite-startedand gotLast started suite before the device stopped responding: VisionCamera - Controller.DeviceNotRespondingErroraftertest-startedand gotLast started test before the device stopped responding: VisionCamera - Controller startZoomAnimation() animates the zoom.