-
Notifications
You must be signed in to change notification settings - Fork 323
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
21 compiler tests that relied on the old parser disabled #5894
Labels
--breaking
Important: a change that will break a public API or user-facing behaviour
--bug
Type: bug
-compiler
Milestone
Comments
kazcw
added a commit
that referenced
this issue
Mar 13, 2023
- Doc parsing is now done only in the frontend. - The scala parser has been eliminated. We were using it for docs and a few odd cases, including to run some tests. Some syntax cases that only occurred in compiler tests are treated differently in the new parser. Mainly these relate to type signatures and annotations. Some of these cases should be handled in translation. #5894 tracks triaging these cases and re-enabling the affected tests. - The option to run the old searcher has been removed, as it is obsolete and was already broken before this. - Some interfaces used only by the old searcher have been removed.
kazcw
changed the title
Placeholder
Investigate backend tests that relied on the old parser
Mar 13, 2023
mergify bot
pushed a commit
that referenced
this issue
Mar 15, 2023
Implement new Enso documentation parser; remove old Scala Enso parser. Performance: Total time parsing documentation is now ~2ms. # Important Notes - Doc parsing is now done only in the frontend. - Some engine tests had never been switched to the new parser. We should investigate tests that don't pass after the switch: #5894. - The option to run the old searcher has been removed, as it is obsolete and was already broken before this (see #5909). - Some interfaces used only by the old searcher have been removed.
There seems to be 21 such tests right now: enso$ grep -r 5894 engine/runtime/src/test/
engine/runtime/src/test/scala/org/enso/compiler/test/pass/desugar/LambdaShorthandToLambdaTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/desugar/FunctionBindingTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/desugar/ComplexTypeTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/IgnoredBindingsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/ExpressionAnnotationsTest.scala: // FIXME: New parser handles the syntax error differently--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SugaredTypeFunctionsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/TypeSignaturesTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/TypeSignaturesTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SuspendedArgumentsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/resolve/SuspendedArgumentsTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/analyse/AliasAnalysisTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/analyse/DataflowAnalysisTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/analyse/DataflowAnalysisTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/analyse/DataflowAnalysisTest.scala: // FIXME: Not supported by new parser--needs triage (#5894).
engine/runtime/src/test/scala/org/enso/compiler/test/pass/analyse/DataflowAnalysisTest.scala: // FIXME: Different result in new parser!--needs triage (#5894). CCing @hubertp |
JaroslavTulach
changed the title
Investigate backend tests that relied on the old parser
21 compiler tests that relied on the old parser disabled
Mar 16, 2023
JaroslavTulach
added
--breaking
Important: a change that will break a public API or user-facing behaviour
--bug
Type: bug
labels
Mar 16, 2023
Jaroslav Tulach reports a new STANDUP for yesterday (2023-03-30): Progress: - PR: #6143
Next Day: Continue analyzing disabled parser tests.
|
Jaroslav Tulach reports a new STANDUP for yesterday (2023-03-31): Progress: - Review: #6154
Next Day: Continue analyzing disabled parser tests. |
mergify bot
pushed a commit
that referenced
this issue
Apr 2, 2023
Modification to various tests disabled when #5917 was integrated to pass with new parser. Fixes #5894. # Important Notes Some tests can be fixed just by changes on the `IR` side. Some (especially error simulating ones) would benefit from changes in the `Tree` structure or at least @kazcw evaluation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
--breaking
Important: a change that will break a public API or user-facing behaviour
--bug
Type: bug
-compiler
Some backend tests that had not been switched to the new parser before #5917 don't pass with the new parser; these can be found by searching the codebase for references to this issue number (after that PR merges).
This is due to syntax cases that don't occur outside the tests in question, and that generally relate to type signatures and type declarations.
Each test either needs to be updated or needs a (generally simple) change in translation or the parser.
The text was updated successfully, but these errors were encountered: