Skip to content
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

test_deterministic_sets fails on x86 (32 bit) #99934

Closed
kanavin opened this issue Dec 1, 2022 · 0 comments
Closed

test_deterministic_sets fails on x86 (32 bit) #99934

kanavin opened this issue Dec 1, 2022 · 0 comments
Labels
type-bug An unexpected behavior, bug, or error

Comments

@kanavin
Copy link
Contributor

kanavin commented Dec 1, 2022

I am observing:

======================================================================
FAIL: test_deterministic_sets (test.test_marshal.BugsTestCase.test_deterministic_sets) [set([('Spam', 0), ('Spam', 1), ('Spam', 2)])]
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.11/test/test_marshal.py", line 368, in test_deterministic_sets
    self.assertNotEqual(repr_0, repr_1)
AssertionError: b"{('Spam', 1), ('Spam', 0), ('Spam', 2)}\n" == b"{('Spam', 1), ('Spam', 0), ('Spam', 2)}\n"

======================================================================
FAIL: test_deterministic_sets (test.test_marshal.BugsTestCase.test_deterministic_sets) [frozenset([('Spam', 0), ('Spam', 1), ('Spam', 2)])]
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.11/test/test_marshal.py", line 368, in test_deterministic_sets
    self.assertNotEqual(repr_0, repr_1)
AssertionError: b"frozenset({('Spam', 1), ('Spam', 0), ('Spam', 2)})\n" == b"frozenset({('Spam', 1), ('Spam', 0), ('Spam', 2)})\n"

Linked PRs

@kanavin kanavin added the type-bug An unexpected behavior, bug, or error label Dec 1, 2022
kanavin pushed a commit to kanavin/cpython that referenced this issue Dec 1, 2022
…tic_sets

Existing elements do produce different output on x86_64, but they
do not on x86. Let's make the data longer to ensure it differs.
kanavin added a commit to kanavin/cpython that referenced this issue Dec 1, 2022
…tic_sets

Existing elements do produce different output on x86_64, but they
do not on x86. Let's make the data longer to ensure it differs.
rhettinger pushed a commit that referenced this issue Dec 3, 2022
…ts (GH-99935)

Existing elements do produce different output on x86_64, but they
do not on x86. Let's make the data longer to ensure it differs.
miss-islington pushed a commit to miss-islington/cpython that referenced this issue Dec 3, 2022
…tic_sets (pythonGH-99935)

Existing elements do produce different output on x86_64, but they
do not on x86. Let's make the data longer to ensure it differs.
(cherry picked from commit c68573b)

Co-authored-by: Alexander Kanavin <alex.kanavin@gmail.com>
miss-islington added a commit that referenced this issue Dec 3, 2022
…ts (GH-99935)

Existing elements do produce different output on x86_64, but they
do not on x86. Let's make the data longer to ensure it differs.
(cherry picked from commit c68573b)

Co-authored-by: Alexander Kanavin <alex.kanavin@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

No branches or pull requests

2 participants