Howdy,
part2: now ITs got full isolation (from user env that runs them). This
means that ITs are running in their own (dedicated and fully
controlled) $HOME.
The flipside: Maven IT suite (the one in Maven repo) can be run ONLY
with Maven 3.9+ (local repo tail support required).
Which is IMO fine,
Or handle our testing infrastructure randomly changing on us. Whatever it was
seems to have switched back and the ITs work again.
On Sep 8, 2013, at 1:16 AM, Olivier Lamy wrote:
> testitMNG2201(org.apache.maven.it.MavenITmng2201PluginConfigInterpolationTest)
> Time elapsed: 0.603 sec <<< FAIL
testitMNG2201(org.apache.maven.it.MavenITmng2201PluginConfigInterpolationTest)
Time elapsed: 0.603 sec <<< FAILURE!
junit.framework.AssertionFailedError:
expected:
but
was:
AFAICS unit test doesn't handle correctly symlinks.
On 8 September 2013 12:50, Jason van Zyl wrote:
> Olivier,
>
> Not
I'm not sure I ever ran the core IT's in parallel; and I dont think
benjamin did either...?
Kristian
Den 1. sep. 2012 kl. 04:20 skrev Jason van Zyl :
> I rebased the ITs for Maven I have and I notice now that the setup I had now
> fails to run ITs in parallel.
>
> I do a touchstone build on Jav
I'm assuming this message is old and I'm just now seeing it for some
quirk of the email server, but looking at that file it's definitely set
to 1.2-SNAPSHOT.
I haven't modified that file in a long time, but it may have been me
that bumped it to 1.2-SNAPSHOT in the first place. However, I can t
I will setup a standard job to wipe the repo. All these tests needs to
work from scratch on any machine with a clean repo. And figure out
what are install/deploy problems and what are actual bugs.
On 7-Jul-08, at 10:14 PM, Brett Porter wrote:
On 08/07/2008, at 9:49 AM, Jason van Zyl wrote:
On 08/07/2008, at 9:49 AM, Jason van Zyl wrote:
I have the start of all the jobs running in the Hudson Zone @ Apache
and we have the same ITs that were failing yesterday failing on
Solaris:
http://hudson.zones.apache.org/hudson/view/Maven/
Was that because the artifact snapshot had not y
Hi All,
I am just a reader, but I would like to ask everyone who is sending to
this mailing list to pay little bit of attention to what you are sending
here. For instance, email quoted below have about two pages of signatures
and other system information that adds lots of visual noise to the em
On 07/07/2008, at 11:32 PM, Jason van Zyl wrote:
But is that hiding another bug? We are wiping out the artifacts
once a day on Hudson, but everyone seems to be able to run them
locally. So now we're just nuking everything but is that just
hiding a dependency resolution bug? I hate just did
On 7-Jul-08, at 9:17 AM, Brett Porter wrote:
On 07/07/2008, at 11:00 PM, Jason van Zyl wrote:
On 7-Jul-08, at 8:42 AM, Brett Porter wrote:
What does that mean. For 13 days it bubbles and then starts
magically working? Something must have changed.
Yes, I committed a fix for your two f
On 07/07/2008, at 11:00 PM, Jason van Zyl wrote:
On 7-Jul-08, at 8:42 AM, Brett Porter wrote:
What does that mean. For 13 days it bubbles and then starts
magically working? Something must have changed.
Yes, I committed a fix for your two failures, and my two failures,
and a bit more c
On 7-Jul-08, at 8:42 AM, Brett Porter wrote:
What does that mean. For 13 days it bubbles and then starts
magically working? Something must have changed.
Yes, I committed a fix for your two failures, and my two failures,
and a bit more cleanup, which all bubbled through CI eventually and
On 07/07/2008, at 10:37 PM, Jason van Zyl wrote:
On 6-Jul-08, at 11:32 PM, Brett Porter wrote:
Yes, and I thought John had fixed the offending code in Maven
Artifact - and the ITs seem to be picking up those changes. Maybe
there's a further case that needs to be addressed?
Ok, I think
On 6-Jul-08, at 11:32 PM, Brett Porter wrote:
Yes, and I thought John had fixed the offending code in Maven
Artifact - and the ITs seem to be picking up those changes. Maybe
there's a further case that needs to be addressed?
Ok, I think this particular circumstance is fixed by the time it
On 07/07/2008, at 12:45 PM, Brett Porter wrote:
On 07/07/2008, at 5:15 AM, Jason van Zyl wrote:
On 6-Jul-08, at 2:46 PM, Brett Porter wrote:
Fine here, and on vmbuild too.
digester being null happens after a transfer error of some sort -
you might throw in -X to see if it shows somethi
On 07/07/2008, at 5:15 AM, Jason van Zyl wrote:
On 6-Jul-08, at 2:46 PM, Brett Porter wrote:
Fine here, and on vmbuild too.
digester being null happens after a transfer error of some sort -
you might throw in -X to see if it shows something else occuring.
After a transfer error it cal
On 6-Jul-08, at 2:46 PM, Brett Porter wrote:
Fine here, and on vmbuild too.
digester being null happens after a transfer error of some sort -
you might throw in -X to see if it shows something else occuring.
After a transfer error it calls transferStarted( XX )? That seems wrong.
The ot
Fine here, and on vmbuild too.
digester being null happens after a transfer error of some sort - you
might throw in -X to see if it shows something else occuring.
The other curiosity is why it's resolved the project info reports
plugin in both cases?
Cheers,
Brett
On 07/07/2008, at 4:03
18 matches
Mail list logo
