Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OSOE-464: Making dotnet test output go to the build output to aid debugging, as well as printing ITestOutputHelper content #101
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
OSOE-464: Making dotnet test output go to the build output to aid debugging, as well as printing ITestOutputHelper content #101
Changes from 6 commits
51dfe31
a997a7b
0f13926
1d5c001
d3fa27e
e3d3ec7
e371d76
2e6636d
c341ef1
03008f5
75a9726
243ff58
2ce191d
82a5323
0eeda56
a5c1a40
8597152
659dc73
6998a75
220d729
e81ce27
84141ba
5a9a831
4912bec
7827fa4
9a5b62a
7f4e3e9
829c298
1f56fac
96383e0
187e1d8
92eb9f7
3825d1e
9fa4d0b
829fa11
9795fed
e30a536
4f93303
acb5f5f
6865a0b
0fdd730
2965e67
fbdbebb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we still filter out these pointless "Connection refused" and "ChromeDriver" log lines on
dotnet test @dotnetTestSwitches
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know or have found a way to live-filter a streaming output, though I only have smallish experience with PS.
The goal here is for the output of the tests to show up in the log continuously (to pinpoint what the last thing was before the runner was killed due to timeout). If there's a file at the end of the
dotnet test
call then you can grep like this, but we can't wait for a file.We could still redirect to a file and tail it and that can be filtered but going through a file doesn't seem like the best idea, and we also need to somehow know when the stream actually ended and quit the
Wait
.So, I don't know. It seems to me that implementing grouping around the test project if it doesn't have its custom group and letting UI tests group themselves, as well as filtering out such messages need a file. If we have a file, however, we won't have a continuous output.
Do you have any suggestions by chance?
BTW I'm also trying to figure out where the annoying log messages come from and disable them in the first place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dotnet test @dotnetTestSwitches 2>&1 | ? { $_ -notlike '*Connection refused [[]::ffff:127.0.0.1[]]*' -and $_ -notlike '*ChromeDriver was started successfully*' }
should filter it line-by-line as it's passed to the pipe. We can live without the outer grouping until they finally add named groups to the runner.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah nice, so this works like this!