[URGENT][ACTION REQUIRED] ovirt-engine 3.4.3 build fails on CentOS

Sandro Bonazzola sbonazzo at redhat.com
Thu Jul 17 09:33:27 UTC 2014


Il 17/07/2014 10:03, Eyal Edri ha scritto:
> 
> 
> ----- Original Message -----
>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>> To: "infra" <infra at ovirt.org>
>> Sent: Thursday, July 17, 2014 10:54:21 AM
>> Subject: Re: [URGENT][ACTION REQUIRED] ovirt-engine 3.4.3 build fails on CentOS
>>
>> Il 17/07/2014 08:20, Sandro Bonazzola ha scritto:
>>> Hi,
>>> looks like there's an issue while building on CentOS while Fedora builds
>>> completed successfully.
>>>
>>> On a clean CentOS VM I'm running the same build and it passed the failure
>>> point so it seems an infra issue.
>>>
>>> http://jenkins.ovirt.org/job/manual-build-tarball/354/label=centos6-host/console
>>>
>>> Results :
>>>
>>> Tests in error:
>>>   initializationError(org.ovirt.engine.api.restapi.resource.BackendResourceDebugDetailTest):
>>>   Bad <init> method call from inside of a branch
>>> Exception Details:
>>>   Location:
>>>     org/ovirt/engine/api/restapi/resource/AbstractBackendResourceLoggingTest.<init>(Lorg/powermock/core/IndicateReloadClass;)V
>>>     @40: invokespecial
>>>   Reason:
>>>     Error exists in the bytecode
>>>   Bytecode:
>>>     0000000: 2a2b 4e4d 1210 b800 1604 bd00 0d59 032d
>>>     0000010: 5312 a6b8 001b b800 213a 0519 05b2 0025
>>>     0000020: a500 0e2a 01c0 0027 b700 2aa7 000a 2c2d
>>>     0000030: b700 2a01 57b1
>>>   Stackmap Table:
>>>     full_frame(@46,{UninitializedThis,Object[#39],UninitializedThis,Object[#39],Top,Object[#13]},{})
>>>     full_frame(@53,{Object[#2],Object[#39],Object[#2],Object[#39],Top,Object[#13]},{})
>>>
>>>   initializationError(org.ovirt.engine.api.restapi.resource.BackendResourceInfoDetailTest):
>>>   Bad <init> method call from inside of a branch
>>> Exception Details:
>>>   Location:
>>>     org/ovirt/engine/api/restapi/resource/AbstractBackendResourceLoggingTest.<init>(Lorg/powermock/core/IndicateReloadClass;)V
>>>     @40: invokespecial
>>>   Reason:
>>>     Error exists in the bytecode
>>>   Bytecode:
>>>     0000000: 2a2b 4e4d 1210 b800 1604 bd00 0d59 032d
>>>     0000010: 5312 a6b8 001b b800 213a 0519 05b2 0025
>>>     0000020: a500 0e2a 01c0 0027 b700 2aa7 000a 2c2d
>>>     0000030: b700 2a01 57b1
>>>   Stackmap Table:
>>>     full_frame(@46,{UninitializedThis,Object[#39],UninitializedThis,Object[#39],Top,Object[#13]},{})
>>>     full_frame(@53,{Object[#2],Object[#39],Object[#2],Object[#39],Top,Object[#13]},{})
>>>
>>>
>>> Tests run: 1324, Failures: 0, Errors: 2, Skipped: 65
>>>
>>
>> looks like latest update broke javac, with:
>>
>> java-1.7.0-openjdk-1.7.0.55-2.4.7.1.el6_5.x86_64
>> java-1.7.0-openjdk-devel-1.7.0.55-2.4.7.1.el6_5.x86_64
>>
>> works fine, but with latest update it fails.
> 
> should we open a bug on this (on java?)

I think we should, not checked if it's a known issue

> , also - maybe worth enforcing a specific java version via puppet?
> david?
> 
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>> _______________________________________________
>> Infra mailing list
>> Infra at 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



More information about the Infra mailing list