You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Two ubuntu-latest shard 5/5 jobs were cancelled at the 30-minute cap while tests/test_watch.bats was running. Both PRs change nothing that test_watch.bats exercises for these tests, and a re-run of one of them passed.
The stalled test differs between the two runs, so this is not one test.
In the first job's diagnostic process dump, a watch.sh sess-liveness.<pid> child was alive under the test with a sleep 600 sibling.
Main's run on the 1.3.0 release commit (34911107475) passed.
Unlike #1107, the file does not progress: no test result line is printed for about 27 minutes.
Next step: capture per-test start lines and a process tree at the stall (the timed runner already prints file starts), then find which wait has no ceiling.
Two ubuntu-latest shard 5/5 jobs were cancelled at the 30-minute cap while
tests/test_watch.batswas running. Both PRs change nothing thattest_watch.batsexercises for these tests, and a re-run of one of them passed.session-end: leaves the store-owned read cursor intact(next: test 6, actas-mode ready sentinel)watch: a failed pending-scan is surfaced and exits...(next: test 30,the watcher names this session's pane (#1044))watch.sh sess-liveness.<pid>child was alive under the test with asleep 600sibling.Unlike #1107, the file does not progress: no test result line is printed for about 27 minutes.
Next step: capture per-test start lines and a process tree at the stall (the timed runner already prints file starts), then find which wait has no ceiling.