Skip to content
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

re-enabled asserts that got disabled before #21434

Merged
merged 2 commits into from
Aug 14, 2017

Conversation

heejaechang
Copy link
Contributor

@heejaechang heejaechang commented Aug 10, 2017

these asserts were disabled before once I added tests that calls GetOperations over every nodes in AllInOneCS and AllInOneVB test files.

since GetOperation is supposed to handle all nodes given to it, it should not cause any assert to fire. even if it returns null if it can't handle the given node.

I talked with @AlekseyTs and he suggested checking IsSemanticModelBinder on all those asserts and re-enable those.

@heejaechang
Copy link
Contributor Author

@dotnet/analyzer-ioperation @cston @AlekseyTs @jcouv can you take a look?

@heejaechang
Copy link
Contributor Author

retest windows_release_unit32_prtest please

@heejaechang
Copy link
Contributor Author

retest windows_release_vs-integration_prtest please

@cston
Copy link
Member

cston commented Aug 14, 2017

LGTM

@heejaechang
Copy link
Contributor Author

@AlekseyTs @cston can you take a look? I followed @AlekseyTs 's suggestion.

Copy link
Contributor

@AlekseyTs AlekseyTs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@heejaechang heejaechang merged commit a2840b9 into dotnet:features/ioperation Aug 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants