Test failures in the vim-appimage

23 views
Skip to first unread message

Christian Brabandt

unread,
Dec 22, 2020, 6:03:07 AM12/22/20
to vim...@vim.org
Hi,
I just noticed, that the vim-appimage release fails since march with
those error messages in the test:

Excerpt from the logfile: https://api.travis-ci.org/v3/job/750898814/log.txt

Failures:
From test_options.vim:
Found errors in Test_backupskip():
Caught exception in Test_backupskip(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_backupskip, line 68
Found errors in Test_opt_default_cdpath():
Caught exception in Test_opt_default_cdpath(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_opt_default_cdpath, line 13
From test_python3.vim:
Found errors in Test_python3_dict():
command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_dict[2]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_dict[6]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
Found errors in Test_python3_list():
command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_list[2]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_list[6]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'

Does anybody know, what this would cause? For now I have disabled those
tests over there, so that at least a new release can be build and used.

For the first 2 failures, I thought perhaps the vim that is run in a terminal writes
those files to a different directory, causing them to be not found, but
not sure.

And I have no clue at all about the python3 failures.

On a related Note: how hard is it to migrate travis CI scripts to github/actions?

Thanks,
Christian
--
Die Erinnerung ist das einzige Paradies, aus dem wir nicht vertrieben
werden können.
-- Jean Paul (eig. Johann Paul Friedrich Richter)

Bram Moolenaar

unread,
Dec 22, 2020, 6:52:40 AM12/22/20
to vim...@googlegroups.com, Christian Brabandt, vim...@vim.org

Christian Brabandt wrote:

> I just noticed, that the vim-appimage release fails since march with
> those error messages in the test:
>
> Excerpt from the logfile: https://api.travis-ci.org/v3/job/750898814/log.txt
>
> Failures:
> From test_options.vim:
> Found errors in Test_backupskip():
> Caught exception in Test_backupskip(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_backupskip, line 68
> Found errors in Test_opt_default_cdpath():
> Caught exception in Test_opt_default_cdpath(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_opt_default_cdpath, line 13

Perhaps something specific about the path, using backslash where a slash
is expected?

> From test_python3.vim:
> Found errors in Test_python3_dict():
> command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_dict[2]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_dict[6]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> Found errors in Test_python3_list():
> command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_list[2]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_list[6]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
>
> Does anybody know, what this would cause? For now I have disabled those
> tests over there, so that at least a new release can be build and used.
>
> For the first 2 failures, I thought perhaps the vim that is run in a terminal writes
> those files to a different directory, causing them to be not found, but
> not sure.
>
> And I have no clue at all about the python3 failures.

The tests check for very specific messages from the Python code. We
don't really care about the exact message, so long as the error is
given. I'll make it accept both messages we have seen.


--
Never enter the boss's office unless it's absolutely necessary. Every boss
saves one corner of the desk for useless assignments that are doled out like
Halloween candy to each visitor.
(Scott Adams - The Dilbert principle)

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

Christian Brabandt

unread,
Dec 22, 2020, 7:01:49 AM12/22/20
to vim...@googlegroups.com

On Di, 22 Dez 2020, Bram Moolenaar wrote:

>
> Christian Brabandt wrote:
>
> > I just noticed, that the vim-appimage release fails since march with
> > those error messages in the test:
> >
> > Excerpt from the logfile: https://api.travis-ci.org/v3/job/750898814/log.txt
> >
> > Failures:
> > From test_options.vim:
> > Found errors in Test_backupskip():
> > Caught exception in Test_backupskip(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_backupskip, line 68
> > Found errors in Test_opt_default_cdpath():
> > Caught exception in Test_opt_default_cdpath(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_opt_default_cdpath, line 13
>
> Perhaps something specific about the path, using backslash where a slash
> is expected?

I'll try to investigate this later.

>
> > From test_python3.vim:
> > Found errors in Test_python3_dict():
> > command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_dict[2]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> > command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_dict[6]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> > Found errors in Test_python3_list():
> > command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_list[2]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> > command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_python3_list[6]..AssertException line 9: Pattern 'Vim(py3):SystemError: <built-in function eval> returned NULL without setting an error' does not match 'Vim(py3):SystemError: error return without exception set'
> >
> > Does anybody know, what this would cause? For now I have disabled those
> > tests over there, so that at least a new release can be build and used.
> >
> > For the first 2 failures, I thought perhaps the vim that is run in a terminal writes
> > those files to a different directory, causing them to be not found, but
> > not sure.
> >
> > And I have no clue at all about the python3 failures.
>
> The tests check for very specific messages from the Python code. We
> don't really care about the exact message, so long as the error is
> given. I'll make it accept both messages we have seen.

Ah great, thanks. Then I can at least allow this one again.

Best,
Christian
--
Unmöglich kann ein naturhaftes Begehren vergeblich sein.
-- Thomas von Aquin

Christian Brabandt

unread,
Dec 23, 2020, 3:48:26 AM12/23/20
to vim...@googlegroups.com, vim...@vim.org

On Di, 22 Dez 2020, Bram Moolenaar wrote:

>
> Christian Brabandt wrote:
>
> > I just noticed, that the vim-appimage release fails since march with
> > those error messages in the test:
> >
> > Excerpt from the logfile: https://api.travis-ci.org/v3/job/750898814/log.txt
> >
> > Failures:
> > From test_options.vim:
> > Found errors in Test_backupskip():
> > Caught exception in Test_backupskip(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_backupskip, line 68
> > Found errors in Test_opt_default_cdpath():
> > Caught exception in Test_opt_default_cdpath(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_opt_default_cdpath, line 13
>
> Perhaps something specific about the path, using backslash where a slash
> is expected?

This might be a Travis Error. I see:
"create mount dir error: No such file or directory"

don't know why this would happen


Mit freundlichen Grüßen
Christian
--
Der Mensch leidet an einer fatalen Spätzündung: Er begreift alles erst
in der nächsten Generation.
-- Stanislaw Jerzy Lec (eig. S. J. de Tusch-Letz)

Christian Brabandt

unread,
Dec 23, 2020, 6:32:32 AM12/23/20
to vim...@googlegroups.com

On Mi, 23 Dez 2020, Christian Brabandt wrote:

>
> On Di, 22 Dez 2020, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote:
> >
> > > I just noticed, that the vim-appimage release fails since march with
> > > those error messages in the test:
> > >
> > > Excerpt from the logfile: https://api.travis-ci.org/v3/job/750898814/log.txt
> > >
> > > Failures:
> > > From test_options.vim:
> > > Found errors in Test_backupskip():
> > > Caught exception in Test_backupskip(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_backupskip, line 68
> > > Found errors in Test_opt_default_cdpath():
> > > Caught exception in Test_opt_default_cdpath(): Vim(call):E484: Can't open file Xtestout @ command line..script /home/travis/build/vim/vim-appimage/vim/src/testdir/runtest.vim[468]..function RunTheTest[39]..Test_opt_default_cdpath, line 13
> >
> > Perhaps something specific about the path, using backslash where a slash
> > is expected?
>
> This might be a Travis Error. I see:
> "create mount dir error: No such file or directory"
>
> don't know why this would happen

I think the failure comes from the fact, that VIMPROG was set when
executing the testdir Makefile and GetVimProg() failed to understand
that correctly. At least I could work-around it, by not setting VIMPROG=

Best,
Christian
--
Es gibt sicherlich nicht so viele Männer mit großem Vermögen auf der
Welt wie hübsche Frauen, die sie verdienen.
-- Jane Austen
Reply all
Reply to author
Forward
0 new messages