[JIRA] (OVIRT-1021) Trigger a job on a github repo change
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1021?page=com.atlassian.jir... ]
Barak Korren commented on OVIRT-1021:
-------------------------------------
{quote}
I'd like to run a job on a github repo, without the need to add he complete automation folder.
But maybe it is enough if I can come up with a freeform job when writing it in JJB YAML.
{quote}
This would just mean you will be maintaining the code for your job in the '{{jenkins}}' repo instead of in your own repo where it belongs (Try asking the Travis devs to store your '{{.travis}}' file in one of their repos...).
This would also mean that you are not going to enjoy any of the effors made over the years to improve the oVirt CI infra, in essence you are going to have to re-learn all the lessons already learned.
And come on, its not like its a massive task to create an '{{automation}}' directory, its just a directory with simple scripts in it, and requirement files if needed. I think the learning curve to making it is far shallower then learning the whole Jenkins Job Builder syntax and how all the different system components interlock together. Being simple scripts, you get the benefit of being able to also run them locally to test without needing the whole CI infrastructure to do it.
> Trigger a job on a github repo change
> -------------------------------------
>
> Key: OVIRT-1021
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1021
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Fabian Deutsch
> Assignee: infra
>
> Hey,
> we are pushing some changes to this github repository:
> https://github.com/kubevirt/demo
> The test autpmation requires nesting, thus it would be nice if this repo could be run on jenkins.
> Could our jenkins instance get a plugin to be able to hook it up to github i.e.
> https://wiki.jenkins-ci.org/display/JENKINS/GitHub+plugin
> The other thing would be how to store the job specification in the repo.
> Here it would be nice if we could dump a travis-ci-like file into the repo and let the job inerprete this.
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
7 years, 5 months
Re: [ovirt-devel] 3.6 upstream deps failure
by Sandro Bonazzola
Adding infra since nothing changed on devel side about this.
Il 13/Gen/2017 05:26 PM, "Yaniv Kaul" <ykaul(a)redhat.com> ha scritto:
> From http://jenkins.ovirt.org/job/ovirt-system-tests_master_
> check-patch-fc24-x86_64/804/console :
>
> *16:04:45* + yum install --nogpgcheck -y --downloaddir=/dev/shm ntp ovirt-engine ovirt-log-collector 'ovirt-engine-extension-aaa-ldap*'*16:04:45* Error: Package: ovirt-engine-3.6.10.3-0.0.master.20170101161303.git5f35a1a.el6.noarch (alocalsync)*16:04:45* Requires: ovirt-iso-uploader >= 3.6.0*16:04:45* Error: Package: ovirt-engine-backend-3.6.10.3-0.0.master.20170101161303.git5f35a1a.el6.noarch (alocalsync)*16:04:45* Requires: ovirt-host-deploy-java >= 1.4.0*16:04:45* Error: Package: ovirt-engine-tools-backup-3.6.10.3-0.0.master.20170101161303.git5f35a1a.el6.noarch (alocalsync)*16:04:45* Requires: otopi >= 1.4.1*16:04:45* Error: Package: ovirt-engine-setup-plugin-ovirt-engine-3.6.10.3-0.0.master.20170101161303.git5f35a1a.el6.noarch (alocalsync)*16:04:45* Requires: ovirt-engine-extension-aaa-jdbc*16:04:45* Error: Package: ovirt-setup-lib-1.0.2-1.el6.noarch (alocalsync)*16:04:45* Requires: otopi*16:04:45* Error: Package: ovirt-engine-backend-3.6.10.3-0.0.master.20170101161303.git5f35a1a.el6.noarch (alocalsync)*16:04:45* Requires: ovirt-engine-extension-aaa-jdbc*16:04:45* Error: Package: ovirt-engine-setup-base-3.6.10.3-0.0.master.20170101161303.git5f35a1a.el6.noarch (alocalsync)*16:04:45* Requires: otopi >= 1.4.1*16:04:45* Error: Package: ovirt-engine-extension-aaa-ldap-setup-1.1.6-0.0.master.20160630130757.gitea5658b.el6.noarch (alocalsync)*16:04:45* Requires: otopi >= 1.4.0
>
>
> _______________________________________________
> Devel mailing list
> Devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/devel
>
7 years, 5 months
[JIRA] (OVIRT-1027) cockpit-ovirt_3.6_build-artifacts is failing
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-1027?page=com.atlassian.jir... ]
Daniel Belenky reassigned OVIRT-1027:
-------------------------------------
Assignee: Ryan Barry (was: infra)
> cockpit-ovirt_3.6_build-artifacts is failing
> --------------------------------------------
>
> Key: OVIRT-1027
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1027
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Reporter: Daniel Belenky
> Assignee: Ryan Barry
>
> [~sbonazzo(a)redhat.com]
> cockpit-ovirt_3.6_build-artifacts-el7-x86_64 job is failing, and in a result of that the nightly publisher doesn't publish nightly rpms.
> The errors seen in the log:
> 12:46:53 > cockpit-ovirt-dashboard(a)0.0.1 test /home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1/dashboard
> 12:46:53 > eslint src --ext js,jsx
> 12:46:53
> 12:46:53 *sh: eslint: command not found*
> 12:46:53 npm ERR! Test failed. See above for more details.
> 12:46:53 npm WARN Local package.json exists, but node_modules missing, did you mean to install?
> 12:46:53
> 12:46:53 npm ERR! Linux 4.8.15-200.fc24.x86_64
> 12:46:53 npm ERR! argv "/usr/share/ovirt-engine-nodejs/bin/node" "/usr/share/ovirt-engine-nodejs/bin/npm" "run" "build"
> 12:46:53 npm ERR! node v6.9.1
> 12:46:53 npm ERR! npm v3.10.8
> 12:46:53 npm ERR! code ELIFECYCLE
> 12:46:53 npm ERR! cockpit-ovirt-dashboard(a)0.0.1 build: `npm test && NODE_ENV=production webpack -p --progress`
> 12:46:53 npm ERR! Exit status 1
> 12:46:53 npm ERR!
> 12:46:53 npm ERR! Failed at the cockpit-ovirt-dashboard(a)0.0.1 build script 'npm test && NODE_ENV=production webpack -p --progress'.
> 12:46:53 npm ERR! Make sure you have the latest version of node.js and npm installed.
> 12:46:53 npm ERR! If you do, this is most likely a problem with the cockpit-ovirt-dashboard package,
> 12:46:53 npm ERR! not with npm itself.
> 12:46:53 npm ERR! Tell the author that this fails on your system:
> 12:46:53 npm ERR! npm test && NODE_ENV=production webpack -p --progress
> 12:46:53 npm ERR! You can get information on how to open an issue for this project with:
> 12:46:53 npm ERR! npm bugs cockpit-ovirt-dashboard
> 12:46:53 npm ERR! Or if that isn't available, you can get their info via:
> 12:46:53 npm ERR! npm owner ls cockpit-ovirt-dashboard
> 12:46:53 npm ERR! There is likely additional logging output above.
> 12:46:53 npm WARN Local package.json exists, but node_modules missing, did you mean to install?
> 12:46:53
> 12:46:53 npm ERR! Please include the following file with any support request:
> 12:46:53 npm ERR! /home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1/dashboard/npm-debug.log
> 12:46:53 make[2]: *** [ovirt-dashboard] Error 1
> 12:46:53 make[2]: Leaving directory `/home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1/dashboard'
> 12:46:53 make[1]: *** [all-recursive] Error 1
> 12:46:53 make[1]: Leaving directory `/home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1'
> 12:46:53 error: Bad exit status from /var/tmp/rpm-tmp.tbsqw1 (%build)
> 12:46:53
> 12:46:53
> 12:46:53 RPM build errors:
> 12:46:53 Bad exit status from /var/tmp/rpm-tmp.tbsqw1 (%build)
> 12:46:53 make: *** [rpm] Error 1
> Looks like there was an issue with building eslint
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
7 years, 5 months
[JIRA] (OVIRT-1027) cockpit-ovirt_3.6_build-artifacts is failing
by Daniel Belenky (oVirt JIRA)
Daniel Belenky created OVIRT-1027:
-------------------------------------
Summary: cockpit-ovirt_3.6_build-artifacts is failing
Key: OVIRT-1027
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1027
Project: oVirt - virtualization made easy
Issue Type: Bug
Reporter: Daniel Belenky
Assignee: infra
[~sbonazzo(a)redhat.com]
cockpit-ovirt_3.6_build-artifacts-el7-x86_64 job is failing, and in a result of that the nightly publisher doesn't publish nightly rpms.
The errors seen in the log:
12:46:53 > cockpit-ovirt-dashboard(a)0.0.1 test /home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1/dashboard
12:46:53 > eslint src --ext js,jsx
12:46:53
12:46:53 *sh: eslint: command not found*
12:46:53 npm ERR! Test failed. See above for more details.
12:46:53 npm WARN Local package.json exists, but node_modules missing, did you mean to install?
12:46:53
12:46:53 npm ERR! Linux 4.8.15-200.fc24.x86_64
12:46:53 npm ERR! argv "/usr/share/ovirt-engine-nodejs/bin/node" "/usr/share/ovirt-engine-nodejs/bin/npm" "run" "build"
12:46:53 npm ERR! node v6.9.1
12:46:53 npm ERR! npm v3.10.8
12:46:53 npm ERR! code ELIFECYCLE
12:46:53 npm ERR! cockpit-ovirt-dashboard(a)0.0.1 build: `npm test && NODE_ENV=production webpack -p --progress`
12:46:53 npm ERR! Exit status 1
12:46:53 npm ERR!
12:46:53 npm ERR! Failed at the cockpit-ovirt-dashboard(a)0.0.1 build script 'npm test && NODE_ENV=production webpack -p --progress'.
12:46:53 npm ERR! Make sure you have the latest version of node.js and npm installed.
12:46:53 npm ERR! If you do, this is most likely a problem with the cockpit-ovirt-dashboard package,
12:46:53 npm ERR! not with npm itself.
12:46:53 npm ERR! Tell the author that this fails on your system:
12:46:53 npm ERR! npm test && NODE_ENV=production webpack -p --progress
12:46:53 npm ERR! You can get information on how to open an issue for this project with:
12:46:53 npm ERR! npm bugs cockpit-ovirt-dashboard
12:46:53 npm ERR! Or if that isn't available, you can get their info via:
12:46:53 npm ERR! npm owner ls cockpit-ovirt-dashboard
12:46:53 npm ERR! There is likely additional logging output above.
12:46:53 npm WARN Local package.json exists, but node_modules missing, did you mean to install?
12:46:53
12:46:53 npm ERR! Please include the following file with any support request:
12:46:53 npm ERR! /home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1/dashboard/npm-debug.log
12:46:53 make[2]: *** [ovirt-dashboard] Error 1
12:46:53 make[2]: Leaving directory `/home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1/dashboard'
12:46:53 make[1]: *** [all-recursive] Error 1
12:46:53 make[1]: Leaving directory `/home/jenkins/workspace/cockpit-ovirt_3.6_build-artifacts-el7-x86_64/cockpit-ovirt/tmp.repos/BUILD/cockpit-ovirt-0.9.1-0.0.1'
12:46:53 error: Bad exit status from /var/tmp/rpm-tmp.tbsqw1 (%build)
12:46:53
12:46:53
12:46:53 RPM build errors:
12:46:53 Bad exit status from /var/tmp/rpm-tmp.tbsqw1 (%build)
12:46:53 make: *** [rpm] Error 1
Looks like there was an issue with building eslint
--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
7 years, 5 months
please use a single patch for a single task
by Sandro Bonazzola
Looking at:
https://gerrit.ovirt.org/#/c/69438/3
but there are several others in gerrit for different projects
taking this one as example just because it make me loose the evening on it.
"adding cli for 4.1 experimental repos" as stated in the header of the patch
has totally nothing to do with the body of the patch:
"- also dropped fc23 since its eol"
which just dropped all the fc23 artifacts from the publisher causing:
- cockpit-ovirt for fc23 failing to build due to missing dependencies
- publisher 4.0 nightly failing due to missing cockpit-ovirt for fc23
Now I unblocked the publisher for 4.0 with: https://gerrit.ovirt.org/70402
but if infra decided to drop fc23 support since fc23 gone EOL, please do it
completely.
If a patch need a "also did..." it needs a separate patch.
Thanks,
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 5 months
Build failed in Jenkins: ovirt_3.6_publish-rpms_nightly #320
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/320/>
------------------------------------------
Started by timer
[EnvInject] - Loading node environment variables.
Building on master in workspace <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/ws/>
[WS-CLEANUP] Deleting project workspace...
[workspace] $ /bin/bash -xe /tmp/hudson9074633346306085222.sh
+ rm -rf <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/ws/artifacts>
+ mkdir <http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/ws/artifacts>
Copied 8 artifacts from "ovirt-host-deploy_3.6_create-rpms-el6-x86_64_merged" build number 2
Copied 10 artifacts from "ovirt-host-deploy_3.6_create-rpms-el7-x86_64_merged" build number 1
Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-el6-x86_64" build number 16
Copied 4 artifacts from "ovirt-engine-sdk_3.6_build-artifacts-el7-x86_64" build number 18
Copied 14 artifacts from "otopi_3.6_create-rpms-el6-x86_64_merged" build number 4
Copied 19 artifacts from "otopi_3.6_create-rpms-el7-x86_64_merged" build number 4
Copied 8 artifacts from "ovirt-vmconsole_3.6_create-rpms-el6-x86_64_merged" build number 16
Copied 8 artifacts from "ovirt-vmconsole_3.6_create-rpms-el7-x86_64_merged" build number 16
Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-el6-x86_64" build number 23
Copied 4 artifacts from "ovirt-engine-cli_3.6_build-artifacts-el7-x86_64" build number 23
Copied 7 artifacts from "unboundid-ldapsdk_3.6_create-rpms-el6-x86_64_merged" build number 4
Copied 7 artifacts from "unboundid-ldapsdk_3.6_create-rpms-el7-x86_64_merged" build number 8
Copied 7 artifacts from "ovirt-iso-uploader_3.6_create-rpms-el6-x86_64_merged" build number 1
Copied 7 artifacts from "ovirt-iso-uploader_3.6_create-rpms-el7-x86_64_merged" build number 1
Copied 7 artifacts from "ovirt-log-collector_3.6_create-rpms-el6-x86_64_merged" build number 1
Copied 7 artifacts from "ovirt-log-collector_3.6_create-rpms-el7-x86_64_merged" build number 1
Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_3.6_create-rpms-el6-x86_64_merged" build number 8
Copied 8 artifacts from "ovirt-engine-extension-aaa-ldap_3.6_create-rpms-el7-x86_64_merged" build number 8
Copied 9 artifacts from "ovirt-engine-extension-aaa-misc_3.6_create-rpms-el6-x86_64_merged" build number 3
Copied 9 artifacts from "ovirt-engine-extension-aaa-misc_3.6_create-rpms-el7-x86_64_merged" build number 3
Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_3.6_create-rpms-el6-x86_64_merged" build number 3
Copied 7 artifacts from "ovirt-engine-extension-logger-log4j_3.6_create-rpms-el7-x86_64_merged" build number 3
Copied 5 artifacts from "ovirt-dwh_3.6_build-artifacts-el6-x86_64" build number 6
Copied 5 artifacts from "ovirt-dwh_3.6_build-artifacts-el7-x86_64" build number 4
Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_3.6_create-rpms-el6-x86_64_merged" build number 1
Copied 7 artifacts from "ovirt-engine-extension-aaa-jdbc_3.6_create-rpms-el7-x86_64_merged" build number 1
Copied 3 artifacts from "ovirt-setup-lib_3.6_build-artifacts-el6-x86_64" build number 7
Copied 3 artifacts from "ovirt-setup-lib_3.6_build-artifacts-el7-x86_64" build number 4
Copied 5 artifacts from "vdsm-jsonrpc-java_3.6_build-artifacts-el6-x86_64" build number 18
Copied 5 artifacts from "vdsm-jsonrpc-java_3.6_build-artifacts-el7-x86_64" build number 15
Copied 25 artifacts from "ovirt-engine_3.6_build-artifacts-el7-x86_64" build number 1892
Copied 24 artifacts from "ovirt-engine_3.6_build-artifacts-el6-x86_64" build number 1893
Copied 3 artifacts from "mom_3.6_build-artifacts-el7-x86_64" build number 13
Copied 7 artifacts from "ovirt-engine-sdk-java_3.6_create-rpms-el6-x86_64_merged" build number 11
Copied 7 artifacts from "ovirt-engine-sdk-java_3.6_create-rpms-el7-x86_64_merged" build number 13
Copied 4 artifacts from "ovirt-scheduler-proxy_3.6_build-artifacts-el6-x86_64" build number 1
Copied 6 artifacts from "ovirt-optimizer_3.6_build-artifacts-el6-x86_64" build number 1
Copied 6 artifacts from "ovirt-optimizer_3.6_build-artifacts-el7-x86_64" build number 1
Copied 8 artifacts from "ioprocess_0.15_create-rpms-el7-x86_64_merged" build number 3
Copied 45 artifacts from "vdsm_3.6_build-artifacts-el7-x86_64" build number 101
Copied 6 artifacts from "ovirt-hosted-engine-ha_3.6_create-rpms-el7-x86_64_merged" build number 24
Copied 4 artifacts from "ovirt-hosted-engine-setup_3.6_build-artifacts-el7-x86_64" build number 25
Copied 9 artifacts from "qemu_3.6_create-rpms-el7-x86_64_merged" build number 17
Copied 9 artifacts from "qemu_3.6_create-rpms-el7-ppc64le_merged" build number 13
Copied 16 artifacts from "ovirt-node_ovirt-3.6_build-artifacts-el7-x86_64" build number 25
Copied 4 artifacts from "ovirt-node_ovirt-3.6_create-iso-el7_merged" build number 205
Copied 4 artifacts from "ovirt-node-plugin-vdsm_ovirt-3.6_build-artifacts-el7-x86_64" build number 5
Copied 4 artifacts from "ovirt-node-plugin-hosted-engine_ovirt-3.6_build-artifacts-el7-x86_64" build number 5
Copied 11 artifacts from "ovirt-appliance_ovirt-3.6_build-artifacts-el7-x86_64" build number 72
Copied 7 artifacts from "ovirt-reports_3.6_create-rpms-el6-x86_64_merged" build number 1
Copied 7 artifacts from "ovirt-reports_3.6_create-rpms-el7-x86_64_merged" build number 1
Copied 6 artifacts from "ovirt-live_3.6_build-artifacts-el7-x86_64" build number 12
ERROR: Unable to find a build for artifact copy from: cockpit-ovirt_3.6_build-artifacts-el7-x86_64
7 years, 5 months
Build failed in Jenkins: ovirt_4.0_system-tests #775
by jenkins＠jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/775/changes>
Changes:
[Your Name] network utils: rename attach/detach vlans
[Sandro Bonazzola] cockpit-ovirt: add missing check-patch jobs
[Sandro Bonazzola] publisher: 4.0: drop cockpit-ovirt for fc23
------------------------------------------
[...truncated 80.81 KB...]
## Sat Jan 14 02:50:13 UTC 2017 Finished env: el7:epel-7-x86_64
## took 64 seconds
## rc = 1
##########################################################
##! ERROR vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
##! Last 20 log entries: ./mock_logs.otDWD5mT/mocker-epel-7-x86_64.el7.basic_suite_4.0.sh/basic_suite_4.0.sh.log
##!
@ Cleanup prefix:
# Stop prefix:
# Stop prefix:
* Stop vms:
* Stop vms: Success (in 0:00:00)
* Stop nets:
* Stop nets: Success (in 0:00:00)
# Stop prefix: Success (in 0:00:00)
# Tag prefix as uninitialized:
# Tag prefix as uninitialized: Success (in 0:00:00)
@ Cleanup prefix: Success (in 0:00:00)
+ echo '----------- Cleaning with lago done'
----------- Cleaning with lago done
+ [[ 0 != \0 ]]
+ echo '======== Cleanup done'
======== Cleanup done
+ exit 0
+ exit
Took 46 seconds
===================================
##!
##! ERROR ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
##!########################################################
Collecting mock logs
'./mock_logs.otDWD5mT/mocker-epel-7-x86_64.el7.basic_suite_4.0.sh' -> 'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.basic_suite_4.0.sh'
'./mock_logs.otDWD5mT/mocker-epel-7-x86_64.el7.clean_rpmdb' -> 'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.clean_rpmdb'
'./mock_logs.otDWD5mT/mocker-epel-7-x86_64.el7.init' -> 'exported-artifacts/mock_logs/mocker-epel-7-x86_64.el7.init'
##########################################################
Build step 'Execute shell' marked build as failure
Performing Post build task...
Match found for :.* : True
Logical operation result is TRUE
Running script : #!/bin/bash -xe
echo 'shell_scripts/system_tests.collect_logs.sh'
#
# Required jjb vars:
# version
#
VERSION=4.0
SUITE_TYPE=
WORKSPACE="$PWD"
OVIRT_SUITE="$SUITE_TYPE_suite_$VERSION"
TESTS_LOGS="$WORKSPACE/ovirt-system-tests/exported-artifacts"
rm -rf "$WORKSPACE/exported-artifacts"
mkdir -p "$WORKSPACE/exported-artifacts"
if [[ -d "$TESTS_LOGS" ]]; then
mv "$TESTS_LOGS/"* "$WORKSPACE/exported-artifacts/"
fi
[ovirt_4.0_system-tests] $ /bin/bash -xe /tmp/hudson7604104769176783064.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=4.0
+ SUITE_TYPE=
+ WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/>
+ OVIRT_SUITE=4.0
+ TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...>
+ rm -rf <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/775/artifact/exported...>
+ mkdir -p <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/775/artifact/exported...>
+ [[ -d <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...> ]]
+ mv <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...> <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/775/artifact/exported...>
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Match found for :.* : True
Logical operation result is TRUE
Running script : #!/bin/bash -x
echo "shell-scripts/mock_cleanup.sh"
# Make clear this is the cleanup, helps reading the jenkins logs
cat <<EOC
_______________________________________________________________________
#######################################################################
# #
# CLEANUP #
# #
#######################################################################
EOC
shopt -s nullglob
WORKSPACE="${WORKSPACE:-$PWD}"
UMOUNT_RETRIES="${UMOUNT_RETRIES:-3}"
UMOUNT_RETRY_DELAY="${UMOUNT_RETRY_DELAY:-1s}"
safe_umount() {
local mount="${1:?}"
local attempt
for ((attempt=0 ; attempt < $UMOUNT_RETRIES ; attempt++)); do
# If this is not the 1st time through the loop, Sleep a while to let
# the problem "solve itself"
[[ attempt > 0 ]] && sleep "$UMOUNT_RETRY_DELAY"
# Try to umount
sudo umount --lazy "$mount" && return 0
# See if the mount is already not there despite failing
findmnt --kernel --first "$mount" > /dev/null && return 0
done
echo "ERROR: Failed to umount $mount."
return 1
}
# restore the permissions in the working dir, as sometimes it leaves files
# owned by root and then the 'cleanup workspace' from jenkins job fails to
# clean and breaks the jobs
sudo chown -R "$USER" "$WORKSPACE"
sudo chmod -R u+w "$WORKSPACE"
# stop any processes running inside the chroot
failed=false
mock_confs=("$WORKSPACE"/*/mocker*)
# Clean current jobs mockroot if any
for mock_conf_file in "${mock_confs[@]}"; do
[[ "$mock_conf_file" ]] || continue
echo "Cleaning up mock $mock_conf"
mock_root="${mock_conf_file##*/}"
mock_root="${mock_root%.*}"
my_mock="/usr/bin/mock"
my_mock+=" --configdir=${mock_conf_file%/*}"
my_mock+=" --root=${mock_root}"
my_mock+=" --resultdir=$WORKSPACE"
#TODO: investigate why mock --clean fails to umount certain dirs sometimes,
#so we can use it instead of manually doing all this.
echo "Killing all mock orphan processes, if any."
$my_mock \
--orphanskill \
|| {
echo "ERROR: Failed to kill orphans on $chroot."
failed=true
}
mock_root="$(\
grep \
-Po "(?<=config_opts\['root'\] = ')[^']*" \
"$mock_conf_file" \
)" || :
[[ "$mock_root" ]] || continue
mounts=($(mount | awk '{print $3}' | grep "$mock_root")) || :
if [[ "$mounts" ]]; then
echo "Found mounted dirs inside the chroot $chroot. Trying to umount."
fi
for mount in "${mounts[@]}"; do
safe_umount "$mount" || failed=true
done
done
# Clean any leftover chroot from other jobs
for mock_root in /var/lib/mock/*; do
this_chroot_failed=false
mounts=($(cut -d\ -f2 /proc/mounts | grep "$mock_root" | sort -r)) || :
if [[ "$mounts" ]]; then
echo "Found mounted dirs inside the chroot $mock_root." \
"Trying to umount."
fi
for mount in "${mounts[@]}"; do
safe_umount "$mount" && continue
# If we got here, we failed $UMOUNT_RETRIES attempts so we should make
# noise
failed=true
this_chroot_failed=true
done
if ! $this_chroot_failed; then
sudo rm -rf "$mock_root"
fi
done
# remove mock caches that are older then 2 days:
find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0 | \
xargs -0 -tr sudo rm -rf
# We make no effort to leave around caches that may still be in use because
# packages installed in them may go out of date, so may as well recreate them
# Drop all left over libvirt domains
for UUID in $(virsh list --all --uuid); do
virsh destroy $UUID || :
sleep 2
virsh undefine --remove-all-storage --storage vda --snapshots-metadata $UUID || :
done
if $failed; then
echo "Cleanup script failed, propegating failure to job"
exit 1
fi
[ovirt_4.0_system-tests] $ /bin/bash -x /tmp/hudson5019109105133048955.sh
+ echo shell-scripts/mock_cleanup.sh
shell-scripts/mock_cleanup.sh
+ cat
_______________________________________________________________________
#######################################################################
# #
# CLEANUP #
# #
#######################################################################
+ shopt -s nullglob
+ WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/>
+ UMOUNT_RETRIES=3
+ UMOUNT_RETRY_DELAY=1s
+ sudo chown -R jenkins <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/>
+ sudo chmod -R u+w <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/>
+ failed=false
+ mock_confs=("$WORKSPACE"/*/mocker*)
+ for mock_conf_file in '"${mock_confs[@]}"'
+ [[ -n <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...> ]]
+ echo 'Cleaning up mock '
Cleaning up mock
+ mock_root=mocker-epel-7-x86_64.el7.cfg
+ mock_root=mocker-epel-7-x86_64.el7
+ my_mock=/usr/bin/mock
+ my_mock+=' --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests'>
+ my_mock+=' --root=mocker-epel-7-x86_64.el7'
+ my_mock+=' --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/'>
+ echo 'Killing all mock orphan processes, if any.'
Killing all mock orphan processes, if any.
+ /usr/bin/mock --configdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests> --root=mocker-epel-7-x86_64.el7 --resultdir=<http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/> --orphanskill
WARNING: Could not find required logging config file: <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests....> Using default...
INFO: mock.py version 1.2.21 starting (python version = 3.5.1)...
Start: init plugins
INFO: selinux enabled
Finish: init plugins
Start: run
Finish: run
++ grep -Po '(?<=config_opts\['\''root'\''\] = '\'')[^'\'']*' <http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/ws/ovirt-system-tests...>
+ mock_root=epel-7-x86_64-6f628e6dc1a827c86d5e1bd9d3b3d38b
+ [[ -n epel-7-x86_64-6f628e6dc1a827c86d5e1bd9d3b3d38b ]]
+ mounts=($(mount | awk '{print $3}' | grep "$mock_root"))
++ mount
++ awk '{print $3}'
++ grep epel-7-x86_64-6f628e6dc1a827c86d5e1bd9d3b3d38b
+ :
+ [[ -n '' ]]
+ find /var/cache/mock/ -mindepth 1 -maxdepth 1 -type d -mtime +2 -print0
+ xargs -0 -tr sudo rm -rf
++ virsh list --all --uuid
+ false
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 1
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Archiving artifacts
7 years, 5 months
oVirt infra daily report - unstable production jobs - 200
by jenkins＠jenkins.phx.ovirt.org
------=_Part_123_1876741748.1484434805666
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Good morning!
Attached is the HTML page with the jenkins status report. You can see it also here:
- http://jenkins.ovirt.org/job/system_jenkins-report/200//artifact/exported...
Cheers,
Jenkins
------=_Part_123_1876741748.1484434805666
Content-Type: text/html; charset=us-ascii; name=upstream_report.html
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=upstream_report.html
Content-ID: <upstream_report.html>
<!DOCTYPE html><head><style type="text/css">
table.gridtable {
border-collapse: collapse;
table-layout:fixed;
width:1600px;
font-family: monospace;
font-size:13px;
}
.head {
font-size:20px;
font-family: arial;
}
.sub {
font-size:18px;
background-color:#e5e5e5;
font-family: arial;
}
pre {
font-family: monospace;
display: inline;
white-space: pre-wrap;
white-space: -moz-pre-wrap !important;
white-space: -pre-wrap;
white-space: -o-pre-wrap;
word-wrap: break-word;
}
</style>
</head>
<body>
<table class="gridtable" border=2>
<tr><th colspan=2 class=head>
RHEVM CI Jenkins Daily Report - 14/01/2017
</th></tr><tr><th colspan=2 class=sub>
<font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font>
</th></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_buil...">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x...">ovirt-system-tests_master_check-patch-fc24-x86_64</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_image-ng-system-tests/">ovirt_3.6_image-ng-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_publish-rpms_nightly/">ovirt_3.6_publish-rpms_nightly</a>
</td><td>
Collects RPMs from all oVirt projects (3.6 branches) and publish them to resources.ovirt.org yum repository.<br> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h..."> jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_3.6_system-tests/">ovirt_3.6_system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.0_he-system-tests/">ovirt_4.0_he-system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.0_system-tests/">ovirt_4.0_system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/ovirt_4.1_system-tests/">ovirt_4.1_system-tests</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/system-backup_jenkins_old_ovirt_org/">system-backup_jenkins_old_ovirt_org</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_3.6/">test-repo_ovirt_experimental_3.6</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
<tr><td>
<a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.0/">test-repo_ovirt_experimental_4.0</a>
</td><td>
This job is automatically updated by jenkins job builder, any manual
change will be lost in the next update. If you want to make permanent
changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;h...">
jenkins</a> repo.
<!-- Managed by Jenkins Job Builder -->
</td></tr>
------=_Part_123_1876741748.1484434805666--
7 years, 5 months