-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
Force tasks with no files as failed #92
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #92 +/- ##
==========================================
- Coverage 46.35% 46.11% -0.25%
==========================================
Files 10 10
Lines 384 386 +2
Branches 43 44 +1
==========================================
Hits 178 178
- Misses 205 206 +1
- Partials 1 2 +1 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haven't checked the template to find out what happens exactly but this with current line 133 is a mistake
return MailToSend(status=SUCCESS, target=target, subject=subject, body=body)
I don't get why? Because |
Please do so in this PR. This function used to return only on failures and only reach this point when everything's fine. Now that we get to this point with a failed task, we need to be more careful. We don't want to have to look at the templates to find this out |
Nope, this function already reached this point when task status was among "requested", "succeeded", "failed" or "canceled". See line
But anyway, will fix this in this PR, better now than never |
Fix #90