Skip to content

ci: classify Bun epoll faults as runtime crashes #1475

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Wibias merged 1 commit into from
Aug 11, 2026
Merged

ci: classify Bun epoll faults as runtime crashes #1475

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions scripts/ci/run-bun-test-batches.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,16 @@ is_bun_runtime_crash() {
;;
esac

# Bun 1.3.14 can surface a Linux epoll registration failure as exit 1,
# even though the failure comes from Bun's internal WriteStream setup rather
# than a test assertion. Treat only that narrow runtime signature as a crash.
if (( status == 1 )) \
&& grep -Fq '# Unhandled error between tests' "$log_file" \
&& grep -Fq 'error: EEXIST: file already exists, epoll_ctl' "$log_file" \
&& grep -Fq 'at new WriteStream (internal:fs/streams:' "$log_file"; then
return 0
fi

grep -Eqi \
'oh no: Bun has crashed|Segmentation fault at address|Illegal instruction|Bus error|Aborted \(core dumped\)' \
"$log_file"
Expand Down
Loading