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

t9128 failing randomly with svn 1.9?

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jan 29, 2018, 01:51 UTC
Message-ID
<20180129015134.GN431130@genre.crustytoothpaste.net>

While running tests for my object_id part 11 series, I noticed a random segfault in git svn while running t9128. I've reproduced this on a different machine as well, using both Subversion 1.9.5 and 1.9.7 (Debian stable and unstable). It is reproducible on master.

When the test fails, it fails on the "git svn tag tag3" step, and I get the following:

Copying file:///home/bmc/checkouts/git/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk at r2 to file:///home/bmc/checkouts/git/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/tags/tag3... Found possible branch point: file:///home/bmc/checkouts/git/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk => file:///home/bmc/checkouts/git/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/tags/tag3, 2 Found branch parent: (refs/remotes/origin/tags/tag3) 0604824a81a121ad05aaf8caea65d8ca8f86c018 Following parent with do_switch Successfully followed parent r7 = f8467f2cee3bcead03e84cb51cf44f467a87457d (refs/remotes/origin/tags/tag3) error: git-svn died of signal 11

Doing the following three times, I had two crashes.
(set -e; for i in $(seq 1 20); do (cd t && ./t9128-git-svn-cmd-branch.sh --verbose); done)

I'm not really familiar with git svn or its internals, and I didn't see anything recently on the list about this. Is this issue known?

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
Next: Todd Zullinger
Message 1 of 8 in “t9128 failing randomly with svn 1.9?”
  1. brian m. carlsonJan 29, 2018
  2. Todd ZullingerJan 29, 2018
  3. Eric WongJan 29, 2018
  4. Todd ZullingerJan 29, 2018
  5. git-svn: control destruction order to avoid segfaultEric Wong, Jan 29, 2018
  6. Junio C HamanoJan 30, 2018
  7. brian m. carlsonJan 30, 2018
  8. Todd ZullingerJan 30, 2018

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.