#23850: Test failure in migrations tests
--------------------------------------+------------------------
               Reporter:  jphalip     |          Owner:  nobody
                   Type:  Bug         |         Status:  new
              Component:  Migrations  |        Version:  master
               Severity:  Normal      |       Keywords:
           Triage Stage:  Unreviewed  |      Has patch:  0
    Needs documentation:  0           |    Needs tests:  0
Patch needs improvement:  0           |  Easy pickings:  0
                  UI/UX:  0           |
--------------------------------------+------------------------
 I'm seeing a test failure on Python 3.3.6 and 3.4.2 (it passes with
 2.7.3):

 {{{
 ======================================================================
 FAIL: test_makemigrations_with_custom_name
 (migrations.test_commands.MakeMigrationsTests)
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "/django/tests/migrations/test_commands.py", line 545, in
 test_makemigrations_with_custom_name
     content = cmd("0002", migration_name_0002, "--empty")
   File "/django/tests/migrations/test_commands.py", line 531, in cmd
     self.assertTrue(os.path.exists(migration_file))
 AssertionError: False is not true

 ----------------------------------------------------------------------
 }}}

 The issue is that the following migration files get created:

 {{{
 $ ls tests/migrations/migrations_21/
 0001_my_custom_migration.py  0001_my_initial_migration.py __init__.py
 }}}

 Note that `my_custom_migration.py` starts with `0001_` whereas it should
 start with `0002_`. I'm unsure why this wasn't detected by the CI builds.
 Perhaps there's something broken in my environment but I really don't see
 what that could be.

 Again, this works for me in 2.7 but fails in Python 3.

--
Ticket URL: <https://code.djangoproject.com/ticket/23850>
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/050.26e50a6fd5a10787e7ee4998898f4454%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to