GNU bug report logs - #26443
vim-full 8.0.0494 and above fails its testsuite

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: ng0 <contact.ng0 <at> cryptolab.net>
Subject: bug#26443: closed (Re: bug#26443: vim-full 8.0.0494 and above
 fails its testsuite)
Date: Wed, 28 Jun 2017 11:52:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#26443: vim-full 8.0.0494 and above fails its testsuite

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 26443 <at> debbugs.gnu.org.

-- 
26443: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26443
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: ng0 <ng0 <at> infotropique.org>
To: 26443-done <at> debbugs.gnu.org
Subject: Re: bug#26443: vim-full 8.0.0494 and above fails its testsuite
Date: Wed, 28 Jun 2017 11:51:10 +0000

[Message part 3 (text/plain, inline)]

ng0 transcribed 2.7K bytes:
> Currently vim-full in version 8.0.0494 is failing its testsuite:
…

We are able to build vim-full again. Closing.
-- 
ng0
GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
GnuPG: https://n0is.noblogs.org/my-keys
infotropique: https://www.infotropique.org

[signature.asc (application/pgp-signature, inline)]

[Message part 5 (message/rfc822, inline)]

From: ng0 <contact.ng0 <at> cryptolab.net>
To: bug-guix <at> gnu.org
Subject: vim-full 8.0.0494 and above fails its testsuite
Date: Tue, 11 Apr 2017 09:23:25 +0000

Currently vim-full in version 8.0.0494 is failing its testsuite:

Executed 287 tests


From test_system.vim:
Found errors in Test_system_exmode():
function RunTheTest[24]..Test_system_exmode line 7: Expected '0' but got '/'

Test results:


From test_system.vim:
Found errors in Test_system_exmode():
function RunTheTest[24]..Test_system_exmode line 7: Expected '0' but got '/'
TEST FAILURE
make[2]: *** [Makefile:43: report] Error 1
make[2]: Leaving directory '/tmp/guix-build-vim-full-8.0.0494.drv-0/vim-8.0.0494/src/testdir'
make[1]: *** [Makefile:2030: scripttests] Error 2
make[1]: Leaving directory '/tmp/guix-build-vim-full-8.0.0494.drv-0/vim-8.0.0494/src'
make: *** [Makefile:39: test] Error 2
phase `check' failed after 90.8 seconds
builder for `/gnu/store/819d26h3ijapwmxjw9zykmmq73snmvhz-vim-full-8.0.0494.drv' failed with exit code 1
@ build-failed /gnu/store/819d26h3ijapwmxjw9zykmmq73snmvhz-vim-full-8.0.0494.drv - 1 builder for `/gnu/store/819d26h3ijapwmxjw9zykmmq73snmvhz-vim-full-8.0.0494.drv' failed with exit code 1
guix build: error: build failed: build of `/gnu/store/819d26h3ijapwmxjw9zykmmq73snmvhz-vim-full-8.0.0494.drv' failed



And for version 8.0.0562, where I tried to fix it by just packaging this
version the test phase fails too:

:set im
Vim: Caught deadly signal SEGVery_long_name()
/gnu/store/k7029k5va68lkapbzcycdzj7m5bjb4b8-bash-4.4.12/bin/sh: line 1:  8012 Segmentation fault      ../vim -f -u unix.vim -U NONE --noplugin --not-a-term -S runtest.vim test_edit.vim
make[2]: *** [Makefile:131: test_edit.res] Error 139
make[2]: Leaving directory '/tmp/guix-build-vim-full-8.0.0562.drv-0/vim-8.0.0562/src/testdir'
make[1]: *** [Makefile:2040: scripttests] Error 2
make[1]: Leaving directory '/tmp/guix-build-vim-full-8.0.0562.drv-0/vim-8.0.0562/src'
make: *** [Makefile:39: test] Error 2
phase `check' failed after 64.4 seconds
builder for `/gnu/store/4rglszbz6s06xwrp5q0rdinpp0jh0ds1-vim-full-8.0.0562.drv' failed with exit code 1
@ build-failed /gnu/store/4rglszbz6s06xwrp5q0rdinpp0jh0ds1-vim-full-8.0.0562.drv - 1 builder for `/gnu/store/4rglszbz6s06xwrp5q0rdinpp0jh0ds1-vim-full-8.0.0562.drv' failed with exit code 1
guix build: error: build failed: build of `/gnu/store/4rglszbz6s06xwrp5q0rdinpp0jh0ds1-vim-full-8.0.0562.drv' failed


The issue in patchversion 562 is more more obvious to me than the one we currently
have, but honestly I don't know where to start with debugging this.
Reading the testdir/test_edit.vim test of vim didn't help.
This could be related (or not): https://github.com/vim/vim/issues/1627
Anyone got an github account to further interact with their bugtracker?
Otherwise I'll just signup again.

-- 
PGP and more: https://people.pragmatique.xyz/ng0/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.