Mailinglist Archive: yast-devel (251 mails)

< Previous Next >
[yast-devel] Build failed in Jenkins: yast-security-HEAD #132
  • From: hudson@xxxxxxx
  • Date: Wed, 31 Jul 2013 10:49:50 +0200 (CEST)
  • Message-id: <1182868055.196.1375260590136.JavaMail.jenkins@river>
See <http://river.suse.de/job/yast-security-HEAD/132/changes>

Changes:

[yast-devel] YCP Killer: Unify YaST module structure

[yast-devel] YCP Killer: Apply changes needed for Ruby translation

[yast-devel] YCP Killer: Translate YCP files into Ruby

[yast-devel] YCP Killer: Regenerate Makefile.am files in all source directories

[yast-devel] version 3.0.0

------------------------------------------
[...truncated 114 lines...]
++ [[ 1 == 1 ]]
++ echo 'Using autotools for building'
Using autotools for building
++ export BUILDDIR=<http://river.suse.de/job/yast-security-HEAD/ws/checkout>
++ BUILDDIR=<http://river.suse.de/job/yast-security-HEAD/ws/checkout>
++ export
PACKAGEDIR=<http://river.suse.de/job/yast-security-HEAD/ws/checkout/package>
++ PACKAGEDIR=<http://river.suse.de/job/yast-security-HEAD/ws/checkout/package>
++ mkdir -p <http://river.suse.de/job/yast-security-HEAD/ws/rpm>
++ mkdir -p <http://river.suse.de/job/yast-security-HEAD/ws/rpm/rpms>
++ mkdir -p <http://river.suse.de/job/yast-security-HEAD/ws/rpm/rpmbuild>
++ mkdir -p <http://river.suse.de/job/yast-security-HEAD/ws/rpm/rpmbuildroot>
++ mkdir -p <http://river.suse.de/job/yast-security-HEAD/ws/.artifacts>
++ mkdir -p <http://river.suse.de/job/yast-security-HEAD/ws/OBS>
++ cat
+ PACKAGENAME=yast-security
+ PACKAGENAME=yast2-security
+ cd <http://river.suse.de/job/yast-security-HEAD/ws/checkout>
+ make -f Makefile.cvs
y2tool y2autoconf
y2autoconf: Generating toplevel configure.ac
y2tool y2automake
y2automake: Copying automakefiles for inclusion
y2automake: Generating toplevel Makefile.am
autoreconf --force --install
./configure --prefix=/usr --libdir=/usr/lib64
checking build system type... x86_64-suse-linux-gnu
checking host system type... x86_64-suse-linux-gnu
checking target system type... x86_64-suse-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for xgettext... /usr/bin/xgettext
checking for ycpdoc... /usr/lib/YaST2/bin/ycpdoc
checking for ycpmakedep... /usr/lib/YaST2/bin/ycpmakedep
checking for ycpc... /usr/bin/ycpc
checking for /usr/share/YaST2/data/testsuite/Makefile.testsuite... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating agents/Makefile
config.status: creating doc/autodocs/Makefile
config.status: creating doc/Makefile
config.status: creating src/Makefile
config.status: creating testsuite/Makefile
+ make
Making all in agents
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/agents'>
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/agents'>
Making all in doc
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
Making all in autodocs
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc/autodocs'>
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc/autodocs'>
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
make[2]: Nothing to be done for `all-am'.
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
Making all in src
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/src'>
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/src'>
Making all in testsuite
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make -f /usr/share/YaST2/data/testsuite/Makefile.testsuite
RPMNAME=yast2-security srcdir=.
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout'>
make[1]: Nothing to be done for `all-am'.
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout'>
+ make check
Making check in agents
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/agents'>
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/agents'>
Making check in doc
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
Making check in autodocs
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc/autodocs'>
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc/autodocs'>
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
make[2]: Nothing to be done for `check-am'.
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/doc'>
Making check in src
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/src'>
make[1]: Nothing to be done for `check'.
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/src'>
Making check in testsuite
make[1]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make -f /usr/share/YaST2/data/testsuite/Makefile.testsuite
RPMNAME=yast2-security srcdir=.
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make check-DEJAGNU check-local
make[2]: Entering directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
Making a new site.exp file ...
srcdir='.'; export srcdir; \
EXPECT=expect; export EXPECT; \
runtest=runtest; \
if /bin/sh -c "$runtest --version" > /dev/null 2>&1; then \
exit_status=0; l='yast2-security'; for tool in $l; do \
if $runtest --tool $tool --srcdir $srcdir ; \
then :; else exit_status=1; fi; \
done; \
else echo "WARNING: could not find 'runtest'" 1>&2; :;\
fi; \
exit $exit_status
WARNING: Couldn't find tool init file
Test Run By root on Wed Jul 31 10:49:48 2013
Native configuration is x86_64-suse-linux-gnu

=== yast2-security tests ===

Schedule of variations:
unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./yast2-security.test/testsuite.exp ...

Checking started

Running Import ...
FAIL: Wrong stderr for Import

The diff follows...

--- tests/Import.err 2013-01-22 11:59:45.000000000 +0100
+++ tmp.err.Import 2013-07-31 10:49:48.000000000 +0200
@@ -0,0 +1,2 @@
+2013-07-31 10:49:48 <3> app42(26989) [Interpreter] modules/Testsuite.rb:42
Loading module 'Security' failed
+2013-07-31 10:49:48 <3> app42(26989) [libycp] Import.cc(import):97 No matching
component found

FAIL: Wrong stderr for Import
See the diff above.
Running Level1 ...
FAIL: Wrong stderr for Level1

The diff follows...

--- tests/Level1.err 2013-01-22 11:59:45.000000000 +0100
+++ tmp.err.Level1 2013-07-31 10:49:49.000000000 +0200
@@ -0,0 +1,2 @@
+2013-07-31 10:49:49 <3> app42(27015) [Interpreter] modules/Testsuite.rb:42
Loading module 'Security' failed
+2013-07-31 10:49:49 <3> app42(27015) [libycp] Import.cc(import):97 No matching
component found

FAIL: Wrong stderr for Level1
See the diff above.
Running Level2 ...
FAIL: Wrong stderr for Level2

The diff follows...

--- tests/Level2.err 2013-01-22 11:59:45.000000000 +0100
+++ tmp.err.Level2 2013-07-31 10:49:49.000000000 +0200
@@ -0,0 +1,2 @@
+2013-07-31 10:49:49 <3> app42(27041) [Interpreter] modules/Testsuite.rb:42
Loading module 'Security' failed
+2013-07-31 10:49:49 <3> app42(27041) [libycp] Import.cc(import):97 No matching
component found

FAIL: Wrong stderr for Level2
See the diff above.
Running Level3 ...
FAIL: Wrong stderr for Level3

The diff follows...

--- tests/Level3.err 2013-01-22 11:59:45.000000000 +0100
+++ tmp.err.Level3 2013-07-31 10:49:49.000000000 +0200
@@ -0,0 +1,2 @@
+2013-07-31 10:49:49 <3> app42(27067) [Interpreter] modules/Testsuite.rb:42
Loading module 'Security' failed
+2013-07-31 10:49:49 <3> app42(27067) [libycp] Import.cc(import):97 No matching
component found

FAIL: Wrong stderr for Level3
See the diff above.
Running Read ...
FAIL: Wrong stderr for Read

The diff follows...

--- tests/Read.err 2013-01-22 11:59:45.000000000 +0100
+++ tmp.err.Read 2013-07-31 10:49:49.000000000 +0200
@@ -0,0 +1,2 @@
+2013-07-31 10:49:49 <3> app42(27093) [Interpreter] modules/Testsuite.rb:42
Loading module 'Security' failed
+2013-07-31 10:49:49 <3> app42(27093) [libycp] Import.cc(import):97 No matching
component found

FAIL: Wrong stderr for Read
See the diff above.
Running Write ...
FAIL: Wrong stderr for Write

The diff follows...

--- tests/Write.err 2013-01-22 11:59:45.000000000 +0100
+++ tmp.err.Write 2013-07-31 10:49:50.000000000 +0200
@@ -0,0 +1,2 @@
+2013-07-31 10:49:49 <3> app42(27119) [Interpreter] modules/Testsuite.rb:42
Loading module 'Security' failed
+2013-07-31 10:49:49 <3> app42(27119) [libycp] Import.cc(import):97 No matching
component found

FAIL: Wrong stderr for Write
See the diff above.

Checking finished


=== yast2-security Summary ===

# of unexpected failures 12
make[2]: *** [check-DEJAGNU] Error 1
make[2]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make[1]: *** [check-am] Error 2
make[1]: Leaving directory
`<http://river.suse.de/job/yast-security-HEAD/ws/checkout/testsuite'>
make: *** [check-recursive] Error 1
++ error_exit 2
++ echo 'ERROR: detected exitcode 2'
ERROR: detected exitcode 2
++ cleanup
++ echo '==> Running cleanup'
==> Running cleanup
++ rm -f
<http://river.suse.de/job/yast-security-HEAD/ws/ICECC/40c0ab7e54f59a1e4e493c1ea90a882a.tar.gz>
++ footer_and_exit 1
++ '[' -z 1 ']'
++ MYEXIT=1
++ '[' 1 == 0 ']'
++ ascii_failed
++ cat

( )
( ) (
) _ )
( \_
_(_\ \)__
(____\___))

build failed

++ exit 1
Build step 'Execute shell' marked build as failure
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
Follow Ups
References