Skip to content

Conversation

@cerdelen
Copy link
Contributor

fixing #9790.

When multiple files are parsed only the last exit code would be returned. This means if the command succeeded for the last file the return code for the whole command would always be success even though an earlier files would be unsuccesful.

@sylvestre
Copy link
Contributor

could you please add a test to make sure we don't regress? thanks

@github-actions
Copy link

GNU testsuite comparison:

Congrats! The gnu test tests/misc/tsort is no longer failing!
Congrats! The gnu test tests/tail/inotify-dir-recreate is now passing!

Copy link
Contributor

@sylvestre sylvestre left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need tests

@asder8215
Copy link
Contributor

this might conflict with my PR #9802, which tries to resolve issue #9789

@cerdelen
Copy link
Contributor Author

this might conflict with my PR #9802, which tries to resolve issue #9789

I don’t think this should actually conflict with your PR #9802. I looked through your code and added my test locally; it does fail for this specific issue, but it i double checked and verified its fixed by the same online change as in this PR.

If this PR lands in main, it should be straightforward to resolve with a rebase. Worst case, it would just require manually applying the fix (a simple .and(r) on l. 422 in your current fork).

I still think keeping these as separate PRs makes sense, since it provides clearer documentation of what fixes which issue and ensures the corresponding regression tests are in place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants