Skip to content
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.

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

fix: propagate aborted status correctly on GKE's OOMKilled #5762

Merged
merged 4 commits into from
Aug 14, 2024

Conversation

rangoo94
Copy link
Member

Pull request description

Checklist (choose whats happened)

  • breaking change! (describe)
  • tested locally
  • tested on cluster
  • added new dependencies
  • updated the docs
  • added a test

Breaking changes

Changes

Fixes

@rangoo94 rangoo94 requested a review from a team as a code owner August 14, 2024 11:11
@rangoo94 rangoo94 merged commit 3dd3301 into develop Aug 14, 2024
6 checks passed
@rangoo94 rangoo94 deleted the dawid/fix/gke-oomkilled-aborted branch August 14, 2024 12:46
rangoo94 added a commit that referenced this pull request Aug 14, 2024
* fix: propagate aborted status correctly on GKE's OOMKilled
* fix: don't trust step statuses in Test Workflow after it's aborted
* fix: show abort information about pod/job timeout
* fix: isolate abort error to single step
rangoo94 added a commit that referenced this pull request Aug 14, 2024
* fix: propagate aborted status correctly on GKE's OOMKilled
* fix: don't trust step statuses in Test Workflow after it's aborted
* fix: show abort information about pod/job timeout
* fix: isolate abort error to single step
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.

2 participants