Gerrit hooks doesn't mark open patches in other branches as -verified
by Tal Nisan
Check out this patches for instance: https://gerrit.ovirt.org/#/c/68862
https://gerrit.ovirt.org/#/c/68861
Those are 4.1 and 4.0 patches that are open on master, I'd expect to see
them get -verified from the hooks which they didn't:
- Update Tracker::#1406042::OK, status: POST
- Check Bug-Url::OK
- Check Product::#1406042::OK, product: ovirt-engine
- Check TM::#1406042::OK, found clone candidate ovirt-4.0.zfor target
milestone: ovirt-4.0.7
- Set POST::#1406042::IGNORE, bug is already in 'POST' status
- Check Backport::IGNORE, The patch backported to all newer
branches.(open in 'master' branch/es) found not relevant branch/es:
'ovirt-engine-4.0' (not exist in the newer branches list)
This was the flow before and it made my life easier as I didn't have to
actively search for cherry-picks in all other branches to see if it can be
merged
8 years
[JIRA] (OVIRT-967) add support for notification plugin in standard CI
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-967?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-967:
-------------------------------------------------
Integration with GetBadges Gamification which is working nice until now with the GitHub integration, this will allow oVirt users/developers to get badges / points on having
successful builds ( or lose on failing builds ).
We already got positive feedback from developers on it, and adding another integration will increase visibility of the game [1] and hopefully make oVirt more fun to use/fix bugs/make ci happy.
Fedora has something similar which works well [1]
[1] https://badges.fedoraproject.org/
> add support for notification plugin in standard CI
> --------------------------------------------------
>
> Key: OVIRT-967
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-967
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: eyal edri [Administrator]
> Assignee: infra
>
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
8 years
[JIRA] (OVIRT-952) CI-1 unrelated to patch
by Barak Korren (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-952?page=com.atlassian.jira... ]
Barak Korren commented on OVIRT-952:
------------------------------------
I can't analyse this now, b/c I don't have the logs any more.
We did not wait for two weeks there was a Jira malfunction that made ticket-opening mails to reach the right place for the last two weeks up until a few hours ago.
If this was any real infra issue we probably have already resolved it back then. If it is a repeating issue we probably have other tickets about it.
There is no information on this ticket that I can investigate any further.
(An no, just the Jenkins exception is NEVER enough, the real reason is typically a few scores of lines above it)
This seems reminiscent on OVIRT-938, I wouldn't mark this as duplicate though b/c we're not talking about vdsm check_merged here.
> CI-1 unrelated to patch
> -----------------------
>
> Key: OVIRT-952
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-952
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: danken
> Assignee: infra
>
> An ovirt-engine patch has got -1 for a failing job:
> http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/1...
> Triggered by Gerrit: https://gerrit.ovirt.org/67308
> [EnvInject] - Loading node environment variables.
> FATAL: java.io.IOException: Unexpected termination of the channel
> hudson.remoting.RequestAbortedException: java.io.IOException:
> Unexpected termination of the channel
> at hudson.remoting.Request.abort(Request.java:303)
> at hudson.remoting.Channel.terminate(Channel.java:847)
> at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
> at ......remote call to vm0129.workers-phx.ovirt.org(Native Method)
> at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)
> at hudson.remoting.Request.call(Request.java:172)
> at hudson.remoting.Channel.call(Channel.java:780)
> at hudson.FilePath.act(FilePath.java:1074)
> at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44)
> at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81)
> at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39)
> at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:572)
> at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:492)
> 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: java.io.IOException: Unexpected termination of the channel
> at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
> Caused by: java.io.EOFException
> at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2353)
> at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2822)
> at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:804)
> at java.io.ObjectInputStream.<init>(ObjectInputStream.java:301)
> at hudson.remoting.ObjectInputStreamEx.<init>(ObjectInputStreamEx.java:48)
> at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
> at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
> Performing Post build task...
> Match found for :.* : True
--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
8 years