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

[POSSIBLE BUG] t5562.08 hangs consistently in 2.28.0 when run via Jenkins

From
Randall S. Becker <rsbecker@nexbridge.com>
Date
Aug 2, 2020, 16:33 UTC
Message-ID
<072201d668ea$9f90a0e0$deb1e2a0$@nexbridge.com>

I have been working through figuring out why we are getting a consistent hang on t5562.08  for 2.28.0 on the NonStop TNS/X platform (x86 big endian). This did not happen in the -rc series changes and appears transient. My investigation into this did not turn up anything useful other than the circumstances.

When run from a shell, the test consistently passes regardless of options used. Then only time this hangs is when we run through the git test suite through Jenkins – so there is no valid input tty. Even redirecting stdin to /dev/null does not cause an issue.

I am suspecting something in the test suite rather than git itself. We have had similar issues with t5526 in the past – 2.20 timeframe as I recall. Interrupting git-http-backend unwound the test and allowed us to continue with the pipeline but I have no evidence of anything wrong there.

This will not stop our release of the NonStop builds of 2.28.0 since the test passes in isolation. Curiously, this does not have an issue on the TNS/E platform (itanium big endian) where we have seen more issues historically.

Kind Regards, Randall

-- Brief whoami: NonStop developer since approximately 211288444200000000 UNIX developer since approximately 421664400 -- In my real life, I talk too much.

Message 1 of 1 in “[POSSIBLE BUG] t5562.08 hangs consistently in 2.28.0 when run via Jenkins”
  1. Randall S. BeckerAug 2, 2020

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.