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

Re: UBSan failing on expensive test(s)

From
Jeff King <peff@peff.net>
Date
May 16, 2026, 02:13 UTC
Message-ID
<20260516021343.GA174647@coredump.intra.peff.net>
In-Reply-To
<871pfcdyt0.fsf@gitster.g>
On Sat, May 16, 2026 at 08:43:07AM +0900, Junio C Hamano wrote:
Show 16 quoted lines
> This started happening on 'next' that runs EXPENSIVE tests thanks to
> Dscho's recent updates to enable them in CI.
> 
> https://github.com/git/git/actions/runs/25896439353/job/76110441841#step:10:2172
> 
> It claims that """
> 
>     commit.c:1574:6: runtime error: signed integer overflow:
>     -2147483648 - 1 cannot be represented in type 'int'
> 
> """.
> 
> Another is related in the sense that it used to be hidden behind
> EXPENSIVE prerequisite, but is probably unrelated.
> 
> https://github.com/git/git/actions/runs/25896439353/job/76110441842#step:10:156
These patches should fix both.
  [1/2]: apply: plug leak on "patch too large" error
  [2/2]: commit: handle large commit messages in utf8 verification
 apply.c  |  6 ++++--
 commit.c | 31 +++++++++++++++----------------
 2 files changed, 19 insertions(+), 18 deletions(-)
-Peff
Previous: Junio C HamanoNext: Jeff King
Message 2 of 5 in “UBSan failing on expensive test(s)”
  1. Junio C HamanoMay 15, 2026
  2. Jeff KingMay 16, 2026
  3. 1/2 apply: plug leak on "patch too large" errorJeff King, May 16, 2026
  4. 2/2 commit: handle large commit messages in utf8 verificationJeff King, May 16, 2026
  5. Derrick StoleeMay 16, 2026

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.