git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] p5310: Fix broken && chain in performance test

From
Jeff King <peff@peff.net>
Date
Jun 27, 2015, 06:14 UTC
Message-ID
<20150627061444.GB9353@peff.net>
In-Reply-To
<CAGZ79kYCcexkdcF4D4GhUydh=0u0UOZGb0QGbtg6gbKWeO2M_Q@mail.gmail.com>
On Fri, Jun 26, 2015 at 03:34:19PM -0700, Stefan Beller wrote:
Show 7 quoted lines
> > Thanks.  How did you find this (does the auto &&-chain test apply to
> > t/perf stuff as well)?
> 
> Apparently the &&-chain tests for it as I got a warning for it while
> benchmarking some changes in ALLOC_GROW. (which originally
> should have fixed the coverity false positives, but I was side tracked
> wondering about performance)

That makes sense; we use test_expect_success here, so I think it is good for it to check that we are actually creating a sane exit status.

It looks like we do not extend the same protection to test_perf (it uses test_eval_, bnot test_run_). That is probably OK, as those tests are more about measuring the time than about correctness. OTOH, we do notice when a test_perf reports failure, so perhaps it would make sense to extend &&-chaining checks there.

-Peff
Previous: Stefan Beller
Message 4 of 4 in “p5310: Fix broken && chain in performance test”
  1. p5310: Fix broken && chain in performance testStefan Beller, Jun 26, 2015
  2. Junio C HamanoJun 26, 2015
  3. Stefan BellerJun 26, 2015
  4. Jeff KingJun 27, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.