Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 657624

Summary: app-editors/gvim-8.0.1298 fails test_autocmd.vim, test_profile.vim, test_system.vim on ppc
Product: Gentoo Linux Reporter: ernsteiswuerfel <erhard_f>
Component: Current packagesAssignee: Vim Maintainers <vim>
Status: RESOLVED DUPLICATE    
Severity: normal CC: jstein
Priority: Normal Keywords: TESTFAILURE
Version: unspecified   
Hardware: PPC   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info
build.log.xz

Description ernsteiswuerfel archtester 2018-06-08 20:18:28 UTC
Created attachment 535324 [details]
emerge --info

Test results:


From test_autocmd.vim:
Found errors in Test_autocmd_bufwipe_in_SessLoadPost():
function RunTheTest[34]..Test_autocmd_bufwipe_in_SessLoadPost line 22: Pattern 'E814' does not match ''
Found errors in Test_autocmd_bufwipe_in_SessLoadPost2():
function RunTheTest[34]..Test_autocmd_bufwipe_in_SessLoadPost2 line 31: Pattern 'SessionLoadPost DONE' does not match ''
Found errors in Test_bufunload_all():
function RunTheTest[34]..Test_bufunload_all line 23: Expected True but got 0

From test_normal.vim:
Found errors in Test_normal22_zet():
function RunTheTest[34]..Test_normal22_zet line 8: Expected [] but got ['1', '2']

From test_profile.vim:
Found errors in Test_profile_file():
function RunTheTest[34]..Test_profile_file line 19: Expected 0 but got 1
Found errors in Test_profile_file_with_cont():
function RunTheTest[34]..Test_profile_file_with_cont line 15: Expected 0 but got 1
Found errors in Test_profile_func():
function RunTheTest[34]..Test_profile_func line 35: Expected 0 but got 1

From test_system.vim:
Found errors in Test_system_exmode():
function RunTheTest[34]..Test_system_exmode line 7: Pattern 'result=0' does not match 'result=1\n'
TEST FAILURE
Comment 1 ernsteiswuerfel archtester 2018-06-08 20:21:12 UTC
Created attachment 535326 [details]
build.log.xz
Comment 2 ernsteiswuerfel archtester 2018-10-20 10:40:56 UTC

*** This bug has been marked as a duplicate of bug 630042 ***