Skip to content

Keep runners alive when runs OOM#224

Draft
socksy wants to merge 4 commits intodevelopfrom
feature/keep-runners-alive-when-runs-oom
Draft

Keep runners alive when runs OOM#224
socksy wants to merge 4 commits intodevelopfrom
feature/keep-runners-alive-when-runs-oom

Conversation

@socksy
Copy link
Contributor

@socksy socksy commented Mar 11, 2026

No description provided.

socksy added 3 commits March 11, 2026 16:48
status.code() returns None when a process is killed by a signal rather
than exiting normally. We haven't really hit this code path in
production yet, hence why it's been here latent
If a child process dies due to disk-full errors, we pop
the balloon and then suddenly should have some disk space
again (theoretically, let's test this idea).
@coderabbitai
Copy link

coderabbitai bot commented Mar 11, 2026

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 963a8233-aea8-4e7c-9165-8a1539426cbc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feature/keep-runners-alive-when-runs-oom

Comment @coderabbitai help to get the list of available commands and usage tips.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant