Brent Westbrook a71513bae1 Fix tests on 32-bit architectures (#19652) ...

Summary
--

Fixes #19640. I'm not sure these are the exact fixes we really want, but
I
reproduced the issue in a 32-bit Docker container and tracked down the
causes,
so I figured I'd open a PR.

As I commented on the issue, the `goto_references` test depends on the
iteration
order of the files in an `FxHashSet` in `Indexed`. In this case, we can
just
sort the output in test code.

Similarly, the tuple case depended on the order of overloads inserted in
an
`FxHashMap`. `FxIndexMap` seemed like a convenient drop-in replacement,
but I
don't know if that will have other detrimental effects. I did have to
change the
assertion for the tuple test, but I think it should now be stable across
architectures.

Test Plan
--

Running the tests in the aforementioned Docker container

2025-07-31 08:52:19 -04:00

..

bytes.md

[ty] Integer indexing into bytes returns int (#18218)

2025-05-20 16:44:12 +02:00

class.md

[ty] Fix false positives when subscripting an object inferred as having an Intersection type (#18920)

2025-06-24 18:39:02 +00:00

instance.md

[ty] Fix incorrect diagnostic when calling __setitem__ (#19645)

2025-07-30 20:34:52 +02:00

lists.md

[ty] Understand classes that inherit from subscripted Protocol[] as generic (#17832)

2025-05-09 17:39:15 +01:00

stepsize_zero.md

Rename Red Knot (#17820)

2025-05-03 19:49:15 +02:00

string.md

Rename Red Knot (#17820)

2025-05-03 19:49:15 +02:00

tuple.md

Fix tests on 32-bit architectures (#19652)

2025-07-31 08:52:19 -04:00