[JIRA] (OVIRT-1368) http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/23419/

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1368:


 Summary: 
http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/23419/
 Key: OVIRT-1368
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1368
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Hi,

Could someone help me to understand what has failed in ${subject} build?

Thanks in advance,
Yevgeny



--
This message was sent by Atlassian JIRA
(v1000.929.2#100040)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1293) Plugin "reviewers" failed to load

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1293:


 Summary: Plugin "reviewers" failed to load
 Key: OVIRT-1293
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1293
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra






--
This message was sent by Atlassian JIRA
(v1000.870.3#100039)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28340#comment-28340
 ] 

Yevgeny Zaspitsky commented on OVIRT-1226:
--

How do you know that findBugs job should've being running? There is no
evidence for starting that on patchset 4 in the comments.
There are comments for the 2 other jobs that mention their number out of 3,
but there is nothing telling a thing about the 3rd job.

On Tue, Mar 7, 2017 at 8:00 PM, Yevgeny Zaspitsky (oVirt JIRA) <



> https://gerrit.ovirt.org/#/c/73161 marked with CI-1
> ---
>
> Key: OVIRT-1226
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful
> CI runs it had.



--
This message was sent by Atlassian JIRA
(v1000.789.5#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28339#comment-28339
 ] 

Yevgeny Zaspitsky commented on OVIRT-1226:
--

The comment in gerrit includes only 2 jobs and both are successful.
Here is the copy of the comment by Jenkins CI:

Patch Set 4: Continuous-Integration-1

Build Failed

http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/19428/
: SUCCESS

http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc25-x86_64/3480/
: SUCCESS

On Tue, Mar 7, 2017 at 1:03 PM, Gil Shinar (oVirt JIRA) <



> https://gerrit.ovirt.org/#/c/73161 marked with CI-1
> ---
>
> Key: OVIRT-1226
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful
> CI runs it had.



--
This message was sent by Atlassian JIRA
(v1000.789.5#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28308#comment-28308
 ] 

Yevgeny Zaspitsky commented on OVIRT-1226:
--

at 01/03 13:14

On Tue, Mar 7, 2017 at 9:41 AM, Gil Shinar (oVirt JIRA) <



> https://gerrit.ovirt.org/#/c/73161 marked with CI-1
> ---
>
> Key: OVIRT-1226
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful
> CI runs it had.



--
This message was sent by Atlassian JIRA
(v1000.789.5#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1226) https://gerrit.ovirt.org/#/c/73161 marked with CI-1

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1226:


 Summary: https://gerrit.ovirt.org/#/c/73161 marked with CI-1
 Key: OVIRT-1226
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1226
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Jenkins CI marked the ${subject} patch with CI-1, despite of 2 successful
CI runs it had.



--
This message was sent by Atlassian JIRA
(v1000.789.5#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1184) ovirt jenkins whitelist

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1184:


 Summary: ovirt jenkins whitelist
 Key: OVIRT-1184
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1184
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Please add me (yzasp...@redhat.com/yevge...@gmail.com) to the whitelist.



--
This message was sent by Atlassian JIRA
(v1000.773.3#100032)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1146) http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/12562/ failed

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1146:


 Summary: 
http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/12562/ 
failed
 Key: OVIRT-1146
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1146
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


The $subject build failed for a reason unrelated to the patch it tries to
check.

>From the job log it looks like it misses some rpms:

Error: Package: perl-Unicode-Normalize-1.25-2.fc24.x86_64 (@fedora)
   Requires: libperl.so.5.22()(64bit)
   Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates)
   libperl.so.5.22()(64bit)
   Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24)
  ~libperl.so.5.24()(64bit)
   Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24)
   libperl.so.5.22()(64bit)
Error: Package: perl-PathTools-3.62-3.fc24.x86_64 (@updates)
   Requires: libperl.so.5.22()(64bit)
   Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates)
   libperl.so.5.22()(64bit)
   Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24)
  ~libperl.so.5.24()(64bit)
   Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24)
   libperl.so.5.22()(64bit)
Error: Package: libselinux-2.5-13.fc25.i686 (fedora-updates-fc24)
   Requires: libsepol(x86-32) >= 2.5-10
   Installing: libsepol-2.5-3.fc24.i686 (fedora-base-fc24)
   libsepol(x86-32) = 2.5-3.fc24
   Installed: libsepol-2.5-10.fc24.x86_64 (@updates)
  ~libsepol(x86-64) = 2.5-10.fc24
Error: Package: python3-devel-3.5.1-7.fc24.x86_64 (fedora-base-fc24)
   Requires: python3-libs(x86-64) = 3.5.1-7.fc24
   Installed: python3-libs-3.5.2-3.fc24.x86_64 (@updates)
   python3-libs(x86-64) = 3.5.2-3.fc24
   Available: python3-libs-3.5.1-7.fc24.x86_64 (fedora-base-fc24)
   python3-libs(x86-64) = 3.5.1-7.fc24
Error: Package: perl-MIME-Base64-3.15-349.fc24.x86_64 (@fedora)
   Requires: libperl.so.5.22()(64bit)
   Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates)
   libperl.so.5.22()(64bit)
   Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24)
  ~libperl.so.5.24()(64bit)
   Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24)
   libperl.so.5.22()(64bit)
Error: Package: 3:perl-Socket-2.024-1.fc24.x86_64 (@updates)
   Requires: libperl.so.5.22()(64bit)
   Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates)
   libperl.so.5.22()(64bit)
   Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24)
  ~libperl.so.5.24()(64bit)
   Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24)
   libperl.so.5.22()(64bit)
Error: Package: perl-Data-Dumper-2.158-348.fc24.x86_64 (@fedora)
   Requires: libperl.so.5.22()(64bit)
   Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates)
   libperl.so.5.22()(64bit)
   Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24)
  ~libperl.so.5.24()(64bit)
   Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24)
   libperl.so.5.22()(64bit)
Error: Package: perl-TermReadKey-2.33-4.fc24.x86_64 (@fedora)
   Requires: libperl.so.5.22()(64bit)
   Removing: 4:perl-libs-5.22.3-368.fc24.x86_64 (@updates)
   libperl.so.5.22()(64bit)
   Updated By: 4:perl-libs-5.24.1-383.fc25.x86_64 (fedora-updates-fc24)
  ~libperl.so.5.24()(64bit)
   Available: 4:perl-libs-5.22.2-359.fc24.x86_64 (fedora-base-fc24)
   libperl.so.5.22()(64bit)
Error: Package: ncurses-libs-6.0-5.20160116.fc24.i686 (fedora-base-fc24)
   Requires: ncurses-base = 6.0-5.20160116.fc24
   Installed: ncurses-base-6.0-6.20160709.fc24.noarch (@updates)
   ncurses-base = 6.0-6.20160709.fc24
   Available: ncurses-base-6.0-5.20160116.fc24.noarch (fedora-base-fc24)
   ncurses-base = 6.0-5.20160116.fc24
Error: Package: libselinux-2.5-13.fc25.i686 (fedora-updates-fc24)
   Requires: libsepol(x86-32) >= 2.5-10
   Available: libsepol-2.5-3.fc24.i686 (fedora-base-fc24)
   libsepol(x86-32) = 2.5-3.fc24
   Installed: libsepol-2.5-10.fc24.x86_64 (@updates)
  ~libsepol(x86-64) = 2.5-10.fc24



--
This message was sent by Atlassian JIRA
(v1000.747.1#100028)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1072) ovirt-engine_master_upgrade-from-4.0_el7_created on a pure Java change

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=26234#comment-26234
 ] 

Yevgeny Zaspitsky commented on OVIRT-1072:
--

Here is another failure
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_created/2081

On Mon, Jan 23, 2017 at 5:45 PM, Yevgeny Zaspitsky 
wrote:

> The $subject job [1] fails from time to time even though it checks a pure
> Java patch that cannot influence on the upgrade process.
>
> [1] - http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-
> from-4.0_el7_created/13182/
>

> ovirt-engine_master_upgrade-from-4.0_el7_created on a pure Java change
> --
>
> Key: OVIRT-1072
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1072
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> The $subject job [1] fails from time to time even though it checks a pure
> Java patch that cannot influence on the upgrade process.
> [1] -
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_created/13182/



--
This message was sent by Atlassian JIRA
(v1000.695.3#100025)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1072) ovirt-engine_master_upgrade-from-4.0_el7_created on a pure Java change

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1072:


 Summary: ovirt-engine_master_upgrade-from-4.0_el7_created on a 
pure Java change
 Key: OVIRT-1072
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1072
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


The $subject job [1] fails from time to time even though it checks a pure
Java patch that cannot influence on the upgrade process.

[1] -
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_created/13182/



--
This message was sent by Atlassian JIRA
(v1000.695.3#100025)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-1040) ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25814#comment-25814
 ] 

Yevgeny Zaspitsky commented on OVIRT-1040:
--

What failed is maven and/or one of its plugins which is a Java code, but
isn't our code.
The fact that the same patch passed the job after re-trigger means either
the node is faulty (if the successfull run was on another node) or some
network/server/etc external resource wasn't functioning in that period of
time (or both).

On Tue, Jan 17, 2017 at 5:08 PM, Yevgeny Zaspitsky 



> ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed
> -
>
> Key: OVIRT-1040
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1040
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> The $subject job [1] has failed upon a reason that doesn't seems to be
> related to the patch it checks.
> From the check_patch.sh.log:
> [INFO] --- exec-maven-plugin:1.4.0:java (generate-enums-jaxb) @
> restapi-definition ---
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-log4j12/1.7.7/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> [WARNING]
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapList(AbstractMapBasedMultimap.java:332)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapCollection(AbstractMapBasedMultimap.java:324)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.get(AbstractMapBasedMultimap.java:308)
>   at 
> com.google.common.collect.AbstractListMultimap.get(AbstractListMultimap.java:66)
>   at 
> com.google.common.collect.ArrayListMultimap.get(ArrayListMultimap.java:66)
>   at 
> org.jboss.weld.annotated.enhanced.jlr.EnhancedAnnotatedTypeImpl.getDeclaredEnhancedFields(EnhancedAnnotatedTypeImpl.java:427)
>   at 
> org.jboss.weld.injection.InjectionPointFactory.getFieldInjectionPoints(InjectionPointFactory.java:210)
>   at 
> org.jboss.weld.injection.producer.DefaultInjector.(DefaultInjector.java:56)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.(ResourceInjector.java:58)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:49)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.(BeanInjectionTarget.java:63)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:47)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:128)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:87)
>   at org.jboss.weld.bean.ManagedBean.(ManagedBean.java:100)
>   at org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:80)
>   at 
> org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:261)
>   at 
> org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:228)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:78)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:75)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
>   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)
>   ... 1 more
> [WARNING] thread Thread[weld-worker-1,5,weld-workers] was interrupted
> but is still alive after waiting at least 15000msecs
> [WARNING] thread

[JIRA] (OVIRT-1040) ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25813#comment-25813
 ] 

Yevgeny Zaspitsky commented on OVIRT-1040:
--

Looks like the problem is in the Jenkins node that ran the job that failed.
Can we check the historical success rate of that node?

On Tue, Jan 17, 2017 at 4:51 PM, eyal edri [Administrator] (oVirt JIRA) <



> ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed
> -
>
> Key: OVIRT-1040
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1040
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> The $subject job [1] has failed upon a reason that doesn't seems to be
> related to the patch it checks.
> From the check_patch.sh.log:
> [INFO] --- exec-maven-plugin:1.4.0:java (generate-enums-jaxb) @
> restapi-definition ---
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-log4j12/1.7.7/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> [WARNING]
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapList(AbstractMapBasedMultimap.java:332)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapCollection(AbstractMapBasedMultimap.java:324)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.get(AbstractMapBasedMultimap.java:308)
>   at 
> com.google.common.collect.AbstractListMultimap.get(AbstractListMultimap.java:66)
>   at 
> com.google.common.collect.ArrayListMultimap.get(ArrayListMultimap.java:66)
>   at 
> org.jboss.weld.annotated.enhanced.jlr.EnhancedAnnotatedTypeImpl.getDeclaredEnhancedFields(EnhancedAnnotatedTypeImpl.java:427)
>   at 
> org.jboss.weld.injection.InjectionPointFactory.getFieldInjectionPoints(InjectionPointFactory.java:210)
>   at 
> org.jboss.weld.injection.producer.DefaultInjector.(DefaultInjector.java:56)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.(ResourceInjector.java:58)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:49)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.(BeanInjectionTarget.java:63)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:47)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:128)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:87)
>   at org.jboss.weld.bean.ManagedBean.(ManagedBean.java:100)
>   at org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:80)
>   at 
> org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:261)
>   at 
> org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:228)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:78)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:75)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
>   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)
>   ... 1 more
> [WARNING] thread Thread[weld-worker-1,5,weld-workers] was interrupted
> but is still alive after waiting at least 15000msecs
> [WARNING] thread Thread[weld-worker-1,5,weld-workers] will linger
> despite being asked to die via interruption
> [WARNING] thread Thread[weld-worker-2,5,weld-workers] will linger
> despit

[JIRA] (OVIRT-1040) ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25809#comment-25809
 ] 

Yevgeny Zaspitsky commented on OVIRT-1040:
--

BTW, after re-triggering the job the patch passed it [1].

[1] -
http://jenkins.ovirt.org/job/ovirt-engine_4.1_check-patch-fc25-x86_64/298/

On Tue, Jan 17, 2017 at 4:38 PM, Yevgeny Zaspitsky (oVirt JIRA) <



> ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed
> -
>
> Key: OVIRT-1040
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1040
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> The $subject job [1] has failed upon a reason that doesn't seems to be
> related to the patch it checks.
> From the check_patch.sh.log:
> [INFO] --- exec-maven-plugin:1.4.0:java (generate-enums-jaxb) @
> restapi-definition ---
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-log4j12/1.7.7/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> [WARNING]
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapList(AbstractMapBasedMultimap.java:332)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapCollection(AbstractMapBasedMultimap.java:324)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.get(AbstractMapBasedMultimap.java:308)
>   at 
> com.google.common.collect.AbstractListMultimap.get(AbstractListMultimap.java:66)
>   at 
> com.google.common.collect.ArrayListMultimap.get(ArrayListMultimap.java:66)
>   at 
> org.jboss.weld.annotated.enhanced.jlr.EnhancedAnnotatedTypeImpl.getDeclaredEnhancedFields(EnhancedAnnotatedTypeImpl.java:427)
>   at 
> org.jboss.weld.injection.InjectionPointFactory.getFieldInjectionPoints(InjectionPointFactory.java:210)
>   at 
> org.jboss.weld.injection.producer.DefaultInjector.(DefaultInjector.java:56)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.(ResourceInjector.java:58)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:49)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.(BeanInjectionTarget.java:63)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:47)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:128)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:87)
>   at org.jboss.weld.bean.ManagedBean.(ManagedBean.java:100)
>   at org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:80)
>   at 
> org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:261)
>   at 
> org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:228)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:78)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:75)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
>   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)
>   ... 1 more
> [WARNING] thread Thread[weld-worker-1,5,weld-

[JIRA] (OVIRT-1040) ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25808#comment-25808
 ] 

Yevgeny Zaspitsky commented on OVIRT-1040:
--

AFAIK we use maven as the build tool for the ovirt-engine java code.

On Jan 17, 2017 16:23, "eyal edri [Administrator] (oVirt JIRA)" <



> ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed
> -
>
> Key: OVIRT-1040
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1040
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> The $subject job [1] has failed upon a reason that doesn't seems to be
> related to the patch it checks.
> From the check_patch.sh.log:
> [INFO] --- exec-maven-plugin:1.4.0:java (generate-enums-jaxb) @
> restapi-definition ---
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-log4j12/1.7.7/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/root/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
> [WARNING]
> java.lang.reflect.InvocationTargetException
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapList(AbstractMapBasedMultimap.java:332)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.wrapCollection(AbstractMapBasedMultimap.java:324)
>   at 
> com.google.common.collect.AbstractMapBasedMultimap.get(AbstractMapBasedMultimap.java:308)
>   at 
> com.google.common.collect.AbstractListMultimap.get(AbstractListMultimap.java:66)
>   at 
> com.google.common.collect.ArrayListMultimap.get(ArrayListMultimap.java:66)
>   at 
> org.jboss.weld.annotated.enhanced.jlr.EnhancedAnnotatedTypeImpl.getDeclaredEnhancedFields(EnhancedAnnotatedTypeImpl.java:427)
>   at 
> org.jboss.weld.injection.InjectionPointFactory.getFieldInjectionPoints(InjectionPointFactory.java:210)
>   at 
> org.jboss.weld.injection.producer.DefaultInjector.(DefaultInjector.java:56)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.(ResourceInjector.java:58)
>   at 
> org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:49)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.(BeanInjectionTarget.java:63)
>   at 
> org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:47)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:128)
>   at 
> org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:87)
>   at org.jboss.weld.bean.ManagedBean.(ManagedBean.java:100)
>   at org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:80)
>   at 
> org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:261)
>   at 
> org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:228)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:78)
>   at 
> org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:75)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
>   at 
> org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
>   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)
>   ... 1 more
> [WARNING] thread Thread[weld-worker-1,5,weld-workers] was interrupted
> but is still alive after waiting at least 15000msecs
> [WARNING] thread Thread[weld-worker-1,5,weld-workers] will linger
> despite being asked to die via interruption
> [WARNING] thread Thread[weld-worker-2,5,weld-workers] will linger
> despite being asked to die via interruption
> [WARNING] NOTE: 2 thread(s) di

[JIRA] (OVIRT-1040) ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1040:


 Summary: ovirt-engine_4.1_check-patch-fc25-x86_64 build has failed
 Key: OVIRT-1040
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1040
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


The $subject job [1] has failed upon a reason that doesn't seems to be
related to the patch it checks.

>From the check_patch.sh.log:

[INFO] --- exec-maven-plugin:1.4.0:java (generate-enums-jaxb) @
restapi-definition ---
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in
[jar:file:/root/.m2/repository/org/slf4j/slf4j-log4j12/1.7.7/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in
[jar:file:/root/.m2/repository/org/slf4j/slf4j-jdk14/1.5.6/slf4j-jdk14-1.5.6.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
[WARNING]
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:293)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NullPointerException
at 
com.google.common.collect.AbstractMapBasedMultimap.wrapList(AbstractMapBasedMultimap.java:332)
at 
com.google.common.collect.AbstractMapBasedMultimap.wrapCollection(AbstractMapBasedMultimap.java:324)
at 
com.google.common.collect.AbstractMapBasedMultimap.get(AbstractMapBasedMultimap.java:308)
at 
com.google.common.collect.AbstractListMultimap.get(AbstractListMultimap.java:66)
at 
com.google.common.collect.ArrayListMultimap.get(ArrayListMultimap.java:66)
at 
org.jboss.weld.annotated.enhanced.jlr.EnhancedAnnotatedTypeImpl.getDeclaredEnhancedFields(EnhancedAnnotatedTypeImpl.java:427)
at 
org.jboss.weld.injection.InjectionPointFactory.getFieldInjectionPoints(InjectionPointFactory.java:210)
at 
org.jboss.weld.injection.producer.DefaultInjector.(DefaultInjector.java:56)
at 
org.jboss.weld.injection.producer.ResourceInjector.(ResourceInjector.java:58)
at 
org.jboss.weld.injection.producer.ResourceInjector.of(ResourceInjector.java:49)
at 
org.jboss.weld.injection.producer.BeanInjectionTarget.(BeanInjectionTarget.java:63)
at 
org.jboss.weld.injection.producer.BeanInjectionTarget.createDefault(BeanInjectionTarget.java:47)
at 
org.jboss.weld.manager.InjectionTargetFactoryImpl.chooseInjectionTarget(InjectionTargetFactoryImpl.java:128)
at 
org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(InjectionTargetFactoryImpl.java:87)
at org.jboss.weld.bean.ManagedBean.(ManagedBean.java:100)
at org.jboss.weld.bean.ManagedBean.of(ManagedBean.java:80)
at 
org.jboss.weld.bootstrap.AbstractBeanDeployer.createManagedBean(AbstractBeanDeployer.java:261)
at 
org.jboss.weld.bootstrap.BeanDeployer.createClassBean(BeanDeployer.java:228)
at 
org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:78)
at 
org.jboss.weld.bootstrap.ConcurrentBeanDeployer$2.doWork(ConcurrentBeanDeployer.java:75)
at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
at 
org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
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)
... 1 more
[WARNING] thread Thread[weld-worker-1,5,weld-workers] was interrupted
but is still alive after waiting at least 15000msecs
[WARNING] thread Thread[weld-worker-1,5,weld-workers] will linger
despite being asked to die via interruption
[WARNING] thread Thread[weld-worker-2,5,weld-workers] will linger
despite being asked to die via interruption
[WARNING] NOTE: 2 thread(s) did not finish despite being asked to  via
interruption. This is not a problem with exec:java, it is a problem
with the running code. Although not serious, it should be remedied.
[WARNING] Couldn't destroy threadgroup
org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=org.ovirt.api.metamodel.tool.Main,maxpri=10]
java.lang.IllegalThreadStateException
at java.lang.ThreadGroup.destroy(ThreadGroup.java:778)
at java.lang.ThreadGroup.d

[JIRA] (OVIRT-1039) ovirt_master_system-tests_manual job failed

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-1039:


 Summary: ovirt_master_system-tests_manual job failed
 Key: OVIRT-1039
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1039
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


The $subject job [1] has failed.
>From looking into lago.log [2] looks like it uses an invalid url for yum
repo [3]

[1] -
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_master_system-tests_manual/31/
[2] -
http://jenkins.ovirt.org/view/oVirt%20system%20tests/job/ovirt_master_system-tests_manual/31/artifact/exported-artifacts/lago_logs/lago.log
[3] - https://
http://plain.resources.ovirt.org/repos/ovirt/experimental/master/latest.tested/rpm/el7



--
This message was sent by Atlassian JIRA
(v1000.695.1#100025)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-987) Infra issues in Jenkins aren't reported properly on most of Jenkins jobs

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-987:
---

 Summary: Infra issues in Jenkins aren't reported properly on most 
of Jenkins jobs
 Key: OVIRT-987
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-987
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Findbugs jobs reports an infra problem to gerrit properly: "There was an
infra issue, please contact infra@ovirt.org"

It'd be good to have same behavior on the rest of the Jenkins jobs.
Currently there is no differentiation between failure upon an infra issue
and a real patch problem in reporting to gerrit.

Regards,
Yevgeny



--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-982) Fwd: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_created/431

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-982:
---

 Summary: Fwd: 
http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_created/431
 Key: OVIRT-982
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-982
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Looks like a lot of jobs fail on similar problem.

>From the job console log:


git -c core.askpass=true fetch --tags --progress
git://gerrit.ovirt.org/ovirt-engine.git refs/changes/93/67593/22
--prune
ERROR: Error fetching remote repo
'origin'hudson.plugins.git.GitException
:
Failed to fetch from git://gerrit.ovirt.org/ovirt-engine.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-engine.git refs/changes/93/67593/22
--prune" returned status code 128:
stdout:
stderr: fatal: read error: Connection reset by peer

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 vm0040.workers-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.jenki

[JIRA] (OVIRT-961) Fwd: Findbugs failures

[Yevgeny Zaspitsky (oVirt JIRA)]

Yevgeny Zaspitsky created OVIRT-961:
---

 Summary: Fwd: Findbugs failures
 Key: OVIRT-961
 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-961
 Project: oVirt - virtualization made easy
  Issue Type: By-EMAIL
Reporter: Yevgeny Zaspitsky
Assignee: infra


Looks like job [1] fails rather then succeeds. IMHO those failures aren't
related to the patches they try to check.

[1] http://jenkins.ovirt.org/job/ovirt-engine_master_find



--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-961) Fwd: Findbugs failures

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24804#comment-24804
 ] 

Yevgeny Zaspitsky commented on OVIRT-961:
-

Sorry, the right link is
http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created/

On Wed, Dec 14, 2016 at 11:50 AM, Yevgeny Zaspitsky 
wrote:

>
> Looks like job [1] fails rather then succeeds. IMHO those failures aren't
> related to the patches they try to check.
>
> [1] http://jenkins.ovirt.org/job/ovirt-engine_master_find
>
>
>

> Fwd: Findbugs failures
> --
>
> Key: OVIRT-961
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-961
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: Yevgeny Zaspitsky
>Assignee: infra
>
> Looks like job [1] fails rather then succeeds. IMHO those failures aren't
> related to the patches they try to check.
> [1] http://jenkins.ovirt.org/job/ovirt-engine_master_find



--
This message was sent by Atlassian JIRA
(v1000.621.5#100023)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

[JIRA] (OVIRT-514) Re: Cannot access http://www.ovirt.org/

[Yevgeny Zaspitsky (oVirt JIRA)]

[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15310#comment-15310
 ] 

Yevgeny Zaspitsky commented on OVIRT-514:
-

Looks like the site is back.

On Mon, May 2, 2016 at 11:40 AM, Sandro Bonazzola 
wrote:

> Opening a ticket.
>
> On Mon, May 2, 2016 at 9:52 AM, Alona Kaplan  wrote:
>
>> Get the following -
>>
>> Proxy Error
>>
>> The proxy server received an invalid response from an upstream server.
>> The proxy server could not handle the request GET /.
>>
>> Reason: Error reading from remote server
>>
>> Apache/2.2.15 (Red Hat) Server at www.ovirt.org Port 80
>> ___
>> Infra mailing list
>> Infra@ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/infra
>>
>
>
>
> --
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com
>
> ___
> Infra mailing list
> Infra@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
>


> Re: Cannot access http://www.ovirt.org/
> ---
>
> Key: OVIRT-514
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-514
> Project: oVirt - virtualization made easy
>  Issue Type: By-EMAIL
>Reporter: sbonazzo
>Assignee: infra
>
> Opening a ticket.
> On Mon, May 2, 2016 at 9:52 AM, Alona Kaplan  wrote:
> > Get the following -
> >
> > Proxy Error
> >
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request GET /.
> >
> > Reason: Error reading from remote server
> >
> > Apache/2.2.15 (Red Hat) Server at www.ovirt.org Port 80
> > ___
> > Infra mailing list
> > Infra@ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/infra
> >
> -- 
> Sandro Bonazzola
> Better technology. Faster innovation. Powered by community collaboration.
> See how it works at redhat.com



--
This message was sent by Atlassian JIRA
(v1000.5.1#72002)
___
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra