Open wdpypere opened 9 years ago
@wdpypere quattor/maven-tools#42 may have fixed this, now it is merged are you able to check?
I'm sorry to say they are still there. 2 consecutive runs (on fedora 21), 2 different failures (1st useraccess, 2nd modprobe):
[INFO] Expanding /home/wdpypere/.m2/repository/org/quattor/maven/build-scripts/1.42/build-scripts-1.42-scripts.tar.gz to /tmp/tmp1033519180353150359.tar
[INFO] Expanding: /tmp/tmp1033519180353150359.tar into /home/wdpypere/workspace/configuration-modules-core/ncm-useraccess/target/dependency
[INFO]
[INFO] --- panc-maven-plugin:10.2:check-syntax (check-generated-pan-syntax) @ useraccess ---
[INFO]
[INFO] --- exec-maven-plugin:1.2:exec (pod2man) @ useraccess ---
Generating man page from target/lib/perl/NCM/Component/useraccess.pm
Creating man page for target/doc/pod/NCM/Component/useraccess.pod, NCM::Component::useraccess.8[INFO]
[INFO] --- exec-maven-plugin:1.2:exec (prove) @ useraccess ---
src/test/perl/00-load.t ..... ok
src/test/perl/close.t ....... ok
src/test/perl/configure.t ... ok
src/test/perl/files.t ....... ok
Uncaught exception!!! Calling stack is:
LC::Exception::throw_error called at /home/wdpypere/quattor-libs/lib/perl/LC/Fatal.pm line 204
LC::Fatal::stat called at /home/wdpypere/quattor-libs/lib/perl/LC/Check.pm line 883
LC::Check::file called at /home/wdpypere/quattor-libs/lib/perl/CAF/FileWriter.pm line 195
CAF::FileWriter::close called at /home/wdpypere/quattor-libs/lib/perl/CAF/FileWriter.pm line 280
CAF::FileWriter::DESTROY called at src/test/perl/kerberos.t line 0
(eval) called at src/test/perl/kerberos.t line 0
*** stat(target/test/ssh_test): No such file or directory
[INFO] Expanding /home/wdpypere/.m2/repository/org/quattor/maven/build-scripts/1.42/build-scripts-1.42-scripts.tar.gz to /tmp/tmp7582592963591555727.tar
[INFO] Expanding: /tmp/tmp7582592963591555727.tar into /home/wdpypere/workspace/configuration-modules-core/ncm-modprobe/target/dependency
[INFO]
[INFO] --- panc-maven-plugin:10.2:check-syntax (check-generated-pan-syntax) @ modprobe ---
[INFO]
[INFO] --- exec-maven-plugin:1.2:exec (pod2man) @ modprobe ---
Generating man page from target/lib/perl/NCM/Component/modprobe.pm
Creating man page for target/doc/pod/NCM/Component/modprobe.pod, NCM::Component::modprobe.8[INFO]
[INFO] --- exec-maven-plugin:1.2:exec (prove) @ modprobe ---
src/test/perl/00-load.t .......... ok
src/test/perl/configure.t ........ ok
src/test/perl/generator.t ........ ok
Prototype mismatch: sub main::NCM::Component::modprobe::directory_contents: none vs ($) at /usr/share/perl5/vendor_perl/Exporter.pm line 66.
at /home/wdpypere/workspace/configuration-modules-core/ncm-modprobe/target/lib/perl/NCM/Component/modprobe.pm line 31.
src/test/perl/mkinitrd.t ......... ok
src/test/perl/pod-syntax.t ....... ok
Uncaught exception!!! Calling stack is:
LC::Exception::throw_error called at /home/wdpypere/quattor-libs/lib/perl/LC/Check.pm line 886
LC::Check::file called at /home/wdpypere/quattor-libs/lib/perl/CAF/FileWriter.pm line 195
CAF::FileWriter::close called at /home/wdpypere/quattor-libs/lib/perl/CAF/FileWriter.pm line 280
CAF::FileWriter::DESTROY called at src/test/perl/process_aliases.t line 0
(eval) called at src/test/perl/process_aliases.t line 0
Damn. Well this gets bumped to the next release then I guess...
just reran tests my fedora 21 laptop and I have 4 succeeded runs out of 8 (3 failures on useraccess and 1 on modprobe). However, on a vm with SL6 (setup with build_all_repos.sh) I have no failures (out of 8 runs). So maybe it is an environment issue on my machine.
it's perl cleanup issue. we need something like https://metacpan.org/pod/ogd, but it's not that easy to "just use"
Sometimes tests fail on the destroy. output from useraccess fail:
output from sysctl fail: