Because when it fails the build, we cannot run the Jenkins builds with IBM J9. 
The JDK is randomly configured/choosen and IBM J9 was (is) also used. But I 
disabled it a few weeks ago, because of the crashes and miscompiled code. I 
think this is fixed now – Mike? If I reenable the IBM J9 1.6 and 1.7 on 
Policeman Jenkins (which I really should do), then it would fail the build, 
because IBM’s Javadocs are formatted in a way that the Python linter does not 
understand (as far as I remember they were not broken, but *different*).

 

Uwe

 

-----

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

 <http://www.thetaphi.de/> http://www.thetaphi.de

eMail: [email protected]

 

From: Shai Erera [mailto:[email protected]] 
Sent: Thursday, February 07, 2013 10:41 PM
To: [email protected]
Subject: Re: documentation-lint and IBM J9

 

I see, but is it possible to FAIL the build in that case? I ran with Oracle's 
1.6.0 and it was ok

Shai

 

On Thu, Feb 7, 2013 at 11:39 PM, Uwe Schindler <[email protected]> wrote:

We ran the llinter with IBM J9 on the Policeman Jenkins server, but the 
generated Javadocs were full of borken links and invalid HTML. So it looks like 
the Javadoc generator of IBM J9 is not compatible with the python checker.

 

This is why it is disabled.

 

-----

Uwe Schindler

H.-H.-Meier-Allee 63, D-28213 Bremen

http://www.thetaphi.de <http://www.thetaphi.de/> 

eMail: [email protected]

 

From: Shai Erera [mailto:[email protected]] 
Sent: Thursday, February 07, 2013 10:30 PM
To: [email protected]
Subject: documentation-lint and IBM J9

 

Hi

I ran 'precommit' and noticed in the end a WARN message that documentation-lint 
doesn't work w/ J9 1.6.0.

While I'm interested to know why (and whether it's just 1.6), can we make the 
build fail in that case? I think that some of my recent Jenkins build failures 
were related to it -- I ran precommit, but just didn't notice the WARN message 
- I only looked at BUILD SUCCESSFUL.

I don't mind if the build fails as early as precommit starts .. just to make 
sure whoever runs it, works w/ a supported JVM.

Is it possible?

Shai

 

Reply via email to