I wrote:
> The 'git svn' tests are not run in Travis because the perl
> subversion bindings are not installed. I haven't made time
> to try installing them and running the tests in Travis to
> see if the failures occur there, but I suspect they would.
Before anyone spends time wondering about thi
On Mon, Jan 29, 2018 at 12:06:27PM +, Eric Wong wrote:
> Todd Zullinger 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)
>
Eric Wong wrote:
> Todd Zullinger wrote:
> Just a guess, but it might be related to destruction order.
> Running t9128 on a 32-bit Pentium-M, it took me 39 tries to
> fail.
>
> diff --git a/git-svn.perl b/git-svn.perl
> index 76a75d0b3d..2ba14269bb 100755
> --- a/git-svn.perl
> +++ b/git-svn.perl
Todd Zullinger wrote:
> brian m. carlson wrote:
> > 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-s
brian m. carlson wrote:
> 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.
>
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
6 matches
Mail list logo
