-
Notifications
You must be signed in to change notification settings - Fork 242
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
Conformance tests: Align automated and manual scoring #1692
Labels
topic: other
Other topics not covered
Comments
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
Pyright produces an error unrelated to the purpose of the test, and I don't see a good way to write the test to avoid the error. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
Pyright produces an error unrelated to the purpose of the test, and I don't see a good way to write the test to avoid the error. Part of #1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
Pyright produces warnings instead of errors for many issues in this test case. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
I can't find the quoted phrase in the spec and I don't see a reason why this should error. Part of python#1692
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
Pyright produces warnings instead of errors for many issues in this test case. Part of #1692
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
I can't find the quoted phrase in the spec and I don't see a reason why this should error. Part of #1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
It fails to produce errors on a few lines expected by the test. Also fix an unrelated pytype error and ignore an unrelated pyre error. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
Pyre and pytype produced an expected error on the wrong line. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 9, 2024
It does not produce an error for `x: Literal[4]; assert_type(x, int)`. Part of python#1692
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
It does not produce an error for `x: Literal[4]; assert_type(x, int)`. Part of #1692
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
Pyre and pytype produced an expected error on the wrong line. Part of #1692
JelleZijlstra
added a commit
that referenced
this issue
Apr 9, 2024
It fails to produce errors on a few lines expected by the test. Also fix an unrelated pytype error and ignore an unrelated pyre error. Part of #1692
JelleZijlstra
added a commit
that referenced
this issue
Apr 10, 2024
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
…1700) Pyright produces an error unrelated to the purpose of the test, and I don't see a good way to write the test to avoid the error. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
…#1702) Pyright produces warnings instead of errors for many issues in this test case. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
I can't find the quoted phrase in the spec and I don't see a reason why this should error. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
It does not produce an error for `x: Literal[4]; assert_type(x, int)`. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
Pyre and pytype produced an expected error on the wrong line. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
It fails to produce errors on a few lines expected by the test. Also fix an unrelated pytype error and ignore an unrelated pyre error. Part of python#1692
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Apr 11, 2024
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Jun 7, 2024
Pyre infers "Literal[1]" instead of "int", which seems legal. Change the test to get an int from a function parameter instead, so that all type checkers are aligned. Part of python#1692.
JelleZijlstra
added a commit
to JelleZijlstra/typing
that referenced
this issue
Jun 7, 2024
It appears to produce the correct output. Part of python#1692
JelleZijlstra
added a commit
that referenced
this issue
Jun 7, 2024
Pyre infers "Literal[1]" instead of "int", which seems legal. Change the test to get an int from a function parameter instead, so that all type checkers are aligned. Part of #1692.
JelleZijlstra
added a commit
that referenced
this issue
Jun 7, 2024
It appears to produce the correct output. Part of #1692
The only remaining issue now is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #1678 I added an automated tool for scoring the conformance test suite, and #1682 and #1683 added some features to support edge cases.
Now I am working on going through the remaining files where the automated conformance judgment on a file differs from the manual one (open PRs: #1684, #1685, #1687, #1688, #1689, #1690, #1691).
I'll use this issue to track the remaining discrepancies (from
conformance/src/unexpected_fails.py
):Any help is appreciated.
The text was updated successfully, but these errors were encountered: