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

CSharpFixAllOccurrences.FixAllOccurrences fails intermittently #10877

Closed
tmat opened this issue Apr 26, 2016 · 9 comments · Fixed by #11221
Closed

CSharpFixAllOccurrences.FixAllOccurrences fails intermittently #10877

tmat opened this issue Apr 26, 2016 · 9 comments · Fixed by #11221
Assignees
Labels
Area-Analyzers Bug Test Test failures in roslyn-CI
Milestone

Comments

@tmat
Copy link
Member

tmat commented Apr 26, 2016

http://dotnet-ci.cloudapp.net/job/dotnet_roslyn_prtest_win_vsi_p2/680/

@gafter gafter added Bug Area-IDE Test Test failures in roslyn-CI labels Apr 26, 2016
@Pilchie
Copy link
Member

Pilchie commented Apr 26, 2016

Looks like the error is finding failures to fix. @mavasani related to the FSD fix?

21:00:43 --------------------------------
21:00:43 System.Exception: Wrong number of errors in error list. Expected '9794', found '58'.
21:00:43 
21:00:43 Actual errors:
21:00:43 Do not use regions
21:00:43 The file header is missing or not located at the top of the file.
21:00:43 Using directive must appear within a namespace declaration
21:00:43 Elements must be documented
21:00:43 Enumeration items must be documented
21:00:43 Enumeration items must be documented
21:00:43 Enumeration items must be documented
21:00:43 Enumeration items must be documented
21:00:43 Enumeration items must be documented
21:00:43 Enumeration items must be documented
21:00:43 Enumeration items must be documented
21:00:43 Disposable fields should be disposed
21:00:43 The file header is missing or not located at the top of the file.
21:00:43 Using directive must appear within a namespace declaration
21:00:43 Field '_commentHandling' must not begin with an underscore
21:00:43 Field '_lineInfoHandling' must not begin with an underscore
21:00:43 All accessors must be single-line or multi-line
21:00:43 Prefix local calls with this
21:00:43 Elements must be separated by blank line
21:00:43 Prefix local calls with this
21:00:43 All accessors must be single-line or multi-line
21:00:43 Prefix local calls with this
21:00:43 Elements must be separated by blank line
21:00:43 Prefix local calls with this
21:00:43 The file header is missing or not located at the top of the file.
21:00:43 Using directive must appear within a namespace declaration
21:00:43 Using directive must appear within a namespace declaration
21:00:43 Using directive must appear within a namespace declaration
21:00:43 Elements must be documented
21:00:43 Elements must be documented
21:00:43 Elements must be documented
21:00:43 Prefix local calls with this
21:00:43 Prefix local calls with this
21:00:43 Prefix local calls with this
21:00:43 Prefix local calls with this
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Disposable fields should be disposed
21:00:43 Do not use regions
21:00:43 The file header is missing or not located at the top of the file.
21:00:43 Elements must be documented
21:00:43 Generic type constraints must be on their own line
21:00:43 Field '_name' must not begin with an underscore
21:00:43 Field '_value' must not begin with an underscore
21:00:43 Elements must be documented
21:00:43 Prefix local calls with this
21:00:43 Elements must be documented
21:00:43 Prefix local calls with this
21:00:43 Elements must be documented
21:00:43 A constructor should not follow a property
21:00:43 Prefix local calls with this
21:00:43 Prefix local calls with this
21:00:43 
21:00:43    at Roslyn.VSHosting.Test.VerifyErrorListAction.Execute(TaoEngine engine) in d:\j\workspace\dotnet_roslyn---b84db72c\Closed\Hosting\RoslynTaoActions\Actions\VisualStudio\VerifyErrorListAction.cs:line 66
21:00:43    at Tao.Engine.DebuggableActionExecutor.Execute() in f:\dd\src\Omni\Tao\Tao.Engine\ActionExecutor.cs:line 139
21:00:43    at Tao.Engine.DefaultActionExecutor.Execute() in f:\dd\src\Omni\Tao\Tao.Engine\ActionExecutor.cs:line 36
21:00:43 ================================
21:00:43 
21:00:43 
21:00:43 Saved screenshot: d:\j\workspace\dotnet_roslyn---b84db72c\Open\Binaries\Release\Screenshots\2016-04-26_03-51-44_67 - Exception System.Exception.png

@mavasani
Copy link
Contributor

FSD wasn't checked into master till today morning - this seems unrelated. I am working on enhancing the logging for this test to give out better output when there is a count mismatch.

@mavasani mavasani self-assigned this Apr 26, 2016
@mavasani
Copy link
Contributor

Wow, so the screenshot shows Low Memory Detected - Full solution analysis turned off warning. Given that this is just a small Newtonsoft.json project with few thousand lines, this seems very surprising indeed.
@lgolding Should we modify the process watchdog to listen to low VM notifications and generate a dump (and possibly fail the test) when it happens?

@mavasani
Copy link
Contributor

2016-04-26_03-51-44_67 20- 20exception 20system exception

@mavasani
Copy link
Contributor

mavasani commented May 2, 2016

We have replaced the IDE diagnostic engine and also improved the logging for the test. Please re-activate and assign to me if we see this test fail again.

@jasonmalinowski
Copy link
Member

This is still failing regularly: http://dotnet-ci.cloudapp.net/job/roslyn-internal_prtest_win_vsi_p2/568/

@srivatsn srivatsn added this to the 1.3 milestone May 9, 2016
@mavasani mavasani assigned heejaechang and unassigned mavasani May 9, 2016
@mavasani
Copy link
Contributor

mavasani commented May 9, 2016

Screenshot shows we didn't get the diagnostic and/or code fix when light bulb was invoked. HeeJae, can you take a look?

@heejaechang
Copy link
Contributor

@mavasani is this compilation end analyzer? or other kind of analyzer?

@mavasani
Copy link
Contributor

mavasani commented May 9, 2016

This is stylecop analyzer SA1101. It's implementation is here - its a regular syntax node analyzer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Analyzers Bug Test Test failures in roslyn-CI
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants