Skip to content
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.

Enable xUnit diagnostic messages #2505

Merged
merged 1 commit into from
Apr 19, 2018

Conversation

mikeharder
Copy link
Contributor

@mikeharder mikeharder commented Apr 18, 2018

@mikeharder
Copy link
Contributor Author

Verified the new setting is working (this particular test is long-running by design):

[00:04:48]   [xUnit.net 00:01:33.4351782] Sockets.FunctionalTests: [Long Running Test] 'TestKeepAliveTimeout', Elapsed: 00:01:29

@mikeharder mikeharder merged commit f3afbeb into dev Apr 19, 2018
@mikeharder mikeharder deleted the mikeharder/xunit-diagnostic-messages branch April 19, 2018 00:14
@mikeharder
Copy link
Contributor Author

CC: @ryanbrandenburg

mikeharder added a commit that referenced this pull request Apr 24, 2018
mikeharder added a commit that referenced this pull request Apr 25, 2018
- xUnit diagnostic messages were enabled in #2505 to help identify hung tests
- However, this also enables log messages for non-serializable theory data (#2509), which adds noise to logs
- It doesn't seem possible to disable the "non-serializable data" messages but keep the "long-running test" messages
- Converting all tests to serializable theory data is expensive and complicates test code
- The best solution for now is to revert xUnit diagnostic messages to disabled, and re-enable when needed to identify hung tests
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants