Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-03-01 Thread Jacques Le Roux

Hi,

@committers: I don't remember if I already told you so: in case BB fails and it works locally, you can rebuild in BB by login with you complete a.o 
email address (eg: jler...@apache.org) and your ASF password


Jacques

Le 29/02/2024 à 20:09, build...@apache.org a écrit :

Build status: BUILD FAILED: failed './gradlew --no-daemon ...' (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/698
Blamelist: Daniel Watford 
Build Text: failed './gradlew --no-daemon ...' (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] c438302149830cd5f8153dab8e58e623915b21cf


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 0

   generateReadmeFiles: 0

   Copy readme: 0

   generateOfbizDocumentation: 0

   Copy OfbizDocumentation: 0

   generateAllPluginsDocumentation: 0

   Copy AllPluginsDocumentation: 0

   javadoc: 0

   Copy javadoc: 0

   loadAll: 0

   testIntegration: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-06 Thread Jacques Le Roux

Hi Michael,

Don't worry, this is me mucking around with BB. It's OK now.

Jacques

Le 06/02/2024 à 17:13, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/647
Blamelist: Michael Brohl 
Build Text: failed Codenarc copied. (failure)
Status Detected: failed build
Build Source Stamp: [branch trunk] c156ab44141ff166f6620e754ac01df00d5e8a1f


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-05 Thread Jacques Le Roux

Hi Michael,

I forgot this email and only reapply the initial one. I have just completed the 
task. The PR can be closed.

TIA

Jacques

Le 04/02/2024 à 11:54, Michael Brohl a écrit :

See https://issues.apache.org/jira/browse/OFBIZ-12888 and 
https://github.com/apache/ofbiz-framework/pull/687

Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 04.02.24 um 11:43 schrieb Michael Brohl:


Hi,

I'm currently working on a solution for this.

Maybe someone can explain why we use the GroovyScripts source set for the 
codenarc checks in the pre-push hook:

gitHooks {

hooks = ['pre-push': 'checkstyleMain codenarcGroovyScripts']

}

That target seems to be automatically defined through the source set definition 
for groovyScripts.

If I remove that source set and the following task configuration:

tasks.named('compileGroovyScriptsGroovy') {

// We don't want to build groovyScripts as they should be considered as 
standalone elements executed in

// isolation by ofbiz. Building them will result in numerous error due to 
duplicated classes.

enabled = false

}

And change the git hooks to

}

gitHooks {

hooks = ['pre-push': 'checkstyleMain codenarcMain codenarcTest']

}

(which is accoring to the pre-push hook definition in .git/hooks/pre-push)

everything seems to work fine, tests are working and the codenarc Main and Test 
reports are build.

I provide a PR for it.

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 04.02.24 um 08:25 schrieb Jacques Le Roux:

Hi Michael,

OK thanks, I'll have a look when I'll get a chance.

It's also weird that it works locally on both Ubuntu 20.04 and Win7 and that BB 
fails. Anyway, so far BB is our guardian.

Jacques

Le 03/02/2024 à 23:36, Michael Brohl a écrit :

Hi Jacques,

the commit fixes an issue with the classpath generation of the "eclipse" gradle task 
which produces double entries for the "src/main/groovy" path.

The initial issue is caused by the "src/main/groovy" path set twice in build gradle, for the "main" and for the "groovyScripts" source sets. The 
second source set entry was removed and the build works as expected.


Instead of reverting the commit, the buildbot process should be checked and repaired. I guess that there is a configuration somewhere which 
relies on the path being present at a stage where it is not after the change. It looks like it has something to do with the codenarc tasks.


I am not familiar enough with the codenarc task to help with that, any help 
from others to have both issues fixed is appreciated.

Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:



Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24

Please refer to INFRA-25456 for more information. I still don't understand why 
it works locally though, any idea?

Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 for that

Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 

Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 625b80dbc626db35dddbaa62057e34b20ae7c38c


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-04 Thread Michael Brohl
See https://issues.apache.org/jira/browse/OFBIZ-12888 and 
https://github.com/apache/ofbiz-framework/pull/687


Regards,

Michael Brohl

ecomify GmbH - www.ecomify.de


Am 04.02.24 um 11:43 schrieb Michael Brohl:


Hi,

I'm currently working on a solution for this.

Maybe someone can explain why we use the GroovyScripts source set for 
the codenarc checks in the pre-push hook:


gitHooks {

hooks = ['pre-push': 'checkstyleMain codenarcGroovyScripts']

}

That target seems to be automatically defined through the source set 
definition for groovyScripts.


If I remove that source set and the following task configuration:

tasks.named('compileGroovyScriptsGroovy') {

// We don't want to build groovyScripts as they should be considered 
as standalone elements executed in


// isolation by ofbiz. Building them will result in numerous error due 
to duplicated classes.


enabled = false

}

And change the git hooks to

}

gitHooks {

hooks = ['pre-push': 'checkstyleMain codenarcMain codenarcTest']

}

(which is accoring to the pre-push hook definition in 
.git/hooks/pre-push)


everything seems to work fine, tests are working and the codenarc Main 
and Test reports are build.


I provide a PR for it.

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 04.02.24 um 08:25 schrieb Jacques Le Roux:

Hi Michael,

OK thanks, I'll have a look when I'll get a chance.

It's also weird that it works locally on both Ubuntu 20.04 and Win7 
and that BB fails. Anyway, so far BB is our guardian.


Jacques

Le 03/02/2024 à 23:36, Michael Brohl a écrit :

Hi Jacques,

the commit fixes an issue with the classpath generation of the 
"eclipse" gradle task which produces double entries for the 
"src/main/groovy" path.


The initial issue is caused by the "src/main/groovy" path set twice 
in build gradle, for the "main" and for the "groovyScripts" source 
sets. The second source set entry was removed and the build works as 
expected.


Instead of reverting the commit, the buildbot process should be 
checked and repaired. I guess that there is a configuration 
somewhere which relies on the path being present at a stage where it 
is not after the change. It looks like it has something to do with 
the codenarc tasks.


I am not familiar enough with the codenarc task to help with that, 
any help from others to have both issues fixed is appreciated.


Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:



Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24 



Please refer to INFRA-25456 for more information. I still don't 
understand why it works locally though, any idea?


Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 
for that


Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 


Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 
625b80dbc626db35dddbaa62057e34b20ae7c38c



Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-04 Thread Michael Brohl

Hi,

I'm currently working on a solution for this.

Maybe someone can explain why we use the GroovyScripts source set for 
the codenarc checks in the pre-push hook:


gitHooks {

hooks = ['pre-push': 'checkstyleMain codenarcGroovyScripts']

}

That target seems to be automatically defined through the source set 
definition for groovyScripts.


If I remove that source set and the following task configuration:

tasks.named('compileGroovyScriptsGroovy') {

// We don't want to build groovyScripts as they should be considered as 
standalone elements executed in


// isolation by ofbiz. Building them will result in numerous error due 
to duplicated classes.


enabled = false

}

And change the git hooks to

}

gitHooks {

hooks = ['pre-push': 'checkstyleMain codenarcMain codenarcTest']

}

(which is accoring to the pre-push hook definition in .git/hooks/pre-push)

everything seems to work fine, tests are working and the codenarc Main 
and Test reports are build.


I provide a PR for it.

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 04.02.24 um 08:25 schrieb Jacques Le Roux:

Hi Michael,

OK thanks, I'll have a look when I'll get a chance.

It's also weird that it works locally on both Ubuntu 20.04 and Win7 
and that BB fails. Anyway, so far BB is our guardian.


Jacques

Le 03/02/2024 à 23:36, Michael Brohl a écrit :

Hi Jacques,

the commit fixes an issue with the classpath generation of the 
"eclipse" gradle task which produces double entries for the 
"src/main/groovy" path.


The initial issue is caused by the "src/main/groovy" path set twice 
in build gradle, for the "main" and for the "groovyScripts" source 
sets. The second source set entry was removed and the build works as 
expected.


Instead of reverting the commit, the buildbot process should be 
checked and repaired. I guess that there is a configuration somewhere 
which relies on the path being present at a stage where it is not 
after the change. It looks like it has something to do with the 
codenarc tasks.


I am not familiar enough with the codenarc task to help with that, 
any help from others to have both issues fixed is appreciated.


Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:



Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24 



Please refer to INFRA-25456 for more information. I still don't 
understand why it works locally though, any idea?


Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 
for that


Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 


Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 
625b80dbc626db35dddbaa62057e34b20ae7c38c



Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-04 Thread Jacques Le Roux

Cool, thanks!

Le 04/02/2024 à 11:26, Michael Brohl a écrit :

Hi Jacques,

I'm currently working on a solution.

Michael


Am 04.02.24 um 08:25 schrieb Jacques Le Roux:

Hi Michael,

OK thanks, I'll have a look when I'll get a chance.

It's also weird that it works locally on both Ubuntu 20.04 and Win7 and that BB 
fails. Anyway, so far BB is our guardian.

Jacques

Le 03/02/2024 à 23:36, Michael Brohl a écrit :

Hi Jacques,

the commit fixes an issue with the classpath generation of the "eclipse" gradle task 
which produces double entries for the "src/main/groovy" path.

The initial issue is caused by the "src/main/groovy" path set twice in build gradle, for the "main" and for the "groovyScripts" source sets. The 
second source set entry was removed and the build works as expected.


Instead of reverting the commit, the buildbot process should be checked and repaired. I guess that there is a configuration somewhere which relies 
on the path being present at a stage where it is not after the change. It looks like it has something to do with the codenarc tasks.


I am not familiar enough with the codenarc task to help with that, any help 
from others to have both issues fixed is appreciated.

Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:



Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24

Please refer to INFRA-25456 for more information. I still don't understand why 
it works locally though, any idea?

Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 for that

Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 

Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 625b80dbc626db35dddbaa62057e34b20ae7c38c


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-04 Thread Michael Brohl

Hi Jacques,

I'm currently working on a solution.

Michael


Am 04.02.24 um 08:25 schrieb Jacques Le Roux:

Hi Michael,

OK thanks, I'll have a look when I'll get a chance.

It's also weird that it works locally on both Ubuntu 20.04 and Win7 
and that BB fails. Anyway, so far BB is our guardian.


Jacques

Le 03/02/2024 à 23:36, Michael Brohl a écrit :

Hi Jacques,

the commit fixes an issue with the classpath generation of the 
"eclipse" gradle task which produces double entries for the 
"src/main/groovy" path.


The initial issue is caused by the "src/main/groovy" path set twice 
in build gradle, for the "main" and for the "groovyScripts" source 
sets. The second source set entry was removed and the build works as 
expected.


Instead of reverting the commit, the buildbot process should be 
checked and repaired. I guess that there is a configuration somewhere 
which relies on the path being present at a stage where it is not 
after the change. It looks like it has something to do with the 
codenarc tasks.


I am not familiar enough with the codenarc task to help with that, 
any help from others to have both issues fixed is appreciated.


Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:



Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24 



Please refer to INFRA-25456 for more information. I still don't 
understand why it works locally though, any idea?


Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 
for that


Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 


Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 
625b80dbc626db35dddbaa62057e34b20ae7c38c



Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-03 Thread Jacques Le Roux

Hi Michael,

OK thanks, I'll have a look when I'll get a chance.

It's also weird that it works locally on both Ubuntu 20.04 and Win7 and that BB 
fails. Anyway, so far BB is our guardian.

Jacques

Le 03/02/2024 à 23:36, Michael Brohl a écrit :

Hi Jacques,

the commit fixes an issue with the classpath generation of the "eclipse" gradle task 
which produces double entries for the "src/main/groovy" path.

The initial issue is caused by the "src/main/groovy" path set twice in build gradle, for the "main" and for the "groovyScripts" source sets. The 
second source set entry was removed and the build works as expected.


Instead of reverting the commit, the buildbot process should be checked and repaired. I guess that there is a configuration somewhere which relies 
on the path being present at a stage where it is not after the change. It looks like it has something to do with the codenarc tasks.


I am not familiar enough with the codenarc task to help with that, any help 
from others to have both issues fixed is appreciated.

Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:



Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24

Please refer to INFRA-25456 for more information. I still don't understand why 
it works locally though, any idea?

Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 for that

Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 

Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 625b80dbc626db35dddbaa62057e34b20ae7c38c


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-03 Thread Michael Brohl

Hi Jacques,

the commit fixes an issue with the classpath generation of the "eclipse" 
gradle task which produces double entries for the "src/main/groovy" path.


The initial issue is caused by the "src/main/groovy" path set twice in 
build gradle, for the "main" and for the "groovyScripts" source sets. 
The second source set entry was removed and the build works as expected.


Instead of reverting the commit, the buildbot process should be checked 
and repaired. I guess that there is a configuration somewhere which 
relies on the path being present at a stage where it is not after the 
change. It looks like it has something to do with the codenarc tasks.


I am not familiar enough with the codenarc task to help with that, any 
help from others to have both issues fixed is appreciated.


Thanks and regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 03.02.24 um 11:01 schrieb Jacques Le Roux:

Hi Michael,

Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24 



Please refer to INFRA-25456 for more information. I still don't 
understand why it works locally though, any idea?


Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 for 
that


Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 


Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 
625b80dbc626db35dddbaa62057e34b20ae7c38c



Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-03 Thread Jacques Le Roux

Hi Michael,

Sorry, to allow BB to build, I had to revert this commit:
https://github.com/apache/ofbiz-framework/commit/a2f3ec88309f8440fe65b227ff3fc2df279dde24

Please refer to INFRA-25456 for more information. I still don't understand why 
it works locally though, any idea?

Jacques

Le 02/02/2024 à 17:57, Jacques Le Roux a écrit :

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 for that

Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 

Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 625b80dbc626db35dddbaa62057e34b20ae7c38c


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2024-02-02 Thread Jacques Le Roux

Hi,

I have created https://issues.apache.org/jira/browse/INFRA-25456 for that

Jacques

Le 02/02/2024 à 14:14, build...@apache.org a écrit :

Build status: BUILD FAILED: failed Codenarc copied. (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/635
Blamelist: Michael Brohl , Michael Brohl 

Build Text: failed Codenarc copied. (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 625b80dbc626db35dddbaa62057e34b20ae7c38c


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   Copy codenarc to destination directory structure: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-12-31 Thread Jacques Le Roux

I have created https://issues.apache.org/jira/browse/INFRA-25327 for that

Jacques

Le 31/12/2023 à 10:21, build...@apache.org a écrit :

Build status: BUILD FAILED: failed 'bash -c ...' (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/614
Blamelist: Jacques Le Roux 
Build Text: failed 'bash -c ...' (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] fd52ae3fe0bcc5edebff6f3fba939475f83c4a41


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 2

   clean things: 0


-- ASF Buildbot



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-21 Thread Jacques Le Roux

Hi Daniel,

But the most problem is that we have no (easy?) mean to know if a RAT build has 
succeeded or not:
https://issues.apache.org/jira/browse/RAT-256

Le 21/04/2023 à 11:57, Daniel Watford a écrit :

Hi Jacques,

We'll need some text in the README adjacent to the badge image to explain
which build each badge relates to.


On Thu, 20 Apr 2023 at 19:32, Jacques Le Roux 
wrote:


Le 19/04/2023 à 11:24, Jacques Le Roux a écrit :

Good idea about the badge. I'll have a look.

Hi Daniel,

It's OK for trunk build but how to cleanly differentiate ?

https://ci2.apache.org/badges/ofbizTrunkFramework.svg
from
https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg

https://ci2.apache.org/badges/ gives nothing :/

Jacques




Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-21 Thread Daniel Watford
Hi Jacques,

We'll need some text in the README adjacent to the badge image to explain
which build each badge relates to.


On Thu, 20 Apr 2023 at 19:32, Jacques Le Roux 
wrote:

> Le 19/04/2023 à 11:24, Jacques Le Roux a écrit :
> > Good idea about the badge. I'll have a look.
>
> Hi Daniel,
>
> It's OK for trunk build but how to cleanly differentiate ?
>
> https://ci2.apache.org/badges/ofbizTrunkFramework.svg
> from
> https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg
>
> https://ci2.apache.org/badges/ gives nothing :/
>
> Jacques
>
>

-- 
Daniel Watford


Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-21 Thread Jacques Le Roux

Done with https://issues.apache.org/jira/browse/OFBIZ-12810

Le 20/04/2023 à 20:32, Jacques Le Roux a écrit :

Le 19/04/2023 à 11:24, Jacques Le Roux a écrit :

Good idea about the badge. I'll have a look.


Hi Daniel,

It's OK for trunk build but how to cleanly differentiate ?

https://ci2.apache.org/badges/ofbizTrunkFramework.svg
from
https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg

https://ci2.apache.org/badges/ gives nothing :/

Jacques



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-20 Thread Jacques Le Roux

Le 19/04/2023 à 11:24, Jacques Le Roux a écrit :

Good idea about the badge. I'll have a look.


Hi Daniel,

It's OK for trunk build but how to cleanly differentiate ?

https://ci2.apache.org/badges/ofbizTrunkFramework.svg
from
https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg

https://ci2.apache.org/badges/ gives nothing :/

Jacques



Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-19 Thread Jacques Le Roux

Hi Daniel,

For now I have committed a change in BB config in order to generate a file at 
https://nightlies.apache.org/ofbiz/trunk/groovyScripts.html
It should appear with the next trunk commit.

I agree that should be enough. It's similar to what I did for checkstyle.
And indeed fixing new Codenarc issues is all what is needed for the status to 
change to success.
As long as we react sufficiently quick, as you did thanks, it's OK.

About your side note: The BB config is already complicated enough for me and OK 
as is. But anyone can have a look :)

Actually as you can see below, you are in the list of those who should receive 
an email from BB when a status change ie the blamelist:

   Blamelist: Aditya Sharma, Benjamin Jugl<

   benjamin.j...@ecomify.de>, Daniel Watford, Jacques Le
   Roux, Michael Brohl,
   Nicolas Malin, Pierre Smits<
   pierre.sm...@gmail.com>, Pierre Smits,
   cshan-ecomify<117295991+cshan-ecom...@users.noreply.github.com>

At least I receive these emails when status change.
From the top of my head I don't remember how this blamelist is set.
I guess people subscribe somewhere. I don't remember where.

Good idea about the badge. I'll have a look.

Thanks

Jacques

Le 19/04/2023 à 08:12, Daniel Watford a écrit :

Hi Jacques,

I haven't found a way to selectively inhibit the failure state of a gradle
task.

However, I'm not sure we should take that approach otherwise we may find
ourselves in a situation where issues related to checkstyle and codenarc
are not addressed.

[ Side note: In this particular case, the codenarc failure was caused by
changes in ofbiz-plugins which are not built as part of the checking of a
pull request. Codenarc issues will not be found in ofbiz-plugins until a
new commit is pushed to ofbiz-framework trunk. Perhaps this is something we
could think about. ]

I have to confess to not checking Build Bot regularly. Instead I rely on
the GitHub Actions builds since they are more visible to me. I imagine
others are also failing to notice the status of the Build Bot builds and
this is why these build failures are not getting addressed.

To improve BuildBot visibility we could update the build status badges
included in Readme.adoc.

We currently include the badge for the framework build as:

image:https://ci2.apache.org/badges/ofbizTrunkFramework.svg[link=
https://ci2.apache.org/badges/ofbizTrunkFramework.svg]

This should be change to link to BuildBot:

image:https://ci2.apache.org/badges/ofbizTrunkFramework.svg[link=
https://ci2.apache.org/#/builders/49]

We could then add badges for the frameworkPlugins and RAT builds.
Presumably the README.adoc would look something like:

image:https://ci2.apache.org/badges/ofbizTrunkFrameworkPlugins.svg[link=
https://ci2.apache.org/#/builders/46]
image:https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg[link=
https://ci2.apache.org/#/builders/51]


Perhaps there is a way to send an email notification to those who have
pushed commits since the last successful build in the event of a new
BuildBot build failure?

Thanks,

Dan.


On Tue, 18 Apr 2023 at 13:29, Jacques Le Roux
wrote:


Hi Team,

Now that we have Codenarc used, we need to generate a report on our site
with BuildBot like we have:
https://nightlies.apache.org/ofbiz/trunk/checkstyle.html  (also available
for next and stable).
This report allows everyone to see what the checkstyle problems are and to
fix them.

In theory (much code violations) having a similar Codenarc report on site
would help us to fix the issue that we currently have at
https://ci2.apache.org/#/builders/46  reported below

I launched the codenarcGroovyScripts Gradle task locally and got this
information at top of the report:

Package Total Files Files with Violations   Priority 1
Priority 2  Priority 3
All Packages547 134 -   448 4396
  62  46  -   269 2416

Fortunately the BB issue does not prevent the rest of the BB script to
complete (the BB "check" step is marked as "haltOnFailure=False")
So it's not a blocker and does not hide other possible issue happening
"below" but it sticks the build status to BUILD FAILED.
So if another issue happens "below"we will not be alerted (no status
change ever).

Here is the part that fails on BB (note: as you can see Cobertura is not a
problem):

  > Task :checkstyleTest
The Cobertura XML file [null] is not accessible; skipping this rule
  > Task :checkstyleMain
  > Task :codenarcGroovyScripts
CodeNarc completed: (p1=0; p2=448; p3=4409) 66597ms

  > Task :codenarcGroovyScripts FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':codenarcGroovyScripts'.
  > CodeNarc rule violations were found. See the report at:

file:///home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/build/reports/codenarc/groovyScripts.html

I'll create a Jira in order to generate a groovyScripts.html with BB
accessible on site.
But I'd like to know if it's possible to bypass the failed status.

Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-18 Thread Daniel Watford
Hi Jacques,

I haven't found a way to selectively inhibit the failure state of a gradle
task.

However, I'm not sure we should take that approach otherwise we may find
ourselves in a situation where issues related to checkstyle and codenarc
are not addressed.

[ Side note: In this particular case, the codenarc failure was caused by
changes in ofbiz-plugins which are not built as part of the checking of a
pull request. Codenarc issues will not be found in ofbiz-plugins until a
new commit is pushed to ofbiz-framework trunk. Perhaps this is something we
could think about. ]

I have to confess to not checking Build Bot regularly. Instead I rely on
the GitHub Actions builds since they are more visible to me. I imagine
others are also failing to notice the status of the Build Bot builds and
this is why these build failures are not getting addressed.

To improve BuildBot visibility we could update the build status badges
included in Readme.adoc.

We currently include the badge for the framework build as:

image:https://ci2.apache.org/badges/ofbizTrunkFramework.svg[link=
https://ci2.apache.org/badges/ofbizTrunkFramework.svg]

This should be change to link to BuildBot:

image:https://ci2.apache.org/badges/ofbizTrunkFramework.svg[link=
https://ci2.apache.org/#/builders/49]

We could then add badges for the frameworkPlugins and RAT builds.
Presumably the README.adoc would look something like:

image:https://ci2.apache.org/badges/ofbizTrunkFrameworkPlugins.svg[link=
https://ci2.apache.org/#/builders/46]
image:https://ci2.apache.org/badges/ofbizTrunkFrameworkRat.svg[link=
https://ci2.apache.org/#/builders/51]


Perhaps there is a way to send an email notification to those who have
pushed commits since the last successful build in the event of a new
BuildBot build failure?

Thanks,

Dan.


On Tue, 18 Apr 2023 at 13:29, Jacques Le Roux 
wrote:

> Hi Team,
>
> Now that we have Codenarc used, we need to generate a report on our site
> with BuildBot like we have:
> https://nightlies.apache.org/ofbiz/trunk/checkstyle.html (also available
> for next and stable).
> This report allows everyone to see what the checkstyle problems are and to
> fix them.
>
> In theory (much code violations) having a similar Codenarc report on site
> would help us to fix the issue that we currently have at
> https://ci2.apache.org/#/builders/46 reported below
>
> I launched the codenarcGroovyScripts Gradle task locally and got this
> information at top of the report:
>
> Package Total Files Files with Violations   Priority 1
> Priority 2  Priority 3
> All Packages547 134 -   448 4396
>   62  46  -   269 2416
>
> Fortunately the BB issue does not prevent the rest of the BB script to
> complete (the BB "check" step is marked as "haltOnFailure=False")
> So it's not a blocker and does not hide other possible issue happening
> "below" but it sticks the build status to BUILD FAILED.
> So if another issue happens "below"we will not be alerted (no status
> change ever).
>
> Here is the part that fails on BB (note: as you can see Cobertura is not a
> problem):
>
>  > Task :checkstyleTest
> The Cobertura XML file [null] is not accessible; skipping this rule
>  > Task :checkstyleMain
>  > Task :codenarcGroovyScripts
> CodeNarc completed: (p1=0; p2=448; p3=4409) 66597ms
>
>  > Task :codenarcGroovyScripts FAILED
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':codenarcGroovyScripts'.
>  > CodeNarc rule violations were found. See the report at:
>
> file:///home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/build/reports/codenarc/groovyScripts.html
>
> I'll create a Jira in order to generate a groovyScripts.html with BB
> accessible on site.
> But I'd like to know if it's possible to bypass the failed status. Either
> by unlocking the rules or another mean?
>
> TIA
>
> Jacques
>
> Le 17/04/2023 à 11:26, build...@apache.org a écrit :
> > Build status: BUILD FAILED: failed './gradlew --no-daemon ...' (failure)
> './gradlew --no-daemon ...' (failure)
> > Worker used: bb_worker4_ubuntu
> > URL:https://ci2.apache.org/#builders/46/builds/507
> > Blamelist: Aditya Sharma, Benjamin Jugl<
> benjamin.j...@ecomify.de>, Daniel Watford, Jacques Le
> Roux, Michael Brohl,
> Nicolas Malin, Pierre Smits<
> pierre.sm...@gmail.com>, Pierre Smits,
> cshan-ecomify<117295991+cshan-ecom...@users.noreply.github.com>
> > Build Text: failed './gradlew --no-daemon ...' (failure) './gradlew
> --no-daemon ...' (failure)
> > Status Detected: new failure
> > Build Source Stamp: [branch trunk]
> 145da8136056a76d4e5c8bb9e40ebe8a93de01fb
> >
> >
> > Steps:
> >
> >worker_preparation: 0
> >
> >git: 0
> >
> >pullAllPluginsSource: 0
> >
> >build: 0
> >
> >check: 2
> >
> >Copy checkstyle to destination directory structure: 0
> >
> >generateReadmeFiles: 0
> >
> >Copy readme: 0
> >
> >generateOfbizDocumentation: 0
> >
> >Copy OfbizDocumentation: 0
> >
> >gene

Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-04-18 Thread Jacques Le Roux

Hi Team,

Now that we have Codenarc used, we need to generate a report on our site with 
BuildBot like we have:
https://nightlies.apache.org/ofbiz/trunk/checkstyle.html (also available for 
next and stable).
This report allows everyone to see what the checkstyle problems are and to fix 
them.

In theory (much code violations) having a similar Codenarc report on site would help us to fix the issue that we currently have at 
https://ci2.apache.org/#/builders/46 reported below


I launched the codenarcGroovyScripts Gradle task locally and got this 
information at top of the report:

Package Total Files Files with Violations   Priority 1  
Priority 2  Priority 3
All Packages547 134 -   448 4396
62  46  -   269 2416

Fortunately the BB issue does not prevent the rest of the BB script to complete (the BB 
"check" step is marked as "haltOnFailure=False")
So it's not a blocker and does not hide other possible issue happening "below" 
but it sticks the build status to BUILD FAILED.
So if another issue happens "below"we will not be alerted (no status change 
ever).

Here is the part that fails on BB (note: as you can see Cobertura is not a 
problem):

> Task :checkstyleTest
The Cobertura XML file [null] is not accessible; skipping this rule
> Task :checkstyleMain
> Task :codenarcGroovyScripts
CodeNarc completed: (p1=0; p2=448; p3=4409) 66597ms

> Task :codenarcGroovyScripts FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':codenarcGroovyScripts'.
> CodeNarc rule violations were found. See the report at: 
file:///home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/build/reports/codenarc/groovyScripts.html


I'll create a Jira in order to generate a groovyScripts.html with BB accessible 
on site.
But I'd like to know if it's possible to bypass the failed status. Either by 
unlocking the rules or another mean?

TIA

Jacques

Le 17/04/2023 à 11:26, build...@apache.org a écrit :

Build status: BUILD FAILED: failed './gradlew --no-daemon ...' (failure) 
'./gradlew --no-daemon ...' (failure)
Worker used: bb_worker4_ubuntu
URL:https://ci2.apache.org/#builders/46/builds/507
Blamelist: Aditya Sharma, Benjamin Jugl, Daniel 
Watford, Jacques Le Roux, Michael Brohl, 
Nicolas Malin, Pierre Smits, Pierre 
Smits, cshan-ecomify<117295991+cshan-ecom...@users.noreply.github.com>
Build Text: failed './gradlew --no-daemon ...' (failure) './gradlew --no-daemon 
...' (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 145da8136056a76d4e5c8bb9e40ebe8a93de01fb


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 2

   Copy checkstyle to destination directory structure: 0

   generateReadmeFiles: 0

   Copy readme: 0

   generateOfbizDocumentation: 0

   Copy OfbizDocumentation: 0

   generateAllPluginsDocumentation: 0

   Copy AllPluginsDocumentation: 0

   javadoc: 0

   Copy javadoc: 0

   loadAll: 0

   testIntegration: 2

   clean things: 0


-- ASF Buildbot


Re: Buildbot failure in on ofbizTrunkFrameworkPlugins

2023-03-10 Thread Jacques Le Roux

False report, works locally (Windows)

Le 10/03/2023 à 09:35, build...@apache.org a écrit :

Build status: BUILD FAILED: failed './gradlew --no-daemon ...' (failure)
Worker used: bb_worker4_ubuntu
URL: https://ci2.apache.org/#builders/46/builds/476
Blamelist: cshan-ecomify <117295991+cshan-ecom...@users.noreply.github.com>
Build Text: failed './gradlew --no-daemon ...' (failure)
Status Detected: new failure
Build Source Stamp: [branch trunk] 08368d624ed2bcf2f5ca09e522dbd393681d6f20


Steps:

   worker_preparation: 0

   git: 0

   pullAllPluginsSource: 0

   build: 0

   check: 0

   Copy checkstyle to destination directory structure: 0

   generateReadmeFiles: 0

   Copy readme: 0

   generateOfbizDocumentation: 0

   Copy OfbizDocumentation: 0

   generateAllPluginsDocumentation: 0

   Copy AllPluginsDocumentation: 0

   javadoc: 0

   Copy javadoc: 0

   loadAll: 0

   testIntegration: 2

   clean things: 0


-- ASF Buildbot



Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-08-10 Thread Nicolas Malin
I will look on it

Nicolas

On 10/08/2021 17:48, build...@apache.org wrote:
> The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
> while building ofbiz-framework. Full details are available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2185
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf947_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch trunk] 25c75e2839d2ad020951edaeae17371a48348906
> Blamelist: Eugen Stan 
>
> BUILD FAILED: failed check
>
> Sincerely,
>  -The Buildbot
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-07-07 Thread Nicolas Malin
Thanks Jacques for your look !

On 03/07/2021 19:35, Jacques Le Roux wrote:
> Oops, actually forgot to pull before testing :/
>
> Fixed now
>
> Le 03/07/2021 à 11:40, Jacques Le Roux a écrit :
>> Hi Nicolas,
>>
>> Nevermind, I can't reproduce locally either and the error message
>> "Each variable declaration must be in its own statement" concerns
>>
>> https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html#f-/home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroCommonRenderer.java
>>
>>
>> That does not make sense when you look at line 64.
>>
>> We will see if Checkstyle repeats that later ;)
>>
>> Thanks
>>
>> Jacques
>>
>> Le 02/07/2021 à 21:12, Nicolas Malin a écrit :
>>> Non mais sérieux ! Why my local the check is good and not on build bot,
>>> -_-' I know, it hate me ^^
>>>
>>> Nicolas
>>>
>>> On 02/07/2021 19:04, build...@apache.org wrote:
 The Buildbot has detected a new failure on builder
 ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
 details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2135

 Buildbot URL: https://ci.apache.org/

 Buildslave for this Build: asf945_ubuntu

 Build Reason: downstream
 Build Source Stamp: [branch trunk]
 7120cf7d5f264830385105dea233c7f56998242e
 Blamelist: Nicolas Malin 

 BUILD FAILED: failed check

 Sincerely,
   -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-07-03 Thread Jacques Le Roux

Oops, actually forgot to pull before testing :/

Fixed now

Le 03/07/2021 à 11:40, Jacques Le Roux a écrit :

Hi Nicolas,

Nevermind, I can't reproduce locally either and the error message "Each variable 
declaration must be in its own statement" concerns

https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html#f-/home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroCommonRenderer.java 



That does not make sense when you look at line 64.

We will see if Checkstyle repeats that later ;)

Thanks

Jacques

Le 02/07/2021 à 21:12, Nicolas Malin a écrit :

Non mais sérieux ! Why my local the check is good and not on build bot,
-_-' I know, it hate me ^^

Nicolas

On 02/07/2021 19:04, build...@apache.org wrote:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2135

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 7120cf7d5f264830385105dea233c7f56998242e
Blamelist: Nicolas Malin 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-07-03 Thread Jacques Le Roux

Hi Nicolas,

Nevermind, I can't reproduce locally either and the error message "Each variable 
declaration must be in its own statement" concerns

https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html#f-/home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/framework/widget/src/main/java/org/apache/ofbiz/widget/renderer/macro/MacroCommonRenderer.java

That does not make sense when you look at line 64.

We will see if Checkstyle repeats that later ;)

Thanks

Jacques

Le 02/07/2021 à 21:12, Nicolas Malin a écrit :

Non mais sérieux ! Why my local the check is good and not on build bot,
-_-' I know, it hate me ^^

Nicolas

On 02/07/2021 19:04, build...@apache.org wrote:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2135

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 7120cf7d5f264830385105dea233c7f56998242e
Blamelist: Nicolas Malin 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-07-02 Thread Nicolas Malin
Non mais sérieux ! Why my local the check is good and not on build bot,
-_-' I know, it hate me ^^

Nicolas

On 02/07/2021 19:04, build...@apache.org wrote:
> The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
> while building ofbiz-framework. Full details are available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2135
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf945_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch trunk] 7120cf7d5f264830385105dea233c7f56998242e
> Blamelist: Nicolas Malin 
>
> BUILD FAILED: failed check
>
> Sincerely,
>  -The Buildbot
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-05-25 Thread Nicolas Malin
:) thanks for the look

Nicolas


On 25/05/2021 12:42, Jacques Le Roux wrote:
> Actually I'm working on
> https://github.com/checkstyle/checkstyle/issues/10012
>
> I did not pull. It's now fixed.
>
> Le 25/05/2021 à 11:33, Jacques Le Roux a écrit :
>> Hi Nicolas,
>>
>> Same here, checking that...
>>
>> Jacques
>>
>> Le 25/05/2021 à 09:56, Nicolas Malin a écrit :
>>> Hi Jacques,
>>>
>>> It's strange, I haven't this issue on my local
>>>
>>> Nicolas
>>>
>>> On 22/05/2021 16:53, Jacques Le Roux wrote:
 Hi Nicolas,

 There is a checkstyle issue in this commit. It's not a big deal in
 itself but it might hide some other issues coming from now

 TIA to fix it :)

 Jacques

 Le 21/05/2021 à 19:37, build...@apache.org a écrit :
> The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
> details are available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2100
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf947_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch trunk]
> b663660486074196385bdf08034547839dc1e11c
> Blamelist: Nicolas Malin 
>
> BUILD FAILED: failed check
>
> Sincerely,
>    -The Buildbot
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-05-25 Thread Jacques Le Roux

Actually I'm working on https://github.com/checkstyle/checkstyle/issues/10012

I did not pull. It's now fixed.

Le 25/05/2021 à 11:33, Jacques Le Roux a écrit :

Hi Nicolas,

Same here, checking that...

Jacques

Le 25/05/2021 à 09:56, Nicolas Malin a écrit :

Hi Jacques,

It's strange, I haven't this issue on my local

Nicolas

On 22/05/2021 16:53, Jacques Le Roux wrote:

Hi Nicolas,

There is a checkstyle issue in this commit. It's not a big deal in
itself but it might hide some other issues coming from now

TIA to fix it :)

Jacques

Le 21/05/2021 à 19:37, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
details are available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2100

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk]
b663660486074196385bdf08034547839dc1e11c
Blamelist: Nicolas Malin 

BUILD FAILED: failed check

Sincerely,
   -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-05-25 Thread Jacques Le Roux

Hi Nicolas,

Same here, checking that...

Jacques

Le 25/05/2021 à 09:56, Nicolas Malin a écrit :

Hi Jacques,

It's strange, I haven't this issue on my local

Nicolas

On 22/05/2021 16:53, Jacques Le Roux wrote:

Hi Nicolas,

There is a checkstyle issue in this commit. It's not a big deal in
itself but it might hide some other issues coming from now

TIA to fix it :)

Jacques

Le 21/05/2021 à 19:37, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
details are available at:
 
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2100


Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk]
b663660486074196385bdf08034547839dc1e11c
Blamelist: Nicolas Malin 

BUILD FAILED: failed check

Sincerely,
   -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-05-25 Thread Nicolas Malin
Hi Jacques,

It's strange, I haven't this issue on my local

Nicolas

On 22/05/2021 16:53, Jacques Le Roux wrote:
> Hi Nicolas,
>
> There is a checkstyle issue in this commit. It's not a big deal in
> itself but it might hide some other issues coming from now
>
> TIA to fix it :)
>
> Jacques
>
> Le 21/05/2021 à 19:37, build...@apache.org a écrit :
>> The Buildbot has detected a new failure on builder
>> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
>> details are available at:
>> 
>> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2100
>>
>> Buildbot URL: https://ci.apache.org/
>>
>> Buildslave for this Build: asf947_ubuntu
>>
>> Build Reason: downstream
>> Build Source Stamp: [branch trunk]
>> b663660486074196385bdf08034547839dc1e11c
>> Blamelist: Nicolas Malin 
>>
>> BUILD FAILED: failed check
>>
>> Sincerely,
>>   -The Buildbot
>>
>>
>>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-05-22 Thread Jacques Le Roux

Hi Nicolas,

There is a checkstyle issue in this commit. It's not a big deal in itself but 
it might hide some other issues coming from now

TIA to fix it :)

Jacques

Le 21/05/2021 à 19:37, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/2100

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] b663660486074196385bdf08034547839dc1e11c
Blamelist: Nicolas Malin 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-02-04 Thread Benjamin Jugl

Sorry, I am on it.

Am 03.02.21 um 14:35 schrieb build...@apache.org:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1973

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 8fac07ad0aeb15af9bb28615f54bc514c7a4a2ba
Blamelist: Benjamin Jugl 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-01-13 Thread Daniel Watford
I'll take a look.

On Wed, 13 Jan 2021 at 12:28, Jacques Le Roux 
wrote:

> Hi Daniel,
>
> Sorry we have a small issue here, please have a look at
> https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html
>
> tasks.checkstyleMain.maxErrors is currently 286 not 293
>
> TIA
>
> Jacques
>
> Le 12/01/2021 à 13:12, build...@apache.org a écrit :
> > The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
> available at:
> >
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1945
> >
> > Buildbot URL: https://ci.apache.org/
> >
> > Buildslave for this Build: asf945_ubuntu
> >
> > Build Reason: downstream
> > Build Source Stamp: [branch trunk]
> 3795727ea2a61e686c1d09cfaa792914bd4f8730
> > Blamelist: Daniel Watford 
> >
> > BUILD FAILED: failed check
> >
> > Sincerely,
> >   -The Buildbot
> >
> >
> >
>


-- 
Daniel Watford


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2021-01-13 Thread Jacques Le Roux

Hi Daniel,

Sorry we have a small issue here, please have a look at 
https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html

tasks.checkstyleMain.maxErrors is currently 286 not 293

TIA

Jacques

Le 12/01/2021 à 13:12, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1945

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 3795727ea2a61e686c1d09cfaa792914bd4f8730
Blamelist: Daniel Watford 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-10-10 Thread Jacques Le Roux

Hi James,

I get the same errors locally, could you please have a look?

TIA

Jacques

Le 10/10/2020 à 08:17, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1845

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 5fca2ed58deb59d7eb2847810208f42cdc5f7a09
Blamelist: James Yong 

BUILD FAILED: failed testIntegration

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-10 Thread Jacques Le Roux

Thanks Girish,

Ah, I did not get those locally (Windows)

So Buildbot mixed things (anticipated, obviously a Buildbot bug) and the problem was rather 
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1751 not 1750


Anyway It's OK now

Jacques

Le 10/09/2020 à 12:05, Girish Vasmatkar a écrit :

Hi Jacques

It is actually due to 2 errors reported under UtilHtmlTest.java. I just ran
it on my machine and it failed with this.
File
/Users/grv/workspace/OFBiz/community/ofbiz-framework/framework/base/src/test/java/org/apache/ofbiz/base/util/UtilHtmlTest.java
Error DescriptionLine
Name 'parseHtmlFragment_unclosedDiv' must match pattern
'^[a-z][a-zA-Z0-9]*$'. 30
Name 'parseHtmlFragment_multiRoot' must match pattern '^[a-z][a-zA-Z0-9]*$'.

Before committing, I did not face any build failure due to checkstyle.

Best Regards,
Girish


On Thu, Sep 10, 2020 at 3:16 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Girish,

I had a quick look at this checkstyle issue, and it's weird.

It's due to
https://github.com/apache/ofbiz-plugins/commit/42192da7d3cc8bd979711e72a47b104dda0c25a3/

And I see no reason why we get

[...]
  > Task :checkstyleTest FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkstyleTest'.
  > Checkstyle rule violations were found. See the report at:
file:///C:/projectsASF/Git/ofbiz-framework/build/reports/checkstyle/test.html
Checkstyle files with violations: 1
Checkstyle violations by severity: [error:2]

Also

https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html#f-/home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/plugins/ofbiz-rest-impl/src/main/java/org/apache/ofbiz/ws/rs/resources/OFBizServiceResource.java
is useless

I'll have a look later, if you beat me on it I'll not be offended ;)

Jacques

Le 10/09/2020 à 08:17, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder

ofbizTrunkFrameworkPlugins while building ofbiz-plugins. Full details are
available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1750

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: The AnyBranchScheduler scheduler named

'onTrunkPluginsCommit' triggered this build

Build Source Stamp: [branch trunk]

42192da7d3cc8bd979711e72a47b104dda0c25a3

Blamelist: Girish Vasmatkar 

BUILD FAILED: failed check

Sincerely,
   -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-10 Thread Girish Vasmatkar
Hi Jacques

It is actually due to 2 errors reported under UtilHtmlTest.java. I just ran
it on my machine and it failed with this.
File
/Users/grv/workspace/OFBiz/community/ofbiz-framework/framework/base/src/test/java/org/apache/ofbiz/base/util/UtilHtmlTest.java
Error DescriptionLine
Name 'parseHtmlFragment_unclosedDiv' must match pattern
'^[a-z][a-zA-Z0-9]*$'. 30
Name 'parseHtmlFragment_multiRoot' must match pattern '^[a-z][a-zA-Z0-9]*$'.

Before committing, I did not face any build failure due to checkstyle.

Best Regards,
Girish


On Thu, Sep 10, 2020 at 3:16 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Girish,
>
> I had a quick look at this checkstyle issue, and it's weird.
>
> It's due to
> https://github.com/apache/ofbiz-plugins/commit/42192da7d3cc8bd979711e72a47b104dda0c25a3/
>
> And I see no reason why we get
>
> [...]
>  > Task :checkstyleTest FAILED
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':checkstyleTest'.
>  > Checkstyle rule violations were found. See the report at:
> file:///C:/projectsASF/Git/ofbiz-framework/build/reports/checkstyle/test.html
>Checkstyle files with violations: 1
>Checkstyle violations by severity: [error:2]
>
> Also
>
> https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html#f-/home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/plugins/ofbiz-rest-impl/src/main/java/org/apache/ofbiz/ws/rs/resources/OFBizServiceResource.java
> is useless
>
> I'll have a look later, if you beat me on it I'll not be offended ;)
>
> Jacques
>
> Le 10/09/2020 à 08:17, build...@apache.org a écrit :
> > The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-plugins. Full details are
> available at:
> >
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1750
> >
> > Buildbot URL: https://ci.apache.org/
> >
> > Buildslave for this Build: asf945_ubuntu
> >
> > Build Reason: The AnyBranchScheduler scheduler named
> 'onTrunkPluginsCommit' triggered this build
> > Build Source Stamp: [branch trunk]
> 42192da7d3cc8bd979711e72a47b104dda0c25a3
> > Blamelist: Girish Vasmatkar 
> >
> > BUILD FAILED: failed check
> >
> > Sincerely,
> >   -The Buildbot
> >
> >
> >
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-10 Thread Jacques Le Roux

Hi Girish,

I had a quick look at this checkstyle issue, and it's weird.

It's due to 
https://github.com/apache/ofbiz-plugins/commit/42192da7d3cc8bd979711e72a47b104dda0c25a3/

And I see no reason why we get

[...]
> Task :checkstyleTest FAILED
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':checkstyleTest'.
> Checkstyle rule violations were found. See the report at: 
file:///C:/projectsASF/Git/ofbiz-framework/build/reports/checkstyle/test.html
  Checkstyle files with violations: 1
  Checkstyle violations by severity: [error:2]

Also 
https://ci.apache.org/projects/ofbiz/logs/trunk/checkstyle.html#f-/home/buildslave/slave/ofbizTrunkFrameworkPlugins/build/plugins/ofbiz-rest-impl/src/main/java/org/apache/ofbiz/ws/rs/resources/OFBizServiceResource.java

is useless

I'll have a look later, if you beat me on it I'll not be offended ;)

Jacques

Le 10/09/2020 à 08:17, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-plugins. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1750

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf945_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'onTrunkPluginsCommit' 
triggered this build
Build Source Stamp: [branch trunk] 42192da7d3cc8bd979711e72a47b104dda0c25a3
Blamelist: Girish Vasmatkar 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-01 Thread Jacques Le Roux

Thanks Girish indeed

Le 02/09/2020 à 08:18, Suraj Khurana a écrit :

Thanks Girish.

--

Best Regards,
Suraj Khurana
Senior Technical Consultant


On Wed, Sep 2, 2020 at 11:44 AM Girish Vasmatkar <
girish.vasmat...@hotwaxsystems.com> wrote:


Hi Jacques/Akash -

I have taken care of it with my latest commit
- 310a2a58eff7cb203e4f7b25b78be23ea856aa79
Checkstyle count stays @ 2007

Best,
Girish

On Tue, Sep 1, 2020 at 10:20 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Hi Akash,

Please either fix the checkstyle issue or increase to 2008

https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins

TIA

Jacques

Le 01/09/2020 à 13:41, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder

ofbizTrunkFrameworkPlugins while building ofbiz-plugins. Full details are
available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1733

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: The AnyBranchScheduler scheduler named

'onTrunkPluginsCommit' triggered this build

Build Source Stamp: [branch trunk]

6a7136ada4d38698a3497002e65cfc1980e4954c

Blamelist: Akash Jain ,Suraj Khurana <

suraj.khur...@hotwax.co>

BUILD FAILED: failed check

Sincerely,
   -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-01 Thread Suraj Khurana
Thanks Girish.

--

Best Regards,
Suraj Khurana
Senior Technical Consultant


On Wed, Sep 2, 2020 at 11:44 AM Girish Vasmatkar <
girish.vasmat...@hotwaxsystems.com> wrote:

> Hi Jacques/Akash -
>
> I have taken care of it with my latest commit
> - 310a2a58eff7cb203e4f7b25b78be23ea856aa79
> Checkstyle count stays @ 2007
>
> Best,
> Girish
>
> On Tue, Sep 1, 2020 at 10:20 PM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > Hi Akash,
> >
> > Please either fix the checkstyle issue or increase to 2008
> >
> > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins
> >
> > TIA
> >
> > Jacques
> >
> > Le 01/09/2020 à 13:41, build...@apache.org a écrit :
> > > The Buildbot has detected a new failure on builder
> > ofbizTrunkFrameworkPlugins while building ofbiz-plugins. Full details are
> > available at:
> > >
> > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1733
> > >
> > > Buildbot URL: https://ci.apache.org/
> > >
> > > Buildslave for this Build: asf946_ubuntu
> > >
> > > Build Reason: The AnyBranchScheduler scheduler named
> > 'onTrunkPluginsCommit' triggered this build
> > > Build Source Stamp: [branch trunk]
> > 6a7136ada4d38698a3497002e65cfc1980e4954c
> > > Blamelist: Akash Jain ,Suraj Khurana <
> > suraj.khur...@hotwax.co>
> > >
> > > BUILD FAILED: failed check
> > >
> > > Sincerely,
> > >   -The Buildbot
> > >
> > >
> > >
> >
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-01 Thread Girish Vasmatkar
Hi Jacques/Akash -

I have taken care of it with my latest commit
- 310a2a58eff7cb203e4f7b25b78be23ea856aa79
Checkstyle count stays @ 2007

Best,
Girish

On Tue, Sep 1, 2020 at 10:20 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Akash,
>
> Please either fix the checkstyle issue or increase to 2008
>
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins
>
> TIA
>
> Jacques
>
> Le 01/09/2020 à 13:41, build...@apache.org a écrit :
> > The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-plugins. Full details are
> available at:
> >
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1733
> >
> > Buildbot URL: https://ci.apache.org/
> >
> > Buildslave for this Build: asf946_ubuntu
> >
> > Build Reason: The AnyBranchScheduler scheduler named
> 'onTrunkPluginsCommit' triggered this build
> > Build Source Stamp: [branch trunk]
> 6a7136ada4d38698a3497002e65cfc1980e4954c
> > Blamelist: Akash Jain ,Suraj Khurana <
> suraj.khur...@hotwax.co>
> >
> > BUILD FAILED: failed check
> >
> > Sincerely,
> >   -The Buildbot
> >
> >
> >
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-09-01 Thread Jacques Le Roux

Hi Akash,

Please either fix the checkstyle issue or increase to 2008

https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins

TIA

Jacques

Le 01/09/2020 à 13:41, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-plugins. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1733

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'onTrunkPluginsCommit' 
triggered this build
Build Source Stamp: [branch trunk] 6a7136ada4d38698a3497002e65cfc1980e4954c
Blamelist: Akash Jain ,Suraj Khurana 


BUILD FAILED: failed check

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-06-22 Thread Pawan Verma
testIntegration works fine locally.

BUILD SUCCESSFUL in 6m 2s
-- 
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Mon, Jun 22, 2020 at 11:33 PM  wrote:

> The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
> available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1515
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf946_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch trunk] 18f5dadd930f3198d9519180b37466101c221178
> Blamelist: Pawan Verma 
>
> BUILD FAILED: failed testIntegration
>
> Sincerely,
>  -The Buildbot
>
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-06-16 Thread Jacques Le Roux

Le 16/06/2020 à 18:04, Jacques Le Roux a écrit :
I'll complete all the details soon... 

Done

Jacques



Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-06-16 Thread Jacques Le Roux

Hi Suraj,

I'm currently writing a comment at OFBIZ-11304 (since this morning, with 
details)

With Aditya's work we have already installed a pre-push automated style check 
hook in trunk.
So everybody using trunk HEAD will pass by it (except if using --no-verify 
option or removing the hook by hand).

But in case of PR merge this has no effect (the related commit was a PR merge). 
Because the hook is only local.
And Infra told me they can't install  a git checkstyle pre receive hook because 
of GH.

I'll complete all the details soon...

Thanks to care :)

Jacques

Le 16/06/2020 à 15:40, Suraj Khurana a écrit :

Hello team,

As Jacques confirms in the very next commit, this was due to a checkstyle
issue introduced. I would like to request all contributors to please run
'./gradlew check' before creating PR's.

TIA.
--
Best Regards,
Suraj Khurana
Senior Technical Consultant


On Tue, Jun 16, 2020 at 4:38 PM  wrote:


The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1494

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] a3059c097dfd2f2ce85ba6eb90ac41f2556b1a91
Blamelist: Priya Sharma 

BUILD FAILED: failed check

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-06-16 Thread Suraj Khurana
Hello team,

As Jacques confirms in the very next commit, this was due to a checkstyle
issue introduced. I would like to request all contributors to please run
'./gradlew check' before creating PR's.

TIA.
--
Best Regards,
Suraj Khurana
Senior Technical Consultant


On Tue, Jun 16, 2020 at 4:38 PM  wrote:

> The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
> available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1494
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf946_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch trunk] a3059c097dfd2f2ce85ba6eb90ac41f2556b1a91
> Blamelist: Priya Sharma 
>
> BUILD FAILED: failed check
>
> Sincerely,
>  -The Buildbot
>
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-25 Thread Aditya Sharma
Sure Jacques. I will add them to the given task.

Thanks and Regards,
Aditya Sharma

On Sun, May 24, 2020 at 4:02 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Thanks Guys,
>
> We have already https://issues.apache.org/jira/browse/OFBIZ-11304
>
> Please Aditya add your references there, we need to handle that before we
> decide to abandon it...
>
> Jacques
>
> Le 23/05/2020 à 16:53, Suraj Khurana a écrit :
> > +1 Aditya
> >
> > If we can do that, that would be great.
> >
> > --
> > Suraj khurana
> >
> >
> > On Sat 23 May, 2020, 6:55 PM Aditya Sharma, 
> wrote:
> >
> >> Hi Jacques,
> >>
> >> I think *check styles* plugin is important for us and we should think of
> >> introducing a pre-commit hook that checks only for the staged changes.
> This
> >> will help developers to know about the lint issues before the commit
> >> itself.
> >>
> >> Some reference I found that achieves the above case. Though I didn't try
> >> any of these solutions.
> >>
> >>
> >>
> https://ebaytech.berlin/checkstyle-on-changed-files-with-gradle-1619e49dbe4e
> >>
> >>
> https://stackoverflow.com/questions/43730901/is-there-a-way-to-run-checkstyle-on-only-files-that-have-changes-in-vcs
> >>
> >>
> https://ealebed.github.io/posts/2020/gradle-checkstyle-on-changed-files-only/
> >>
> >> What do you think?
> >>
> >> Thanks and Regards,
> >> Aditya Sharma
> >>
> >> On Sat, May 23, 2020 at 6:44 PM Pawan Verma <
> pawan.ve...@hotwaxsystems.com
> >> wrote:
> >>
> >>> Hi Jacques,
> >>>
> >>> I care for the *checkstyle* issues but I also feel we should abandon
> it.
> >>>
> >>> --
> >>> Thanks & Regards
> >>> Pawan Verma
> >>> Technical Consultant
> >>> *HotWax Systems*
> >>> *Enterprise open source experts*
> >>> http://www.hotwaxsystems.com
> >>>
> >>>
> >>> On Sat, May 23, 2020 at 6:08 PM Jacques Le Roux <
> >>> jacques.le.r...@les7arts.com> wrote:
> >>>
>  Ha wait I confused w/ something else.
> 
>  Aas I said when starting this thread
> 
>   "this is a *checkstyle* issue. It's not clear to me why it
> >> happened."
>  Currently BuildBot makes erratic exceptions trying to pull. I have
> >>> created
>  for that (and just updated)
>  https://issues.apache.org/jira/browse/INFRA-20303
> 
>  So it's maybe not only your commit which increased the style errors...
> 
>  Unfortunately in this case, as it's then difficult to know form where
>  comes the errors (they can be cumulated commit after commit), the
> >> easier
>  issue
>  is to set tasks.checkstyleMain.maxErrors to the last reported errors
> :/
> 
>  Now I have also mentioned in the 1st msg of this thread:
> 
>   "Also I begin to wonder if the community really cares about
>  *checkstyle* issues..."
> 
>  I mean we could maybe abandon it since it seems I'm the only one to
> >>> care...
>  HTH
> 
>  Jacques
> 
>  Le 23/05/2020 à 14:23, Jacques Le Roux a écrit :
> > Thanks Suraj!
> >
> > Jacques
> >
> > Le 23/05/2020 à 14:04, Suraj Khurana a écrit :
> >> Hello team,
> >>
> >> All tests passed on my local machine.
> >>
> >> I used: ./gradlew testIntegration
> >>
> >> --
> >> Best Regards,
> >> Suraj Khurana
> >> Senior Technical Consultant
> >>
> >>
> >> On Sat, May 23, 2020 at 5:17 PM  wrote:
> >>
> >>> The Buildbot has detected a new failure on builder
> >>> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
>  details are
> >>> available at:
> >>>
> >>> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396
> >>> Buildbot URL: https://ci.apache.org/
> >>>
> >>> Buildslave for this Build: asf947_ubuntu
> >>>
> >>> Build Reason: downstream
> >>> Build Source Stamp: [branch trunk]
>  8bdb6c99856fd4ae17a95ccb0f661a256caaab13
> >>> Blamelist: Suraj Khurana <
>  64310724+surajkhur...@users.noreply.github.com>,Suraj
> >>> Khurana 
> >>>
> >>> BUILD FAILED: failed shell_2
> >>>
> >>> Sincerely,
> >>>-The Buildbot
> >>>
> >>>
> >>>
> >>>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-24 Thread Jacques Le Roux

Thanks Guys,

We have already https://issues.apache.org/jira/browse/OFBIZ-11304

Please Aditya add your references there, we need to handle that before we 
decide to abandon it...

Jacques

Le 23/05/2020 à 16:53, Suraj Khurana a écrit :

+1 Aditya

If we can do that, that would be great.

--
Suraj khurana


On Sat 23 May, 2020, 6:55 PM Aditya Sharma,  wrote:


Hi Jacques,

I think *check styles* plugin is important for us and we should think of
introducing a pre-commit hook that checks only for the staged changes. This
will help developers to know about the lint issues before the commit
itself.

Some reference I found that achieves the above case. Though I didn't try
any of these solutions.


https://ebaytech.berlin/checkstyle-on-changed-files-with-gradle-1619e49dbe4e

https://stackoverflow.com/questions/43730901/is-there-a-way-to-run-checkstyle-on-only-files-that-have-changes-in-vcs

https://ealebed.github.io/posts/2020/gradle-checkstyle-on-changed-files-only/

What do you think?

Thanks and Regards,
Aditya Sharma

On Sat, May 23, 2020 at 6:44 PM Pawan Verma 
Hi Jacques,

I care for the *checkstyle* issues but I also feel we should abandon it.

--
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Sat, May 23, 2020 at 6:08 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:


Ha wait I confused w/ something else.

Aas I said when starting this thread

 "this is a *checkstyle* issue. It's not clear to me why it

happened."

Currently BuildBot makes erratic exceptions trying to pull. I have

created

for that (and just updated)
https://issues.apache.org/jira/browse/INFRA-20303

So it's maybe not only your commit which increased the style errors...

Unfortunately in this case, as it's then difficult to know form where
comes the errors (they can be cumulated commit after commit), the

easier

issue
is to set tasks.checkstyleMain.maxErrors to the last reported errors :/

Now I have also mentioned in the 1st msg of this thread:

 "Also I begin to wonder if the community really cares about
*checkstyle* issues..."

I mean we could maybe abandon it since it seems I'm the only one to

care...

HTH

Jacques

Le 23/05/2020 à 14:23, Jacques Le Roux a écrit :

Thanks Suraj!

Jacques

Le 23/05/2020 à 14:04, Suraj Khurana a écrit :

Hello team,

All tests passed on my local machine.

I used: ./gradlew testIntegration

--
Best Regards,
Suraj Khurana
Senior Technical Consultant


On Sat, May 23, 2020 at 5:17 PM  wrote:


The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full

details are

available at:


https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk]

8bdb6c99856fd4ae17a95ccb0f661a256caaab13

Blamelist: Suraj Khurana <

64310724+surajkhur...@users.noreply.github.com>,Suraj

Khurana 

BUILD FAILED: failed shell_2

Sincerely,
   -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-23 Thread Suraj Khurana
+1 Aditya

If we can do that, that would be great.

--
Suraj khurana


On Sat 23 May, 2020, 6:55 PM Aditya Sharma,  wrote:

> Hi Jacques,
>
> I think *check styles* plugin is important for us and we should think of
> introducing a pre-commit hook that checks only for the staged changes. This
> will help developers to know about the lint issues before the commit
> itself.
>
> Some reference I found that achieves the above case. Though I didn't try
> any of these solutions.
>
>
> https://ebaytech.berlin/checkstyle-on-changed-files-with-gradle-1619e49dbe4e
>
> https://stackoverflow.com/questions/43730901/is-there-a-way-to-run-checkstyle-on-only-files-that-have-changes-in-vcs
>
> https://ealebed.github.io/posts/2020/gradle-checkstyle-on-changed-files-only/
>
> What do you think?
>
> Thanks and Regards,
> Aditya Sharma
>
> On Sat, May 23, 2020 at 6:44 PM Pawan Verma  >
> wrote:
>
> > Hi Jacques,
> >
> > I care for the *checkstyle* issues but I also feel we should abandon it.
> >
> > --
> > Thanks & Regards
> > Pawan Verma
> > Technical Consultant
> > *HotWax Systems*
> > *Enterprise open source experts*
> > http://www.hotwaxsystems.com
> >
> >
> > On Sat, May 23, 2020 at 6:08 PM Jacques Le Roux <
> > jacques.le.r...@les7arts.com> wrote:
> >
> > > Ha wait I confused w/ something else.
> > >
> > > Aas I said when starting this thread
> > >
> > > "this is a *checkstyle* issue. It's not clear to me why it
> happened."
> > >
> > > Currently BuildBot makes erratic exceptions trying to pull. I have
> > created
> > > for that (and just updated)
> > > https://issues.apache.org/jira/browse/INFRA-20303
> > >
> > > So it's maybe not only your commit which increased the style errors...
> > >
> > > Unfortunately in this case, as it's then difficult to know form where
> > > comes the errors (they can be cumulated commit after commit), the
> easier
> > > issue
> > > is to set tasks.checkstyleMain.maxErrors to the last reported errors :/
> > >
> > > Now I have also mentioned in the 1st msg of this thread:
> > >
> > > "Also I begin to wonder if the community really cares about
> > > *checkstyle* issues..."
> > >
> > > I mean we could maybe abandon it since it seems I'm the only one to
> > care...
> > >
> > > HTH
> > >
> > > Jacques
> > >
> > > Le 23/05/2020 à 14:23, Jacques Le Roux a écrit :
> > > > Thanks Suraj!
> > > >
> > > > Jacques
> > > >
> > > > Le 23/05/2020 à 14:04, Suraj Khurana a écrit :
> > > >> Hello team,
> > > >>
> > > >> All tests passed on my local machine.
> > > >>
> > > >> I used: ./gradlew testIntegration
> > > >>
> > > >> --
> > > >> Best Regards,
> > > >> Suraj Khurana
> > > >> Senior Technical Consultant
> > > >>
> > > >>
> > > >> On Sat, May 23, 2020 at 5:17 PM  wrote:
> > > >>
> > > >>> The Buildbot has detected a new failure on builder
> > > >>> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
> > > details are
> > > >>> available at:
> > > >>>
> > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396
> > > >>>
> > > >>> Buildbot URL: https://ci.apache.org/
> > > >>>
> > > >>> Buildslave for this Build: asf947_ubuntu
> > > >>>
> > > >>> Build Reason: downstream
> > > >>> Build Source Stamp: [branch trunk]
> > > 8bdb6c99856fd4ae17a95ccb0f661a256caaab13
> > > >>> Blamelist: Suraj Khurana <
> > > 64310724+surajkhur...@users.noreply.github.com>,Suraj
> > > >>> Khurana 
> > > >>>
> > > >>> BUILD FAILED: failed shell_2
> > > >>>
> > > >>> Sincerely,
> > > >>>   -The Buildbot
> > > >>>
> > > >>>
> > > >>>
> > > >>>
> > >
> >
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-23 Thread Aditya Sharma
Hi Jacques,

I think *check styles* plugin is important for us and we should think of
introducing a pre-commit hook that checks only for the staged changes. This
will help developers to know about the lint issues before the commit itself.

Some reference I found that achieves the above case. Though I didn't try
any of these solutions.

https://ebaytech.berlin/checkstyle-on-changed-files-with-gradle-1619e49dbe4e
https://stackoverflow.com/questions/43730901/is-there-a-way-to-run-checkstyle-on-only-files-that-have-changes-in-vcs
https://ealebed.github.io/posts/2020/gradle-checkstyle-on-changed-files-only/

What do you think?

Thanks and Regards,
Aditya Sharma

On Sat, May 23, 2020 at 6:44 PM Pawan Verma 
wrote:

> Hi Jacques,
>
> I care for the *checkstyle* issues but I also feel we should abandon it.
>
> --
> Thanks & Regards
> Pawan Verma
> Technical Consultant
> *HotWax Systems*
> *Enterprise open source experts*
> http://www.hotwaxsystems.com
>
>
> On Sat, May 23, 2020 at 6:08 PM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
> > Ha wait I confused w/ something else.
> >
> > Aas I said when starting this thread
> >
> > "this is a *checkstyle* issue. It's not clear to me why it happened."
> >
> > Currently BuildBot makes erratic exceptions trying to pull. I have
> created
> > for that (and just updated)
> > https://issues.apache.org/jira/browse/INFRA-20303
> >
> > So it's maybe not only your commit which increased the style errors...
> >
> > Unfortunately in this case, as it's then difficult to know form where
> > comes the errors (they can be cumulated commit after commit), the easier
> > issue
> > is to set tasks.checkstyleMain.maxErrors to the last reported errors :/
> >
> > Now I have also mentioned in the 1st msg of this thread:
> >
> > "Also I begin to wonder if the community really cares about
> > *checkstyle* issues..."
> >
> > I mean we could maybe abandon it since it seems I'm the only one to
> care...
> >
> > HTH
> >
> > Jacques
> >
> > Le 23/05/2020 à 14:23, Jacques Le Roux a écrit :
> > > Thanks Suraj!
> > >
> > > Jacques
> > >
> > > Le 23/05/2020 à 14:04, Suraj Khurana a écrit :
> > >> Hello team,
> > >>
> > >> All tests passed on my local machine.
> > >>
> > >> I used: ./gradlew testIntegration
> > >>
> > >> --
> > >> Best Regards,
> > >> Suraj Khurana
> > >> Senior Technical Consultant
> > >>
> > >>
> > >> On Sat, May 23, 2020 at 5:17 PM  wrote:
> > >>
> > >>> The Buildbot has detected a new failure on builder
> > >>> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
> > details are
> > >>> available at:
> > >>>
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396
> > >>>
> > >>> Buildbot URL: https://ci.apache.org/
> > >>>
> > >>> Buildslave for this Build: asf947_ubuntu
> > >>>
> > >>> Build Reason: downstream
> > >>> Build Source Stamp: [branch trunk]
> > 8bdb6c99856fd4ae17a95ccb0f661a256caaab13
> > >>> Blamelist: Suraj Khurana <
> > 64310724+surajkhur...@users.noreply.github.com>,Suraj
> > >>> Khurana 
> > >>>
> > >>> BUILD FAILED: failed shell_2
> > >>>
> > >>> Sincerely,
> > >>>   -The Buildbot
> > >>>
> > >>>
> > >>>
> > >>>
> >
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-23 Thread Pawan Verma
Hi Jacques,

I care for the *checkstyle* issues but I also feel we should abandon it.

-- 
Thanks & Regards
Pawan Verma
Technical Consultant
*HotWax Systems*
*Enterprise open source experts*
http://www.hotwaxsystems.com


On Sat, May 23, 2020 at 6:08 PM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Ha wait I confused w/ something else.
>
> Aas I said when starting this thread
>
> "this is a *checkstyle* issue. It's not clear to me why it happened."
>
> Currently BuildBot makes erratic exceptions trying to pull. I have created
> for that (and just updated)
> https://issues.apache.org/jira/browse/INFRA-20303
>
> So it's maybe not only your commit which increased the style errors...
>
> Unfortunately in this case, as it's then difficult to know form where
> comes the errors (they can be cumulated commit after commit), the easier
> issue
> is to set tasks.checkstyleMain.maxErrors to the last reported errors :/
>
> Now I have also mentioned in the 1st msg of this thread:
>
> "Also I begin to wonder if the community really cares about
> *checkstyle* issues..."
>
> I mean we could maybe abandon it since it seems I'm the only one to care...
>
> HTH
>
> Jacques
>
> Le 23/05/2020 à 14:23, Jacques Le Roux a écrit :
> > Thanks Suraj!
> >
> > Jacques
> >
> > Le 23/05/2020 à 14:04, Suraj Khurana a écrit :
> >> Hello team,
> >>
> >> All tests passed on my local machine.
> >>
> >> I used: ./gradlew testIntegration
> >>
> >> --
> >> Best Regards,
> >> Suraj Khurana
> >> Senior Technical Consultant
> >>
> >>
> >> On Sat, May 23, 2020 at 5:17 PM  wrote:
> >>
> >>> The Buildbot has detected a new failure on builder
> >>> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full
> details are
> >>> available at:
> >>> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396
> >>>
> >>> Buildbot URL: https://ci.apache.org/
> >>>
> >>> Buildslave for this Build: asf947_ubuntu
> >>>
> >>> Build Reason: downstream
> >>> Build Source Stamp: [branch trunk]
> 8bdb6c99856fd4ae17a95ccb0f661a256caaab13
> >>> Blamelist: Suraj Khurana <
> 64310724+surajkhur...@users.noreply.github.com>,Suraj
> >>> Khurana 
> >>>
> >>> BUILD FAILED: failed shell_2
> >>>
> >>> Sincerely,
> >>>   -The Buildbot
> >>>
> >>>
> >>>
> >>>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-23 Thread Jacques Le Roux

Ha wait I confused w/ something else.

Aas I said when starting this thread

   "this is a *checkstyle* issue. It's not clear to me why it happened."

Currently BuildBot makes erratic exceptions trying to pull. I have created for 
that (and just updated) https://issues.apache.org/jira/browse/INFRA-20303

So it's maybe not only your commit which increased the style errors...

Unfortunately in this case, as it's then difficult to know form where comes the errors (they can be cumulated commit after commit), the easier issue 
is to set tasks.checkstyleMain.maxErrors to the last reported errors :/


Now I have also mentioned in the 1st msg of this thread:

   "Also I begin to wonder if the community really cares about *checkstyle* 
issues..."

I mean we could maybe abandon it since it seems I'm the only one to care...

HTH

Jacques

Le 23/05/2020 à 14:23, Jacques Le Roux a écrit :

Thanks Suraj!

Jacques

Le 23/05/2020 à 14:04, Suraj Khurana a écrit :

Hello team,

All tests passed on my local machine.

I used: ./gradlew testIntegration

--
Best Regards,
Suraj Khurana
Senior Technical Consultant


On Sat, May 23, 2020 at 5:17 PM  wrote:


The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 8bdb6c99856fd4ae17a95ccb0f661a256caaab13
Blamelist: Suraj Khurana <64310724+surajkhur...@users.noreply.github.com>,Suraj
Khurana 

BUILD FAILED: failed shell_2

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-23 Thread Jacques Le Roux

Thanks Suraj!

Jacques

Le 23/05/2020 à 14:04, Suraj Khurana a écrit :

Hello team,

All tests passed on my local machine.

I used: ./gradlew testIntegration

--
Best Regards,
Suraj Khurana
Senior Technical Consultant


On Sat, May 23, 2020 at 5:17 PM  wrote:


The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf947_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 8bdb6c99856fd4ae17a95ccb0f661a256caaab13
Blamelist: Suraj Khurana <64310724+surajkhur...@users.noreply.github.com>,Suraj
Khurana 

BUILD FAILED: failed shell_2

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-23 Thread Suraj Khurana
Hello team,

All tests passed on my local machine.

I used: ./gradlew testIntegration

--
Best Regards,
Suraj Khurana
Senior Technical Consultant


On Sat, May 23, 2020 at 5:17 PM  wrote:

> The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details are
> available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1396
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf947_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch trunk] 8bdb6c99856fd4ae17a95ccb0f661a256caaab13
> Blamelist: Suraj Khurana 
> <64310724+surajkhur...@users.noreply.github.com>,Suraj
> Khurana 
>
> BUILD FAILED: failed shell_2
>
> Sincerely,
>  -The Buildbot
>
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-05-22 Thread Jacques Le Roux

Hi All,

This is a checkstyle issue. It's not clear to me why it happened.

Because there is only a Freemarker template change in 1388, weird!

Also I begin to wonder if the community really cares about checkstyle issues...

Opinions?

Jacques

Le 21/05/2020 à 17:06, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1388

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] e46c7b97249d0d7c74d3833f0c8b69cc4881c8e0
Blamelist: James Yong 

BUILD FAILED: failed shell_2

Sincerely,
  -The Buildbot





Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-02-12 Thread Gil Portenseigne
It's an error while cherry picking the bugFix from trunk.

I will revert.

On Wed, Feb 12, 2020 at 12:10:46PM +0100, Gil Portenseigne wrote:
> Yes, i'm on it...
> On Wed, Feb 12, 2020 at 11:56:14AM +0100, Jacques Le Roux wrote:
> > It's OK, but we have now a compilation in R17: 
> > https://ci.apache.org/builders/ofbizBranch17Framework
> > 
> > Please Gil have a look
> > 
> > Thanks
> > 
> > Le 12/02/2020 à 09:00, Jacques Le Roux a écrit :
> > > Hi Michael,
> > > 
> > > There were no issues before your commit:
> > > 
> > > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins
> > > 
> > > And it was not squashed with another one:
> > > 
> > > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150
> > > 
> > > I suspect a Buildbot error, I'm testing locally to confirm. I'll also 
> > > launch the same on Buildbot
> > > 
> > > Jacques
> > > 
> > > Le 12/02/2020 à 07:57, Michael Brohl a écrit :
> > > > Hi all,
> > > > 
> > > > the errors reported during the build (test classes not found) do not 
> > > > seem to have been introduced by my latest change.
> > > > 
> > > > Any ideas where this come from?
> > > > 
> > > > See 
> > > > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150/steps/shell_5/logs/stdio
> > > > 
> > > > Best regards,
> > > > 
> > > > Michael Brohl
> > > > 
> > > > ecomify GmbH - www.ecomify.de
> > > > 
> > > > Am 11.02.20 um 23:51 schrieb build...@apache.org:
> > > > > The Buildbot has detected a new failure on builder 
> > > > > ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full 
> > > > > details are available at:
> > > > > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150
> > > > > 
> > > > > Buildbot URL: https://ci.apache.org/
> > > > > 
> > > > > Buildslave for this Build: asf946_ubuntu
> > > > > 
> > > > > Build Reason: downstream
> > > > > Build Source Stamp: [branch trunk] 
> > > > > 3788f6766a01eb476c15d32e6b9d9127061d12f4
> > > > > Blamelist: Michael Brohl 
> > > > > 
> > > > > BUILD FAILED: failed shell_5
> > > > > 
> > > > > Sincerely,
> > > > >   -The Buildbot
> > > > > 
> > > > > 
> > > > > 
> > > > 




signature.asc
Description: PGP signature


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-02-12 Thread Gil Portenseigne
Yes, i'm on it...
On Wed, Feb 12, 2020 at 11:56:14AM +0100, Jacques Le Roux wrote:
> It's OK, but we have now a compilation in R17: 
> https://ci.apache.org/builders/ofbizBranch17Framework
> 
> Please Gil have a look
> 
> Thanks
> 
> Le 12/02/2020 à 09:00, Jacques Le Roux a écrit :
> > Hi Michael,
> > 
> > There were no issues before your commit:
> > 
> > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins
> > 
> > And it was not squashed with another one:
> > 
> > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150
> > 
> > I suspect a Buildbot error, I'm testing locally to confirm. I'll also 
> > launch the same on Buildbot
> > 
> > Jacques
> > 
> > Le 12/02/2020 à 07:57, Michael Brohl a écrit :
> > > Hi all,
> > > 
> > > the errors reported during the build (test classes not found) do not seem 
> > > to have been introduced by my latest change.
> > > 
> > > Any ideas where this come from?
> > > 
> > > See 
> > > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150/steps/shell_5/logs/stdio
> > > 
> > > Best regards,
> > > 
> > > Michael Brohl
> > > 
> > > ecomify GmbH - www.ecomify.de
> > > 
> > > Am 11.02.20 um 23:51 schrieb build...@apache.org:
> > > > The Buildbot has detected a new failure on builder 
> > > > ofbizTrunkFrameworkPlugins while building ofbiz-framework. Full details 
> > > > are available at:
> > > > https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150
> > > > 
> > > > Buildbot URL: https://ci.apache.org/
> > > > 
> > > > Buildslave for this Build: asf946_ubuntu
> > > > 
> > > > Build Reason: downstream
> > > > Build Source Stamp: [branch trunk] 
> > > > 3788f6766a01eb476c15d32e6b9d9127061d12f4
> > > > Blamelist: Michael Brohl 
> > > > 
> > > > BUILD FAILED: failed shell_5
> > > > 
> > > > Sincerely,
> > > >   -The Buildbot
> > > > 
> > > > 
> > > > 
> > > 


signature.asc
Description: PGP signature


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-02-12 Thread Jacques Le Roux

It's OK, but we have now a compilation in R17: 
https://ci.apache.org/builders/ofbizBranch17Framework

Please Gil have a look

Thanks

Le 12/02/2020 à 09:00, Jacques Le Roux a écrit :

Hi Michael,

There were no issues before your commit:

https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins

And it was not squashed with another one:

https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150

I suspect a Buildbot error, I'm testing locally to confirm. I'll also launch 
the same on Buildbot

Jacques

Le 12/02/2020 à 07:57, Michael Brohl a écrit :

Hi all,

the errors reported during the build (test classes not found) do not seem to 
have been introduced by my latest change.

Any ideas where this come from?

See 
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150/steps/shell_5/logs/stdio

Best regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 11.02.20 um 23:51 schrieb build...@apache.org:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 3788f6766a01eb476c15d32e6b9d9127061d12f4
Blamelist: Michael Brohl 

BUILD FAILED: failed shell_5

Sincerely,
  -The Buildbot







Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-02-12 Thread Jacques Le Roux

Hi Michael,

There were no issues before your commit:

https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins

And it was not squashed with another one:

https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150

I suspect a Buildbot error, I'm testing locally to confirm. I'll also launch 
the same on Buildbot

Jacques

Le 12/02/2020 à 07:57, Michael Brohl a écrit :

Hi all,

the errors reported during the build (test classes not found) do not seem to 
have been introduced by my latest change.

Any ideas where this come from?

See 
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150/steps/shell_5/logs/stdio

Best regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 11.02.20 um 23:51 schrieb build...@apache.org:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 3788f6766a01eb476c15d32e6b9d9127061d12f4
Blamelist: Michael Brohl 

BUILD FAILED: failed shell_5

Sincerely,
  -The Buildbot







Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2020-02-11 Thread Michael Brohl

Hi all,

the errors reported during the build (test classes not found) do not 
seem to have been introduced by my latest change.


Any ideas where this come from?

See 
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150/steps/shell_5/logs/stdio


Best regards,

Michael Brohl

ecomify GmbH - www.ecomify.de

Am 11.02.20 um 23:51 schrieb build...@apache.org:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building ofbiz-framework. Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/1150

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: downstream
Build Source Stamp: [branch trunk] 3788f6766a01eb476c15d32e6b9d9127061d12f4
Blamelist: Michael Brohl 

BUILD FAILED: failed shell_5

Sincerely,
  -The Buildbot







smime.p7s
Description: S/MIME Cryptographic Signature


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-09-22 Thread Mathieu Lirzin
build...@apache.org writes:

> The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
> while building . Full details are available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/988
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: asf945_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1867343
> Blamelist: mthl
>
> BUILD FAILED: failed shell_4

‘gradlew testIntegration’ works locally with official plugins.

-- 
Mathieu Lirzin
GPG: F2A3 8D7E EB2B 6640 5761  070D 0ADE E100 9460 4D37


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-08-22 Thread Jacques Le Roux

Works locally

Le 18/08/2019 à 18:29, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/922

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: asf946_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1865397
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-05-26 Thread Jacques Le Roux

OK locally

Le 26/05/2019 à 13:21, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/822

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1860051
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-04-27 Thread Rishi Solanki
I see below JUNIT failure as;
- shipment-tests.testPackingServices : Error trying to begin transaction,
could not process method: The current transaction is marked for rollback,
not beginning a new transaction and aborting current operation; the
rollbackOnly was caused by: Error in Service
[completeAllocationPlanItemByOrderItem]: ERROR : Allocation plan is not
available.: [DEMO10090:1]
- production-run-tests.testCreateProductionRunForOrder : Assertion failed:
( NOT empty[originalOrderItemShipGrpInvRes=null]
-
auto-accounting-transaction-tests-sales.testAcctgTransForSalesOrderShipments
: Error trying to begin transaction, could not process method: The current
transaction is marked for rollback, not beginning a new transaction and
aborting current operation; the rollbackOnly was caused by: Error in
Service [completeAllocationPlanItemByOrderItem]: ERROR : Allocation plan is
not available.: [DEMO10090:1]
- productRentalOrder-test : Warning: no shipments created; could not find
anything ready and needing to be shipped.

These are not related to my commit, will check more and see if can fix
them. Thanks!

Best Regards,
--
*Rishi Solanki* | Sr Manager, Enterprise Software Development
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Rishi Solanki*

Direct: +91-9893287847


On Sun, Apr 28, 2019 at 1:49 AM Rishi Solanki 
wrote:

> Jacques,
> I'm looking into this, thanks!
>
> Best Regards,
> --
> *Rishi Solanki* | Sr Manager, Enterprise Software Development
> HotWax Systems 
> Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center,
> Indore, M.P 452010
> Linkedin: *Rishi Solanki*
> 
> Direct: +91-9893287847
>
>
> On Sun, Apr 28, 2019 at 12:38 AM Jacques Le Roux <
> jacques.le.r...@les7arts.com> wrote:
>
>> Hi Rishi,
>>
>> I reproduce locally but I don't understand why we have this problem (the
>> concerned data have no relation with the changed component)
>>
>> https://ci.apache.org/projects/ofbiz/logs/trunk/plugins/html/
>>
>> Also I still get the issue when I remove the plugin
>>
>> Thanks
>>
>> Jacques
>>
>> Le 27/04/2019 à 16:26, build...@apache.org a écrit :
>> > The Buildbot has detected a new failure on builder
>> ofbizTrunkFrameworkPlugins while building . Full details are available at:
>> >
>> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/769
>> >
>> > Buildbot URL: https://ci.apache.org/
>> >
>> > Buildslave for this Build: silvanus_ubuntu
>> >
>> > Build Reason: The AnyBranchScheduler scheduler named
>> 'onTrunkPluginsCommit' triggered this build
>> > Build Source Stamp: [branch ofbiz/ofbiz-plugins/trunk] 1858279
>> > Blamelist: rishi
>> >
>> > BUILD FAILED: failed shell_4
>> >
>> > Sincerely,
>> >   -The Buildbot
>> >
>> >
>> >
>> >
>>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-04-27 Thread Rishi Solanki
Jacques,
I'm looking into this, thanks!

Best Regards,
--
*Rishi Solanki* | Sr Manager, Enterprise Software Development
HotWax Systems 
Plot no. 80, Scheme no. 78 Part 2, Near Brilliant Convention Center, Indore,
M.P 452010
Linkedin: *Rishi Solanki*

Direct: +91-9893287847


On Sun, Apr 28, 2019 at 12:38 AM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:

> Hi Rishi,
>
> I reproduce locally but I don't understand why we have this problem (the
> concerned data have no relation with the changed component)
>
> https://ci.apache.org/projects/ofbiz/logs/trunk/plugins/html/
>
> Also I still get the issue when I remove the plugin
>
> Thanks
>
> Jacques
>
> Le 27/04/2019 à 16:26, build...@apache.org a écrit :
> > The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building . Full details are available at:
> >
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/769
> >
> > Buildbot URL: https://ci.apache.org/
> >
> > Buildslave for this Build: silvanus_ubuntu
> >
> > Build Reason: The AnyBranchScheduler scheduler named
> 'onTrunkPluginsCommit' triggered this build
> > Build Source Stamp: [branch ofbiz/ofbiz-plugins/trunk] 1858279
> > Blamelist: rishi
> >
> > BUILD FAILED: failed shell_4
> >
> > Sincerely,
> >   -The Buildbot
> >
> >
> >
> >
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-04-27 Thread Jacques Le Roux

Hi Rishi,

I reproduce locally but I don't understand why we have this problem (the 
concerned data have no relation with the changed component)

https://ci.apache.org/projects/ofbiz/logs/trunk/plugins/html/

Also I still get the issue when I remove the plugin

Thanks

Jacques

Le 27/04/2019 à 16:26, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/769

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: The AnyBranchScheduler scheduler named 'onTrunkPluginsCommit' 
triggered this build
Build Source Stamp: [branch ofbiz/ofbiz-plugins/trunk] 1858279
Blamelist: rishi

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2019-03-26 Thread Jacques Le Roux

The errors are inconsistent in both Buildbot and locally, I consider as not an 
issue

Jacques

Le 25/03/2019 à 19:43, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/745

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1856212
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-12-29 Thread Jacques Le Roux

Thanks Gil,

I tried again locally and got also no issues

Jacques

Le 29/12/2018 à 11:10, Gil Portenseigne a écrit :

Hello,

I just checked again with  ‘./gradlew cleanAll loadAll testIntegration’,
A got build successful... no failure.

Gil

Le 20:11 - vendredi 28 déc., Jacques Le Roux a écrit :

Hi Gil,

Are we sure there is not a test issue with this commit?

Locally I can't reproduce the same but I have also 4 failures, could you please 
check on your side?

Thanks

Jacques

Le 28/12/2018 à 15:28, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
  https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/625

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1849853
Blamelist: pgil

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-12-29 Thread Gil Portenseigne
Hello,

I just checked again with  ‘./gradlew cleanAll loadAll testIntegration’,
A got build successful... no failure.

Gil

Le 20:11 - vendredi 28 déc., Jacques Le Roux a écrit :
> Hi Gil,
> 
> Are we sure there is not a test issue with this commit?
> 
> Locally I can't reproduce the same but I have also 4 failures, could you 
> please check on your side?
> 
> Thanks
> 
> Jacques
> 
> Le 28/12/2018 à 15:28, build...@apache.org a écrit :
> > The Buildbot has detected a new failure on builder 
> > ofbizTrunkFrameworkPlugins while building . Full details are available at:
> >  https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/625
> > 
> > Buildbot URL: https://ci.apache.org/
> > 
> > Buildslave for this Build: silvanus_ubuntu
> > 
> > Build Reason: downstream
> > Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1849853
> > Blamelist: pgil
> > 
> > BUILD FAILED: failed shell_4
> > 
> > Sincerely,
> >   -The Buildbot
> > 
> > 
> > 
> > 


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-12-28 Thread Jacques Le Roux

Hi Gil,

Are we sure there is not a test issue with this commit?

Locally I can't reproduce the same but I have also 4 failures, could you please 
check on your side?

Thanks

Jacques

Le 28/12/2018 à 15:28, build...@apache.org a écrit :

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/625

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: silvanus_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1849853
Blamelist: pgil

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot






Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-11 Thread Jacques Le Roux

Please follow, this is related to http://markmail.org/message/vltmfn6x7wsfpss2

Jacques


Le 11/01/2018 à 13:18, Taher Alkhateeb a écrit :

So it seems like we have faulty buildbot scripts again. I feel inclined to
rewrite them from scratch. Anyone interested in helping out?

On Jan 11, 2018 3:16 PM,  wrote:


The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/16

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820862
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot








Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-11 Thread Taher Alkhateeb
So it seems like we have faulty buildbot scripts again. I feel inclined to
rewrite them from scratch. Anyone interested in helping out?

On Jan 11, 2018 3:16 PM,  wrote:

> The Buildbot has detected a new failure on builder
> ofbizTrunkFrameworkPlugins while building . Full details are available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/16
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: orcus_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820862
> Blamelist: jleroux
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>  -The Buildbot
>
>
>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-09 Thread Jacques Le Roux

Hi Taher, All,

I put a small BuildBot documentation at 
https://svn.apache.org/repos/asf/ofbiz/tools/documentation/BuildBot I'll now 
create a wiki page to import it

Everybody is welcome to try and improve it

Jacques

Le 07/01/2018 à 23:54, Jacques Le Roux a écrit :


Le 07/01/2018 à 21:08, Taher Alkhateeb a écrit :

Sorry, I'm not sure what you mean by a transient error?

A test error which happens only once.  The same code (no commits between) is 
used few minutes later and it works.
If you want to know more about possible such issues please ask infra.
I was told in the pass that such things happen. Why do you think I use IRC? I 
did not discover this by myself.


How did you determine that it is a transient error,

Because it works locally and, when it's launched from IRC just after, the same 
code passes the tests on Buildbot also.


and did you identify what is causing it?

That I have not ideas and you need to ask infra. There is one sentence I often heard when 
asking: "shit happen" (you certainly know about the fan too)
I was also told that disk and especially network issues happen. The ASF is far from owning all the machines and IIRW the Buildbot machines: 
https://ci.apache.org/



Why are we having more of these errors than in the past?

I think you mix repetitive false warning, which was fixed with INFRA-15394, 
with these kinds of issues:

1. svn fails to update
2. tests pass locally but not on Buildbot

which happen from time to time and not specially more now. Then IRC, with the 
restriction I explained below, is the solution.

Jacques



On Sun, Jan 7, 2018 at 8:41 PM, Jacques Le Roux
 wrote:

Le 07/01/2018 à 15:44, Taher Alkhateeb a écrit :

I am suspecting this is still a broken build system rather than a
genuine error. Can you confirm?

It's not a "broken build system" but was a transient error as you can see
there
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins


If tests are running okay locally

Yes they are, at least now...


then we still have a faulty build logic.

Nope, it's not a "faulty build logic." just a transient error on build
servers

When you see that tests pass locally and not on Buildbot it's most certainly
an issue with servers.
Those are hard workers and make errors from time to time (which shows that
not only human make errors)

When something like that happens, I get to IRC (using
https://webchat.freenode.net)
There using a recognisable username (I use jleroux) I get to the ofbiz
channel.
I wait for ofbiz-bot to appear, click on query and then I can make a request
in the chat line to restart a scheduler.
A request is of the form
"force build ofbizTrunkFrameworkPlugins"
you put the text you want to appear after this expression, something like
"forces manual build after Buildbot weird 85 errors on labels :-o"

I hope this clarify. I'll put a .md file in tools\documentation\BuildBot and
will import is as HTML in a new wiki page for BuildBot

I hope this will help us to get to a fruitful collaboration :)

BTW we are still waiting for something to happen, see
https://issues.apache.org/jira/browse/INFRA-15785

Jacques



On Sun, Jan 7, 2018 at 5:20 PM,  wrote:

The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building . Full details are available at:
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/10

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820457
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot










Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-07 Thread Jacques Le Roux


Le 07/01/2018 à 21:08, Taher Alkhateeb a écrit :

Sorry, I'm not sure what you mean by a transient error?

A test error which happens only once.  The same code (no commits between) is 
used few minutes later and it works.
If you want to know more about possible such issues please ask infra.
I was told in the pass that such things happen. Why do you think I use IRC? I 
did not discover this by myself.


How did you determine that it is a transient error,

Because it works locally and, when it's launched from IRC just after, the same 
code passes the tests on Buildbot also.


and did you identify what is causing it?

That I have not ideas and you need to ask infra. There is one sentence I often heard when 
asking: "shit happen" (you certainly know about the fan too)
I was also told that disk and especially network issues happen. The ASF is far from owning all the machines and IIRW the Buildbot machines: 
https://ci.apache.org/



Why are we having more of these errors than in the past?

I think you mix repetitive false warning, which was fixed with INFRA-15394, 
with these kinds of issues:

1. svn fails to update
2. tests pass locally but not on Buildbot

which happen from time to time and not specially more now. Then IRC, with the 
restriction I explained below, is the solution.

Jacques



On Sun, Jan 7, 2018 at 8:41 PM, Jacques Le Roux
 wrote:

Le 07/01/2018 à 15:44, Taher Alkhateeb a écrit :

I am suspecting this is still a broken build system rather than a
genuine error. Can you confirm?

It's not a "broken build system" but was a transient error as you can see
there
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins


If tests are running okay locally

Yes they are, at least now...


then we still have a faulty build logic.

Nope, it's not a "faulty build logic." just a transient error on build
servers

When you see that tests pass locally and not on Buildbot it's most certainly
an issue with servers.
Those are hard workers and make errors from time to time (which shows that
not only human make errors)

When something like that happens, I get to IRC (using
https://webchat.freenode.net)
There using a recognisable username (I use jleroux) I get to the ofbiz
channel.
I wait for ofbiz-bot to appear, click on query and then I can make a request
in the chat line to restart a scheduler.
A request is of the form
"force build ofbizTrunkFrameworkPlugins"
you put the text you want to appear after this expression, something like
"forces manual build after Buildbot weird 85 errors on labels :-o"

I hope this clarify. I'll put a .md file in tools\documentation\BuildBot and
will import is as HTML in a new wiki page for BuildBot

I hope this will help us to get to a fruitful collaboration :)

BTW we are still waiting for something to happen, see
https://issues.apache.org/jira/browse/INFRA-15785

Jacques



On Sun, Jan 7, 2018 at 5:20 PM,   wrote:

The Buildbot has detected a new failure on builder
ofbizTrunkFrameworkPlugins while building . Full details are available at:
  https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/10

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820457
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
   -The Buildbot







Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-07 Thread Taher Alkhateeb
Sorry, I'm not sure what you mean by a transient error? How did you
determine that it is a transient error, and did you identify what is
causing it? Why are we having more of these errors than in the past?

On Sun, Jan 7, 2018 at 8:41 PM, Jacques Le Roux
 wrote:
> Le 07/01/2018 à 15:44, Taher Alkhateeb a écrit :
>>
>> I am suspecting this is still a broken build system rather than a
>> genuine error. Can you confirm?
>
> It's not a "broken build system" but was a transient error as you can see
> there
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins
>
>> If tests are running okay locally
>
> Yes they are, at least now...
>
>> then we still have a faulty build logic.
>
> Nope, it's not a "faulty build logic." just a transient error on build
> servers
>
> When you see that tests pass locally and not on Buildbot it's most certainly
> an issue with servers.
> Those are hard workers and make errors from time to time (which shows that
> not only human make errors)
>
> When something like that happens, I get to IRC (using
> https://webchat.freenode.net)
> There using a recognisable username (I use jleroux) I get to the ofbiz
> channel.
> I wait for ofbiz-bot to appear, click on query and then I can make a request
> in the chat line to restart a scheduler.
> A request is of the form
> "force build ofbizTrunkFrameworkPlugins"
> you put the text you want to appear after this expression, something like
> "forces manual build after Buildbot weird 85 errors on labels :-o"
>
> I hope this clarify. I'll put a .md file in tools\documentation\BuildBot and
> will import is as HTML in a new wiki page for BuildBot
>
> I hope this will help us to get to a fruitful collaboration :)
>
> BTW we are still waiting for something to happen, see
> https://issues.apache.org/jira/browse/INFRA-15785
>
> Jacques
>
>
>> On Sun, Jan 7, 2018 at 5:20 PM,   wrote:
>>>
>>> The Buildbot has detected a new failure on builder
>>> ofbizTrunkFrameworkPlugins while building . Full details are available at:
>>>  https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/10
>>>
>>> Buildbot URL: https://ci.apache.org/
>>>
>>> Buildslave for this Build: lares_ubuntu
>>>
>>> Build Reason: downstream
>>> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820457
>>> Blamelist: jleroux
>>>
>>> BUILD FAILED: failed shell_4
>>>
>>> Sincerely,
>>>   -The Buildbot
>>>
>>>
>>>
>


Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-07 Thread Jacques Le Roux

Le 07/01/2018 à 18:41, Jacques Le Roux a écrit :

A request is of the form
"force build ofbizTrunkFrameworkPlugins"
you put the text you want to appear after this expression, something like
"forces manual build after Buildbot weird 85 errors on labels :-o" 
Forgot to say that with our last config (see INFRA-15394) the ofbizTrunkFrameworkPlugins and ofbizBranch17FrameworkPlugins builders are dependent and 
respectively automatically launched by the ofbizTrunkFramework and ofbizBranch17Framework builders but only on commits.

So if you use an IRC command like
"force build ofbizTrunkFramework" only this builder will be launched not the 
dependent ofbizTrunkFrameworkPlugins

HTH

Jacques



Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-07 Thread Jacques Le Roux

Le 07/01/2018 à 15:44, Taher Alkhateeb a écrit :

I am suspecting this is still a broken build system rather than a
genuine error. Can you confirm?

It's not a "broken build system" but was a transient error as you can see there
https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins


If tests are running okay locally

Yes they are, at least now...


then we still have a faulty build logic.

Nope, it's not a "faulty build logic." just a transient error on build servers

When you see that tests pass locally and not on Buildbot it's most certainly an 
issue with servers.
Those are hard workers and make errors from time to time (which shows that not 
only human make errors)

When something like that happens, I get to IRC (using 
https://webchat.freenode.net)
There using a recognisable username (I use jleroux) I get to the ofbiz channel.
I wait for ofbiz-bot to appear, click on query and then I can make a request in 
the chat line to restart a scheduler.
A request is of the form
"force build ofbizTrunkFrameworkPlugins"
you put the text you want to appear after this expression, something like
"forces manual build after Buildbot weird 85 errors on labels :-o"

I hope this clarify. I'll put a .md file in tools\documentation\BuildBot and 
will import is as HTML in a new wiki page for BuildBot

I hope this will help us to get to a fruitful collaboration :)

BTW we are still waiting for something to happen, see 
https://issues.apache.org/jira/browse/INFRA-15785

Jacques


On Sun, Jan 7, 2018 at 5:20 PM,   wrote:

The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
while building . Full details are available at:
 https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/10

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: lares_ubuntu

Build Reason: downstream
Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820457
Blamelist: jleroux

BUILD FAILED: failed shell_4

Sincerely,
  -The Buildbot







Re: buildbot failure in on ofbizTrunkFrameworkPlugins

2018-01-07 Thread Taher Alkhateeb
I am suspecting this is still a broken build system rather than a
genuine error. Can you confirm? If tests are running okay locally then
we still have a faulty build logic.

On Sun, Jan 7, 2018 at 5:20 PM,   wrote:
> The Buildbot has detected a new failure on builder ofbizTrunkFrameworkPlugins 
> while building . Full details are available at:
> https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins/builds/10
>
> Buildbot URL: https://ci.apache.org/
>
> Buildslave for this Build: lares_ubuntu
>
> Build Reason: downstream
> Build Source Stamp: [branch ofbiz/ofbiz-framework/trunk] 1820457
> Blamelist: jleroux
>
> BUILD FAILED: failed shell_4
>
> Sincerely,
>  -The Buildbot
>
>
>