Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

Sorry for the trouble. I put clearly in the commit message: This patch deletes 'frontend/webadmin/modules/userportal-gwtp' and won't pass CI on its own. Patch 3/3 will pass. I think it's reasonable that not every single patch will pass CI. Sometimes patches are so large that they need to be split

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

On 19 July 2017 at 13:49, Oved Ourfali wrote: > If that's the case, we should make sure in the future that patches are > self contained, even if the plan is to push them together. > > That is axiomatically true if you want any useful CI... Maybe some tests should be added to check-patch to ascer

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

If that's the case, we should make sure in the future that patches are self contained, even if the plan is to push them together. On Wed, Jul 19, 2017 at 1:39 PM, Daniel Belenky wrote: > The root cause of those failures is that [1] and [2] can't be built > without [3]. > > [1] https://gerrit.ovi

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

The root cause of those failures is that [1] and [2] can't be built without [3]. [1] https://gerrit.ovirt.org/#/c/78847/5 [2] https://gerrit.ovirt.org/#/c/78848/5 [3] https://gerrit.ovirt.org/#/c/78849/10

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

On Wed, Jul 19, 2017 at 12:45 PM, Oved Ourfali wrote: > I also see that subsequent patches, such as [1] pass those tests: > > > Patch Set 4: Continuous-Integration+1 > Build S

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

I also see that subsequent patches, such as [1] pass those tests: Patch Set 4: Continuous-Integration+1 Build Successful http://jenkins.ovirt.org/job/ovirt-engine_master_check-pa

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

Can we access the environment? On Wed, Jul 19, 2017 at 12:21 PM, Daniel Belenky wrote: > It's also removing /home/jenkins/.m2 > > On Wed, 19 Jul 2017 at 12:16 Tomas Jelinek wrote: > >> On Wed, Jul 19, 2017 at 11:02 AM, Daniel Belenky >> wrote: >> >>> I've added a build step that removes .m2 ca

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

It's also removing /home/jenkins/.m2 On Wed, 19 Jul 2017 at 12:16 Tomas Jelinek wrote: > On Wed, Jul 19, 2017 at 11:02 AM, Daniel Belenky > wrote: > >> I've added a build step that removes .m2 cache and the error still >> appears. >> > > are you sure you have removed the right m2 folder? I see

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

On Wed, Jul 19, 2017 at 11:02 AM, Daniel Belenky wrote: > I've added a build step that removes .m2 cache and the error still appears. > are you sure you have removed the right m2 folder? I see this in the logs: rm -rf /root/.m2/repository/org/ovirt and than building it in /home/jenkins/ ... a

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

I've added a build step that removes .m2 cache and the error still appears. On Wed, Jul 19, 2017 at 11:46 AM, Eyal Edri wrote: > Daniel, > IIRC we have local maven cache on the slaves, please try to clean it first > and re-run. > If its not working, then I suggest engine maintainers will look in

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

Daniel, IIRC we have local maven cache on the slaves, please try to clean it first and re-run. If its not working, then I suggest engine maintainers will look into the command that is run inside 'check-merged.sh' and see if there is a leftover profile in Makefile or maven that still requires userpo

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

I discussed that offline with Eyal. Perhaps some of the data there is cached. He said he is on it. On Wed, Jul 19, 2017 at 11:22 AM, Daniel Belenky wrote: > Hi, I've tried to re-trigger build-artifacts and it failed. > What do you mean by 'brand new environment'? It's the build-artifacts and > c

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

Hi, I've tried to re-trigger build-artifacts and it failed. What do you mean by 'brand new environment'? It's the build-artifacts and check-merged of this patch, not OST. Link: check-merged: http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/5408/ build-artifacts: http://jenki

Re: [ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

Can you re-test? We have pushed a fix this morning. Although not specifically for that. Also, is that a brand new environment? We removed the user portal, so it shouldn't look for the pom file. On Jul 19, 2017 09:46, "Daniel Belenky" wrote: > Hi all, > > This patch has [1] failed building, and e

[ovirt-devel] [ OST Failure Report ] [ Failed Build ] [ oVirt engine master ]

Hi all, This patch has [1] failed building, and every patch that was rebased on top of it failed too because of it. Error snippet: [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.ovirt.engine.ui:webadmin-modules:4.2.0-SNAPSHOT (/home/jenkins/workspace/ovi