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

Fix a flaky compiler suite #11514

Merged
merged 1 commit into from
May 24, 2016
Merged

Fix a flaky compiler suite #11514

merged 1 commit into from
May 24, 2016

Conversation

jaredpar
Copy link
Member

The intent of ServerRespectsAppConfig was to verify the server actually read the default timeout value from the application configuration file. The test validated this in a very indirect way:

  • Changing the value in app.config
  • Starting the server
  • Verifying it stopped in the given time frame

This can fail for a number of reasons: computer load during the test, another process communicating with the server, etc ...

Changed the test to just directly test the value being read from application settings.

Justification for ask mode: this test was flaky enough to break signed builds.

@jaredpar
Copy link
Member Author

CC @dotnet/roslyn-compiler, @MattGertz

@jaredpar
Copy link
Member Author

CC @jasonmalinowski

@MattGertz
Copy link
Contributor

No ask mode approval needed for test-only fixes, but the commit also touches code files, yes? Either way, approved.

@jaredpar
Copy link
Member Author

@MattGertz yes this touches code paths (albeit in a very minor way).

@AlekseyTs
Copy link
Contributor

@jaredpar It looks like build failure on windows is related to the change you are making.

The intent of ServerRespectsAppConfig was to verify the server actually read the default timeout value from the application configuration file.  The test validated this in a very indirect way:

- Changing the value in app.config
- Starting the server
- Verifying it stopped in the given time frame

This can fail for a number of reasons: computer load during the test, another process communicating with the server, etc ...

Changed the test to just directly test the value being read from application settings.

Justification for ask mode: this test was flaky enough to break signed builds.
@jaredpar
Copy link
Member Author

@AlekseyTs oops, yep that's my fault. Fixed.

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.

4 participants