#36750: dumpdata's output of m2m values is not deterministic
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: (none)
Type: Bug | Status: new
Component: Core | Version: dev
(Serialization) |
Severity: Normal | Resolution:
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 VIZZARD-X):
I tried to reproduce this issue on the current main branch using the same
shuffle seed and parameters from the report:
python tests/runtests.py fixtures --shuffle 7825542710
--settings=tests.test_sqlite -k forward -v2
All four forward_reference tests pass, including:
test_forward_reference_m2m_natural_key
Given this, I’m unable to reproduce the nondeterministic M2M natural key
ordering on the latest code. It appears the issue may already have been
resolved by recent changes in the serializers or related refactors.
Could the ticket be reviewed and possibly closed if others also cannot
reproduce it?
--
Ticket URL: <https://code.djangoproject.com/ticket/36750#comment:1>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019aaafeb1ce-cd8861e9-396b-4c29-a1be-2cc8e98d3715-000000%40eu-central-1.amazonses.com.
