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

Re: t9128 failing randomly with svn 1.9?

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Jan 30, 2018, 00:25 UTC
Message-ID
<20180130002539.GO431130@genre.crustytoothpaste.net>
In-Reply-To
<20180129120627.al2xvx4yhhvwn6ih@untitled>
On Mon, Jan 29, 2018 at 12:06:27PM +0000, Eric Wong wrote:
Show 14 quoted lines
> Todd Zullinger <tmz@pobox.com> wrote:
> diff --git a/git-svn.perl b/git-svn.perl
> index 76a75d0b3d..2ba14269bb 100755
> --- a/git-svn.perl
> +++ b/git-svn.perl
> @@ -1200,6 +1200,11 @@ sub cmd_branch {
>  	$ctx->copy($src, $rev, $dst)
>  		unless $_dry_run;
>  
> +	# Release resources held by ctx before creating another SVN::Ra
> +	# so destruction is orderly.  This seems necessary Subversion 1.9.5
> +	# to avoid segfaults.
> +	$ctx = undef;
> +

This may be the right thing to do. I've seen a decent number of cases in Perl where global destruction randomly causes segfaults.

Show 8 quoted lines
>  	$gs->fetch_all;
>  }
>  
> 
> I'll be looping t9128, t9141 and t9167 with that for a few
> hours or day.  Will report back sooner if it fails.
> I'm on an ancient 32-bit system, I guess you guys encountered
> it on 64-bit machines?

Yes, both systems are 64-bit Debian systems, one stable, and the other unstable.

-- 
brian m. carlson / brian with sandals: Houston, Texas, US
https://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: https://keybase.io/bk2204
Previous: Junio C HamanoNext: Todd Zullinger
Message 7 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.