Re: [SUMMARY] 3 ITs permanently fail on Linux / Maven Core

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [SUMMARY] 3 ITs permanently fail on Linux / Maven Core

On Sun, 04 Aug 2019 13:06:31 +0200, Elliotte Rusty Harold  
<[hidden email]> wrote:

> This investigation and resolution of this mystery has been quite
> informative. I suspect there are general principles and lessons here
> about separating infrastructure for different projects that extend
> well beyond Maven itself and probably beyond Jenkins. Containers might
> play a role.

Using containers will isolate some issues, but I prefer to test Maven as  
it is used by its users. Even though I don't have the numbers, I still  
think most use it directly on the OS. The usage of Maven inside a  
container is probably increasing, so it does make sense if such a setup is  
possible with the infra of the ASF.

> Perhaps someone would be interested in more formally publishing a full
> writeup somewhere? Or perhaps delivering a lightning talk on this at
> ApacheCon? This feels quite valuable for general DevOps.

This is indeed an interesting topic where one must understand how all the  
tools work, especially in a shared environment.
AFAIK all Maven related proposals were rejected for ApacheCon Europe.


> On Sat, Aug 3, 2019 at 3:12 PM Robert Scholte <[hidden email]>  
> wrote:
>> Here's a very short summary and conclusion about what happened the last
>> period.
>> Half July some integration tests of Maven started to fail, but not  
>> always
>> (it good happen that a certain JDK would succeed again with the next  
>> run).
>> At that time we only noticed:
>> - it failed only on the Linux nodes of Jenkins.
>> - the failing tests were using MAVEN_OPTS
>> It took quite a while, but in the end Hervé discovered the root cause:
>> - On some nodes there was an unexpected ${user.home}/.m2/.mavenrc file
>> that set the value of MAVEN_OPTS
>> INFRA discovered that it was the incubator-shardingsphere that created
>> this file when building there project.
>> We've provided a PR for this project together with an explanation. This  
>> PR
>> has been accepted and INFRA has removed the .mavenrc files.
>> Over the past weeks a lot of changes has been done to the code for
>> investigation.
>> All changes that were done to change the behavior related to  
>> environments
>> variables and mavenrc file should and will be reverted.
>> Mavens master branch was stable, so to ensure the right things are still
>> tested the need to be restored (some of them did indeed test the
>> MAVEN_OPTS explicitly as issued in its JIRA).
>> In general we don't change ITs, we only extend then and provide a range  
>> to
>> control for which Maven versions the test is valid.
>> Details and discussions can be found on the slack channel.
>> thanks,
>> Robert
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]

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