#24384: compilemessages shouldn't return with exit code 0 when it fails
-------------------------------------+-------------------------------------
Reporter: Aymeric Augustin | Owner: Claude
| Paroz
Type: Bug | Status: closed
Component: | Version: master
Internationalization |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"a77f21880dfb0631ea0adb22d47909915cbfc3a9" a77f2188]:
{{{
#!CommitTicketReference repository=""
revision="a77f21880dfb0631ea0adb22d47909915cbfc3a9"
Fixed #24384 -- Allowed compilemessages to continue running after nonfatal
errors.
Thanks Aymeric Augustin for the report and Carlton Gibson and Tim Graham
for
the reviews.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24384#comment:8>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.c0112776c2dc4c2db770fa3ccfa47c2f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
