-
Couldn't load subscription status.
- Fork 32
🎨Computational backend: Automatically stop a running job if no logs are detected for 1h #8549
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
base: master
Are you sure you want to change the base?
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #8549 +/- ##
==========================================
+ Coverage 87.04% 88.39% +1.35%
==========================================
Files 2011 1288 -723
Lines 78751 54876 -23875
Branches 1365 187 -1178
==========================================
- Hits 68545 48506 -20039
+ Misses 9803 6311 -3492
+ Partials 403 59 -344
Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
e6ada92 to
69cb65c
Compare
🧪 CI InsightsHere's what we observed from your CI run for fe881f5. ❌ Job Failures
✅ Passed Jobs With Interesting Signals
|
69cb65c to
fe881f5
Compare
|



What do these changes do?
As it happens more and more this is a measure to protect the platform from long running jobs that are probably hanging and it protects the user from paying for jobs that are hanged.
If a job does not produce any logs during 1h a timeout triggers and will stop the job.
Related issue/s
How to test
Dev-ops