[JIRA] (OVIRT-972) Fwd: Maintainership request
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-972:
----------------------------------
Summary: Fwd: Maintainership request
Key: OVIRT-972
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-972
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Barak Korren
Assignee: infra
Forwarding to infra-support
---------- Forwarded message ----------
From: Amit Aviram <aaviram(a)redhat.com>
Date: 22 December 2016 at 15:16
Subject: Maintainership request
To: infra <infra(a)ovirt.org>
Hi
We need to add the following users as maintainers of ovirt-imageio please:
derez
laravot
Thanks, Amit
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--
Barak Korren
bkorren(a)redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 11 months
[JIRA] (OVIRT-971) Fwd: changes in gerrit - backport does not include reviewers automatically
by Barak Korren (oVirt JIRA)
Barak Korren created OVIRT-971:
----------------------------------
Summary: Fwd: changes in gerrit - backport does not include reviewers automatically
Key: OVIRT-971
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-971
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Barak Korren
Assignee: infra
Forwarding to infra-support
---------- Forwarded message ----------
From: Yaniv Bronheim <ybronhei(a)redhat.com>
Date: 22 December 2016 at 16:25
Subject: changes in gerrit - backport does not include reviewers automatically
To: infra <infra(a)ovirt.org>
A backport with same change-id as in master branch used to add the
reviewer of the original patch automatically. and also the reviewed-on
label with link to the original patch.
can we add it back?
--
Yaniv Bronhaim.
_______________________________________________
Infra mailing list
Infra(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra
--
Barak Korren
bkorren(a)redhat.com
RHCE, RHCi, RHV-DevOps Team
https://ifireball.wordpress.com/
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 11 months
[JIRA] (OVIRT-938) Fix Jenkins slave connection dying on vdsm check_merged jobs
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-938?page=com.atlassian.jira... ]
Barak Korren commented on OVIRT-938:
------------------------------------
Tested to see if behaviour would different when running on an EL7 host (right now its running in an EL7 chroot on a Fedora host)
http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/777
Same results.
I'm beginning to suspect it something the tests are doing, same hosts run Lago fine for other things.
[~ybronhei(a)redhat.com] Thinks it may be this patch:
https://gerrit.ovirt.org/#/c/68078/
He sent an email to devel, investigation will continue.
> Fix Jenkins slave connection dying on vdsm check_merged jobs
> ------------------------------------------------------------
>
> Key: OVIRT-938
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-938
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Jenkins
> Reporter: Barak Korren
> Assignee: infra
>
> Something in the vdsm build_artifacs job makes the Jenkins slave disconnect when it is running. This in turn makes the cleanup scripts not run on the slave leaving it dirty enough to make the next job on that slave fail.
> Example of this can be seen here:
> http://jenkins.ovirt.org/job/vdsm_master_check-merged-el7-x86_64/692/console
> Relevant log lines:
> {code}
> 21:49:00 Ran 44 tests in 1231.988s
> 21:49:00
> 21:49:00 OK
> 21:49:00 + return 0
> 21:49:00 sh: [13086: 1 (255)] tcsetattr: Inappropriate ioctl for device
> 21:49:00 Took 2464 seconds
> 21:49:00 ===================================
> 21:49:00 logout
> 21:49:01 Slave went offline during the build
> 21:49:01 ERROR: Connection was broken: java.io.IOException: Unexpected termination of the channel
> 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> 21:49:01 Caused by: java.io.EOFException
> 21:49:01 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> 21:49:01 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> 21:49:01 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> 21:49:01 at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301)
> 21:49:01 at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)
> 21:49:01 at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> 21:49:01 at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
> 21:49:01
> 21:49:01 Build step 'Execute shell' marked build as failure
> 21:49:01 Performing Post build task...
> 21:49:01 Match found for :.* : True
> 21:49:01 Logical operation result is TRUE
> 21:49:01 Running script : #!/bin/bash -x
> 21:49:01 echo "shell-scripts/mock_cleanup.sh"
> ... SNIP ...
> 21:49:01 Exception when executing the batch command : no workspace from node hudson.slaves.DumbSlave[fc24-vm06.phx.ovirt.org] which is computer hudson.slaves.SlaveComputer@30863c81 and has channel null
> 21:49:01 Build step 'Post build task' marked build as failure
> 21:49:02 ERROR: Step ?Archive the artifacts? failed: no workspace for vdsm_master_check-merged-el7-x86_64 #692
> 21:49:02 ERROR: Failed to evaluate groovy script.
> 21:49:02 java.lang.NullPointerException: Cannot invoke method child() on null object
> 21:49:02 at org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
> 21:49:02 at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
> 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
> 21:49:02 at org.codehaus.groovy.runtime.callsite.NullCallSite.call(NullCallSite.java:32)
> 21:49:02 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
> 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:108)
> 21:49:02 at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:116)
> 21:49:02 at Script1.run(Script1.groovy:2)
> 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580)
> 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
> 21:49:02 at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)
> 21:49:02 at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SecureGroovyScript.evaluate(SecureGroovyScript.java:166)
> 21:49:02 at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder.perform(GroovyPostbuildRecorder.java:361)
> 21:49:02 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
> 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
> 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
> 21:49:02 at hudson.model.Build$BuildExecution.post2(Build.java:185)
> 21:49:02 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
> 21:49:02 at hudson.model.Run.execute(Run.java:1763)
> 21:49:02 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
> 21:49:02 at hudson.model.ResourceController.execute(ResourceController.java:98)
> 21:49:02 at hudson.model.Executor.run(Executor.java:410)
> 21:49:02 Build step 'Groovy Postbuild' marked build as failure
> 21:49:02 Started calculate disk usage of build
> 21:49:02 Finished Calculation of disk usage of build in 0 seconds
> 21:49:02 Finished: FAILURE
> {code}
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 11 months
[JIRA] (OVIRT-970) Add support for GitHub projects in standard CI
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-970?page=com.atlassian.jira... ]
eyal edri [Administrator] reassigned OVIRT-970:
-----------------------------------------------
Assignee: Pavel Zhukov (was: infra)
This can get started regardless of the projects who wish to join, we need to have the support in templates,triggers,builders first, so when we want to add new projects, the templates will be ready.
Most of the work should start at: (on jenkins repo)
jobs/confs/yaml/triggers/github.yml
jobs/confs/yaml/templates/standard-stage.yml
> Add support for GitHub projects in standard CI
> ----------------------------------------------
>
> Key: OVIRT-970
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-970
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: eyal edri [Administrator]
> Assignee: Pavel Zhukov
>
> Needed for https://ovirt-jira.atlassian.net/browse/OVIRT-874
> We have GitHub templates already in YAML, but they are very specific for Lago and not sure they support all the stages of standard CI.
> We need to update the templates so it'll be easy to add new project from GitHub if we want to.
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
7 years, 11 months