oVirt infra daily report - unstable production jobs - 184
by jenkins@jenkins.phx.ovirt.org
------=_Part_26_1573741518.1483052405897
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/184//artifact/exported...
Cheers,
Jenkins
------=_Part_26_1573741518.1483052405897
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 - 29/12/2016
</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_master_system-tests/">ovirt_master_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_master_system-tests_on_demand/">ovirt_master_system-tests_on_demand</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 -->
<br><br>Job disabled - The old Jenkins is probably not up any more
</td></tr>
------=_Part_26_1573741518.1483052405897--
7 years, 10 months
[JIRA] (OVIRT-993) add manual jobs for OST to allow running on custom repos
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-993?page=com.atlassian.jira... ]
eyal edri [Administrator] updated OVIRT-993:
--------------------------------------------
Epic Link: OVIRT-400
> add manual jobs for OST to allow running on custom repos
> --------------------------------------------------------
>
> Key: OVIRT-993
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-993
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: eyal edri [Administrator]
> Assignee: infra
> Priority: High
>
> It has been requested by dev to be able to run easily OST jobs on an open patch(es).
> We plan to refactor experimental flow completely when we move to Zuul, but it will take some time until we have a new job fully working that we can utilize also to allow manual testing.
> Fortunately we recently added new 'build-on-demand' jobs which adds capability to generate new rpms from any open patch.
> With some effort, we can utilize existing system jobs to accept custom repo list and run on rpms created by the 'build-on-demand' jobs using repoman.
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 10 months
[JIRA] (OVIRT-993) add manual jobs for OST to allow running on custom repos
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-993:
-----------------------------------------------
Summary: add manual jobs for OST to allow running on custom repos
Key: OVIRT-993
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-993
Project: oVirt - virtualization made easy
Issue Type: Task
Reporter: eyal edri [Administrator]
Assignee: infra
Priority: High
It has been requested by dev to be able to run easily OST jobs on an open patch(es).
We plan to refactor experimental flow completely when we move to Zuul, but it will take some time until we have a new job fully working that we can utilize also to allow manual testing.
Fortunately we recently added new 'build-on-demand' jobs which adds capability to generate new rpms from any open patch.
With some effort, we can utilize existing system jobs to accept custom repo list and run on rpms created by the 'build-on-demand' jobs using repoman.
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 10 months
Build failed in Jenkins: ovirt_master_system-tests_manual #1
by jenkins@jenkins.phx.ovirt.org
See <http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/1/>
------------------------------------------
Started by user Eyal Edri
[EnvInject] - Loading node environment variables.
Building remotely on ovirt-srv21.phx.ovirt.org (fc24 phx integ-tests physical) in workspace <http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/ws/>
Cloning the remote Git repository
Cloning repository git://gerrit.ovirt.org/ovirt-system-tests.git
> git init <http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/ws/ovirt-sy...> # timeout=10
Fetching upstream changes from git://gerrit.ovirt.org/ovirt-system-tests.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress git://gerrit.ovirt.org/ovirt-system-tests.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url git://gerrit.ovirt.org/ovirt-system-tests.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url git://gerrit.ovirt.org/ovirt-system-tests.git # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
> git clean -fdx # timeout=10
Pruning obsolete local branches
Fetching upstream changes from git://gerrit.ovirt.org/ovirt-system-tests.git
> git -c core.askpass=true fetch --tags --progress git://gerrit.ovirt.org/ovirt-system-tests.git $GERRIT_REFSPEC --prune
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from git://gerrit.ovirt.org/ovirt-system-tests.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:766)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1022)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1053)
at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:129)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1269)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:607)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1738)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: hudson.plugins.git.GitException: Command "git -c core.askpass=true fetch --tags --progress git://gerrit.ovirt.org/ovirt-system-tests.git $GERRIT_REFSPEC --prune" returned status code 128:
stdout:
stderr: fatal: Couldn't find remote ref $GERRIT_REFSPEC
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1640)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1388)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:62)
at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:313)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:152)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:332)
at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
at ......remote call to ovirt-srv21.phx.ovirt.org(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:252)
at hudson.remoting.Channel.call(Channel.java:781)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor251.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy60.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:764)
... 12 more
ERROR: null
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=master
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_master_system-tests_manual] $ /bin/bash -xe /tmp/hudson6909699149264508915.sh
+ echo shell_scripts/system_tests.collect_logs.sh
shell_scripts/system_tests.collect_logs.sh
+ VERSION=master
+ SUITE_TYPE=
+ WORKSPACE=<http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/ws/>
+ OVIRT_SUITE=master
+ TESTS_LOGS=<http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/ws/ovirt-sy...>
+ rm -rf <http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/1/artifact/...>
+ mkdir -p <http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/1/artifact/...>
+ [[ -d <http://jenkins.ovirt.org/job/ovirt_master_system-tests_manual/ws/ovirt-sy...> ]]
POST BUILD TASK : SUCCESS
END OF POST BUILD TASK : 0
Recording test results
ERROR: Step ?Publish JUnit test result report? failed: No test report files were found. Configuration error?
Archiving artifacts
7 years, 10 months
[JIRA] (OVIRT-903) master-to-master CI upgrade tests
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-903?page=com.atlassian.jira... ]
eyal edri [Administrator] reassigned OVIRT-903:
-----------------------------------------------
Assignee: Daniel Belenky (was: infra)
reminder to add to upgrade suites
> master-to-master CI upgrade tests
> ---------------------------------
>
> Key: OVIRT-903
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-903
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Yedidyah Bar David
> Assignee: Daniel Belenky
>
> Hi all,
> Recently a patch to the engine [1] added a new package,
> with a certain set of dependencies, which broke upgrade.
> This is similar to [2] but for a new package.
> CI wasn't affected, I think because of [3].
> To make CI test such flows, we should have a job that:
> 1. Builds, installs and sets up the version we want to test
> 2. Pushes a dummy change to the local git repo (to force
> a new version), build the patched tree, create a yum repo
> with the build and add it to yum.repos.d.
> 3. yum update
> 4. engine-setup
> Another option is to revert [3], or to duplicate - have
> both "upgrade current to self" and "upgrade latest snapshot
> to current". The downside is that it will be checked later
> than above plan - instead of in the same build, will only
> be tested in the first build that uses the snapshot after
> it was updated, and also will be misleading, as the reason
> why that job failed will not be apparent (which was why
> [3] was added).
> Please handle. I can of course try to help. Best,
> [1] https://gerrit.ovirt.org/66999
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1321249
> [3] https://gerrit.ovirt.org/67263
> --
> Didi
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 10 months