Skip to content

analyzer co19_2 test failures when switching the parser to fasta #33995

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

Closed
devoncarew opened this issue Jul 26, 2018 · 5 comments
Closed

analyzer co19_2 test failures when switching the parser to fasta #33995

devoncarew opened this issue Jul 26, 2018 · 5 comments
Labels
legacy-area-analyzer Use area-devexp instead. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@devoncarew
Copy link
Member

@danrubel

@bwilkerson
Copy link
Member

Are there test failures that need to be tracked here, or can we close this?

@devoncarew
Copy link
Member Author

I see 60 references from co19_2/co19_2-analyzer.status.

@bwilkerson bwilkerson added the type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) label Aug 28, 2018
@devoncarew devoncarew changed the title meta issue to track analyzer co19_2 test failures when switching the parser to fasta analyzer co19_2 test failures when switching the parser to fasta Sep 6, 2018
@danrubel
Copy link

danrubel commented Sep 12, 2018

Fixes:

Open issues outside fasta parser and AstBuilder:

Pre existing issues:

@danrubel danrubel self-assigned this Sep 12, 2018
@danrubel
Copy link

I have fixed what I can in the parser (see above) and many (all?) of the rest are pre-existing issues. If you do find another parser or AstBuilder related issue, please let me know

@danrubel danrubel removed their assignment Sep 13, 2018
@devoncarew
Copy link
Member Author

Great! I'll close this now given that the remaining issues are pre-existing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
legacy-area-analyzer Use area-devexp instead. type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Development

No branches or pull requests

3 participants