#34436: `makemigrations --check` fails with error code 1 if system checks
identify
warnings
-------------------------------+--------------------------------------
Reporter: James Addison | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 4.2
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by James Addison):
I think this should be reopened - I suspect I didn't convey the meaning
correctly?
- `manage.py check` is ''correctly not failing'' (see the 0 exit code in
my example)
- nothing is currently (until 5.1 is released) in a broken check state
- `manage.py makemigrations --check` is ''incorrectly failing'' (see 1
exit code in my example above)
- the 'check' for missing migrations yielded no missing migrations, so
should not return an error
- the fact that those warning are raised have nothing to do with
migrations currently at risk (again, until 5.1 is released)
--
Ticket URL: <https://code.djangoproject.com/ticket/34436#comment:2>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701871572e78e-b28df699-5f71-411a-9dbb-366eb9ce9552-000000%40eu-central-1.amazonses.com.
