issue 557.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

issue 557.

Nord, James-2
Hi all,
 
Just updated to 1.133 from 1.132 as I use aggregator poms in the native m2 build, however I can't see the option to enable the new mode of execution.
 
When I click advanced I just get the same MAVEN_OPTS box and I was expecting something new like a checkbox or something.
Same happens when I create a new project - I don't see the option.
 
Tomcat has been restarted with the old war and unpacked data deleted and I have performed a reload in IE browser with no effect?
 
Am I missing something (apart from the coffee that I haven't had yet)?
 
 
Well just before I hit send I noticed the other "Advanced..." button under Advanced project options.  So I guess this is a heads-up to anyone else that is lacking caffeine that the Advanced button you press to change the Maven build style isn't with the rest of the Maven options. 
 
Regards,
 
    /James
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the [hidden email] and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: issue 557.

Nord, James-2
With the new maven building of aggregated projects if a library fails to build due to failing unit tests the whole build stops.  With the old method the maven build was marked as successful if just tests failed so other builds could complete.
 
Is this the intended behaviour of the new maven building?
 
Regards,
 
    /James


From: Nord, James [mailto:[hidden email]]
Sent: 30 August 2007 09:33
To: [hidden email]
Subject: issue 557.

Hi all,
 
Just updated to 1.133 from 1.132 as I use aggregator poms in the native m2 build, however I can't see the option to enable the new mode of execution.
 
When I click advanced I just get the same MAVEN_OPTS box and I was expecting something new like a checkbox or something.
Same happens when I create a new project - I don't see the option.
 
Tomcat has been restarted with the old war and unpacked data deleted and I have performed a reload in IE browser with no effect?
 
Am I missing something (apart from the coffee that I haven't had yet)?
 
 
Well just before I hit send I noticed the other "Advanced..." button under Advanced project options.  So I guess this is a heads-up to anyone else that is lacking caffeine that the Advanced button you press to change the Maven build style isn't with the rest of the Maven options. 
 
Regards,
 
    /James
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the [hidden email] and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the [hidden email] and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: issue 557.

nicolas de loof-2
You may configure maven2 build to run with --fail-at-end flag
Not tested myself, but this would allow the build to go deeper and to be marked as failed.

Nico.

2007/8/30, Nord, James <[hidden email]>:
With the new maven building of aggregated projects if a library fails to build due to failing unit tests the whole build stops.  With the old method the maven build was marked as successful if just tests failed so other builds could complete.
 
Is this the intended behaviour of the new maven building?
 
Regards,
 
    /James


From: Nord, James [mailto:[hidden email]]
Sent: 30 August 2007 09:33
To: [hidden email]
Subject: issue 557.

Hi all,
 
Just updated to 1.133 from 1.132 as I use aggregator poms in the native m2 build, however I can't see the option to enable the new mode of execution.
 
When I click advanced I just get the same MAVEN_OPTS box and I was expecting something new like a checkbox or something.
Same happens when I create a new project - I don't see the option.
 
Tomcat has been restarted with the old war and unpacked data deleted and I have performed a reload in IE browser with no effect?
 
Am I missing something (apart from the coffee that I haven't had yet)?
 
 
Well just before I hit send I noticed the other "Advanced..." button under Advanced project options.  So I guess this is a heads-up to anyone else that is lacking caffeine that the Advanced button you press to change the Maven build style isn't with the rest of the Maven options. 
 
Regards,
 
    /James
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the [hidden email] and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the [hidden email] and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: issue 557.

Nord, James-2
I've managed to work around this by passing -Dmaven.test.failure.ignore=true to maven.
 
However I've noticed that the aggregated test results are now missing from the project page.
 
Also the project dependencies is very wiered and the check relationship is always failing with errors such as "No such project 'com.nds.tvp.scg:Config'"
 
/James

 
You may configure maven2 build to run with --fail-at-end flag
Not tested myself, but this would allow the build to go deeper and to be marked as failed.

Nico.

2007/8/30, Nord, James
With the new maven building of aggregated projects if a library fails to build due to failing unit tests the whole build stops.  With the old method the maven build was marked as successful if just tests failed so other builds could complete.
 
Is this the intended behaviour of the new maven building?
 
Regards,
 
    /James



 
Hi all,
 
Just updated to 1.133 from 1.132 as I use aggregator poms in the native m2 build, however I can't see the option to enable the new mode of execution.
 
When I click advanced I just get the same MAVEN_OPTS box and I was expecting something new like a checkbox or something.
Same happens when I create a new project - I don't see the option.
 
Tomcat has been restarted with the old war and unpacked data deleted and I have performed a reload in IE browser with no effect?
 
Am I missing something (apart from the coffee that I haven't had yet)?
 
 
Well just before I hit send I noticed the other "Advanced..." button under Advanced project options.  So I guess this is a heads-up to anyone else that is lacking caffeine that the Advanced button you press to change the Maven build style isn't with the rest of the Maven options. 
 
Regards,
 
    /James
 
 
 
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the [hidden email] and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**********************************************************************************************************

blue.gif (1K) Download Attachment
fingerprint.gif (822 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: issue 557.

Kohsuke Kawaguchi
Administrator
In reply to this post by nicolas de loof-2
nicolas de loof wrote:
> You may configure maven2 build to run with --fail-at-end flag
> Not tested myself, but this would allow the build to go deeper and to be
> marked as failed.

I don't have any experience using it, but what happens if a build really
fails? Like a compiler error? Does other modules that depend on the
failed module get skipped? Or will they try to run and fail anyway?

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: issue 557.

Kohsuke Kawaguchi
Administrator
In reply to this post by Nord, James-2

No, I think this is just a poor design. I didn't realize that I already
had an "advanced..." button under Maven. I'll move it over there. This
change will be in 1.134.

Nord, James wrote:

> Hi all,
>  
> Just updated to 1.133 from 1.132 as I use aggregator poms in the native
> m2 build, however I can't see the option to enable the new mode of
> execution.
>  
> When I click advanced I just get the same MAVEN_OPTS box and I was
> expecting something new like a checkbox or something.
> Same happens when I create a new project - I don't see the option.
>  
> Tomcat has been restarted with the old war and unpacked data deleted and
> I have performed a reload in IE browser with no effect?
>  
> Am I missing something (apart from the coffee that I haven't had yet)?
>  
>  
> Well just before I hit send I noticed the other "Advanced..." button
> under Advanced project options.  So I guess this is a heads-up to anyone
> else that is lacking caffeine that the Advanced button you press to
> change the Maven build style isn't with the rest of the Maven options.  



--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: issue 557.

Kohsuke Kawaguchi
Administrator
In reply to this post by Nord, James-2
Nord, James wrote:
> With the new maven building of aggregated projects if a library fails to
> build due to failing unit tests the whole build stops.  With the old
> method the maven build was marked as successful if just tests failed so
> other builds could complete.
>  
> Is this the intended behaviour of the new maven building?

No, I intend to fix this. It looks like I just need to run surefire with
  testFailureIgnore=true.

I committed a change toward 1.134, but I need to verify the fix. If
anyone can try the snapshot to verify the fix, that would be great.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: issue 557.

Kohsuke Kawaguchi
Administrator
In reply to this post by Nord, James-2
Nord, James wrote:
> I've managed to work around this by passing
> -Dmaven.test.failure.ignore=true to maven.
>  
> However I've noticed that the aggregated test results are now missing
> from the project page.

I noticed this too, but it seems like this has been an issue all along.

>  
> Also the project dependencies is very wiered and the check relationship
> is always failing with errors such as "No such project
> 'com.nds.tvp.scg:Config'"

Same as above. Could you please file issues for them?

I was hoping to have time to fix them right now, but my time is running
up right now and I don't want to forget.

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Re: issue 557.

Nord, James-2
> Nord, James wrote:
> > I've managed to work around this by passing
> > -Dmaven.test.failure.ignore=true to maven.
> >  
> > However I've noticed that the aggregated test results are
> now missing
> > from the project page.
>
> I noticed this too, but it seems like this has been an issue
> all along.


This was working for me - if I go to a project that has not been built
since the upgrade I can see the graph :-)

I've never had them on the project build resuilt page though...
 i.e http://scg-hudson/job/bob used to show a graph but doesn't since
the upgrade and http://scg-hudson/job/bob/9/ never showed a graph.

Issue 775 created.


> >  
> > Also the project dependencies is very wiered and the check
> > relationship is always failing with errors such as "No such project
> > 'com.nds.tvp.scg:Config'"
>
> Same as above. Could you please file issues for them?
>
> I was hoping to have time to fix them right now, but my time
> is running up right now and I don't want to forget.


Issue 774 created.

/James
*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only.  Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited.  If you have received this message in error, please immediately notify the [hidden email] and destroy the original message.  Messages sent to and from NDS may be monitored.  NDS cannot guarantee any message delivery method is secure or error-free.  Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.  We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission.  You should carry out your own virus checks before opening any attachment.  Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**********************************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Re: issue 557.

Nord, James-2
In reply to this post by Kohsuke Kawaguchi
 

> Nord, James wrote:
> > With the new maven building of aggregated projects if a
> library fails
> > to build due to failing unit tests the whole build stops.  With the
> > old method the maven build was marked as successful if just tests
> > failed so other builds could complete.
> >  
> > Is this the intended behaviour of the new maven building?
>
> No, I intend to fix this. It looks like I just need to run
> surefire with
>   testFailureIgnore=true.

> I committed a change toward 1.134, but I need to verify the
> fix. If anyone can try the snapshot to verify the fix, that
> would be great.



Using Hudson ver. 1.134-SNAPSHOT (private-08/30/2007 08:55-hudson)

Build fails at first opportunity.
        [INFO] Scanning for projects...
        [INFO] Reactor build order:
        [INFO]   CA
        [INFO]   xECM
        [INFO]   xECMGenerators
<SNIP>
        [INFO] Surefire report directory:
c:\hudson\jobs\CA\workspace\trunk\xECM\target\surefire-reports
       
        -------------------------------------------------------
        T E S T S
        -------------------------------------------------------
        Running com.nds.tvp.scg.ca.VECMTest
        Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.172 sec
        Running com.nds.tvp.scg.ca.VECMMessageTest
        Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
0.11 sec <<< FAILURE!
        Running com.nds.tvp.scg.ca.OOBECMTest
        Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
0.031 sec
       
        Results :
       
        Tests in error:
                testParsingValid(com.nds.tvp.scg.ca.VECMMessageTest)
       
        Tests run: 4, Failures: 0, Errors: 1, Skipped: 0
       
        [HUDSON] Recording test results
        [HUDSON] Archiving
c:\hudson\jobs\CA\workspace\trunk\xECM\pom.xml
        [INFO]
------------------------------------------------------------------------
        [ERROR] BUILD FAILURE
        [INFO]
------------------------------------------------------------------------
        [INFO] There are test failures.
        [INFO]
------------------------------------------------------------------------
        [INFO] For more information, run Maven with the -e switch
        [INFO]
------------------------------------------------------------------------
        [INFO] Total time: 32 seconds
        [INFO] Finished at: Thu Aug 30 17:40:58 BST 2007
        [INFO] Final Memory: 12M/25M
        [INFO]
------------------------------------------------------------------------
        Maven failed with error.
        finished: SUCCESS


The status is different as well though.

Old builds (parallel) used to be
        [INFO] Final Memory: 7M/48M
        [INFO]
------------------------------------------------------------------------
        Maven failed with error.
        Sending e-mails to: [hidden email] [hidden email]
[hidden email]
--> finished: UNSTABLE


Created issue 776 for this.

Running from the command line I get different output at the end:
        [INFO]
------------------------------------------------------------------------
----
        [INFO] SKIPPING xECMGenerators
        [INFO]    task-segment: [install]
        [INFO] This project has been banned from further executions due
to previous failures.
        [INFO]
------------------------------------------------------------------------
----
        [INFO]
        [INFO]
        [INFO]
------------------------------------------------------------------------
        [INFO] Reactor Summary:
        [INFO]
------------------------------------------------------------------------
        [INFO] CA ....................................................
SUCCESS [2.281s]
        [INFO] xECM ..................................................
FAILED [0.860s]
        [INFO] xECMGenerators ........................................
SKIPPED (dependency build failed or was skipped)
        [INFO]
------------------------------------------------------------------------
        [INFO] Error for project: xECM (during install)
        [INFO]
------------------------------------------------------------------------
        [INFO] There are test failures.
        [INFO]
------------------------------------------------------------------------
        [INFO] For more information, run Maven with the -e switch
        [INFO]
------------------------------------------------------------------------
        [INFO] BUILD ERRORS
        [INFO]
------------------------------------------------------------------------
        [INFO] Total time: 3 seconds
        [INFO] Finished at: Thu Aug 30 12:59:37 BST 2007
        [INFO] Final Memory: 11M/21M
        [INFO]
------------------------------------------------------------------------

If this is fixed to work I don't think it will do what I'm expecting.
As the sub module (b) which depends on the module (a) will not be build
as the module (a) is not available for module (b) even if a previous
build has succesfully installed a jar in the repository.
This makes sense for a release build but not for a snapshot CI build -
it would break all sub modules from being built until a unit test is
fixed,  the bahaviour I am expecting is the behaviour of the parallel
builds but without the large rebuild cycle which caused certain modules
to be built 2 or 3 times for a single build.

Regards,

        /James

/james

*********************************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only.  Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited.  If you have received this message in error, please immediately notify the [hidden email] and destroy the original message.  Messages sent to and from NDS may be monitored.  NDS cannot guarantee any message delivery method is secure or error-free.  Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.  We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission.  You should carry out your own virus checks before opening any attachment.  Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.

To protect the environment please do not print this e-mail unless necessary.

NDS Limited Registered office: One Heathrow Boulevard, 286 Bath Road, West Drayton, Middlesex, UB7 0DQ, United Kingdom. A company registered in England and Wales  Registered no. 3080780   VAT no. GB 603 8808 40-00
**********************************************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...