Skip to content

Display backtrace from unexpected errors in terminate_all_workers()#187

Merged
JamesWrigley merged 1 commit intomasterfrom
rmprocs-timeout
Apr 14, 2026
Merged

Display backtrace from unexpected errors in terminate_all_workers()#187
JamesWrigley merged 1 commit intomasterfrom
rmprocs-timeout

Conversation

@JamesWrigley
Copy link
Copy Markdown
Member

@JamesWrigley JamesWrigley self-assigned this Apr 13, 2026
@JamesWrigley JamesWrigley added the bug Something isn't working label Apr 13, 2026
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 13, 2026

Codecov Report

❌ Patch coverage is 0% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 79.39%. Comparing base (1a25fc7) to head (14fa32c).
⚠️ Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
src/cluster.jl 0.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #187      +/-   ##
==========================================
- Coverage   79.47%   79.39%   -0.09%     
==========================================
  Files          10       10              
  Lines        1959     1961       +2     
==========================================
  Hits         1557     1557              
- Misses        402      404       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment thread src/cluster.jl
catch _ex
@warn "Forcibly interrupting busy workers" exception=_ex
if _ex isa ErrorException
@warn "Forcibly interrupting busy workers" exception=_ex
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we show the backtrace in all cases?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought about that, but I'd lean against it because rmprocs() timing out is semi-expected and I don't think we want to display a full stacktrace for it.

@JamesWrigley JamesWrigley merged commit 8615c26 into master Apr 14, 2026
7 of 9 checks passed
@JamesWrigley JamesWrigley deleted the rmprocs-timeout branch April 14, 2026 08:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants