-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
log: replace a panic with an error in debug merge-logs #69018
Conversation
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.
Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @cameronnunez)
859de4e
to
3d2f573
Compare
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.
nice
a unit test wouldn't hurt though |
for this you can create a new |
4d6e54d
to
171f831
Compare
@ajwerner mind taking a quick look at this Example test I threw up? The test isn't passing for some reason. No output.
|
I have tried to run the command manually (from the command line) on the test data. This means that the logic is not yet ready. In fact, I don't see any kind of error being handled properly (e.g. disk read errors are probably not handled properly either). This needs to be looked at first. In general, before you build a test, try running the command manually! There's nothing better than the human eye to give confidence that something works as expected. |
Actually now if I run the |
I stand corrected! the problem is that |
here you are: cameronnunez#2
(Arguably it's poor UX that the command terminates without telling you that no files were processed. This could be improved too. Just not in this PR) |
don't forget to squash before merging |
394b320
to
ed02a5b
Compare
ed02a5b
to
6caf95b
Compare
13a61da
to
ff5cb0c
Compare
this is ready to merge I think? |
@knz CI was failing – had to add a release justification. Should I see if CI passes or go ahead and merge? |
let's wait for github CI to be green, you're right. then merge after that |
ff5cb0c
to
20c361f
Compare
What's remaining to do with this PR? |
For some reason, the test is failing with this output:
|
cdaafed
to
9a94e8d
Compare
I think this is good now. nit: I think our release note parser prefers when the release justification comes above the release note. |
9a94e8d
to
3b0c4bd
Compare
Release justification: bug fix Release note (bug fix): Users would receive a panic message when the log parser fails to extract log file formats. This has been replaced with a helpful error message.
3b0c4bd
to
a5caea6
Compare
bors r=ajwerner,knz,otan |
Build succeeded: |
Related issue: #68278
Release justification: bug fix
Release note (bug fix): Users would receive a panic message when the log parser
fails to extract log file formats. This has been replaced with a helpful
error message.