Thread (28 messages) 28 messages, 4 authors, 2025-01-09

Re: [PATCH 4/6] test-lib: simplify leak-log checking

From: Jeff King <hidden>
Date: 2025-01-07 07:01:08

On Mon, Jan 06, 2025 at 08:56:57AM +0100, Patrick Steinhardt wrote:
quoted
Plus I don't think "find" propagates the exit code from -exec anyway. I
think you can check the exit status with more find logic, so you'd then
use a conditional -print for each file like:
It should. Quoting find(1):

    If any invocation with the `+' form returns a non-zero value as exit
    status, then find returns a non-zero exit status.
Ah, right. I tried using ';' to look at individual files, and it does
ignore the code. But of course we don't need to know which logs had
leaks, only that there was at least one.

I think we can make it even simpler, though. I'll post patches in a
moment.

-Peff
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help