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

Re: Testsuite failures on ppc64, sparc64 and s390x (64-bit BE)

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jan 4, 2020, 20:58 UTC
Message-ID
<20200104205803.GE6570@camp.crustytoothpaste.net>
In-Reply-To
<34ed7497-643e-5a38-d68c-7c075b647bcd@physik.fu-berlin.de>
On 2020-01-04 at 20:14:31, John Paul Adrian Glaubitz wrote:
Show 6 quoted lines
> Hi!
> 
> It seems that git is failing its testsuite on all 64-bit Big-Endian targets,
> full build log can be found in [1]. There seem to be multiple failures.
> 
> The issue first showed with 2.25-rc1 [2].

This is interesting, because there are different failures on different platforms. s390x shows failures only in t9100, which is one of the svn tests. From the diff between rc0 and rc1, I don't see anything which should affect git-svn in that way.

ppc64 and sparc64 failing a lot more tests, mostly due to segfaults, but from a cursory glance they all appear to be SVN-related.

Are we sure that some dependency of libsvn1 hasn't caused this problem? I noticed that all of the broken builds seem to have libserf-1-1 1.3.9-8, which appears to have received an overhaul recently. Of course, it could be something else as well.

I got rid of my UltraSPARC hardware when I last moved, so I won't be looking into this further, but it seems unlikely to me that the problem is in Git when the only non-Windows C change between the two versions is a one-line file name change.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
Previous: John Paul Adrian GlaubitzNext: John Paul Adrian Glaubitz
Message 2 of 9 in “Testsuite failures on ppc64, sparc64 and s390x (64-bit BE)”
  1. John Paul Adrian GlaubitzJan 4, 2020
  2. brian m. carlsonJan 4, 2020
  3. John Paul Adrian GlaubitzJan 4, 2020
  4. Thomas BraunJan 6, 2020
  5. John Paul Adrian GlaubitzJan 6, 2020
  6. John Paul Adrian GlaubitzJan 4, 2020
  7. brian m. carlsonJan 4, 2020
  8. John Paul Adrian GlaubitzJan 4, 2020
  9. John Paul Adrian GlaubitzFeb 9, 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.