[red-knot] Two gradual equivalent fully static types are also equivalent#15579
Conversation
|
AlexWaygood
left a comment
There was a problem hiding this comment.
Thanks. Can you say a little bit about why you added this test to the flaky submodule in this file rather than the stable submodule? Did it ever fail when you ran the property tests locally? I stress-tested the flaky property tests by running QUICKCHECK_TESTS=2000000 cargo test --release -p red_knot_python_semantic -- --ignored types::property_tests::flaky several times locally on this branch (after merging in main), and neither the new test you're adding here nor two_equivalent_types_are_also_gradual_equivalent failed once.
That implies to me that we should be adding this test to the stable submodule in this file? And also promoting two_equivalent_types_are_also_gradual_equivalent to stable?
|
Promoted. I thought I should remain careful "just in case". |
Summary
Follow-up to #15563, related to this comment there.
Test Plan
Type property tests.