is there a way we can access to machine/workspace to reproduce this...
those tests most likely have threading issues but it's hard to debug
when they pass...
jerome
On Feb 29, 2008, at 12:12 PM, Marina Vatkina wrote:
> Kedar Mhaswade wrote:
>> Marina Vatkina wrote:
>>> My only solution so far was to remove the test.
>>>
>>> -marina
>>>
>>> Shing Wai Chan wrote:
>>>
>>>> I see the following failure from time to time. It may be gone if
>>>> you run mvn install again.
>>>> It would be a good idea to check we have this.
>>>>
>>>> Mitesh Meswani wrote:
>>>>
>>>>> If you are stuck because of this, you can skip the tests by
>>>>> using "mvn -Dmavan.test.skip=true install"
>> Marina, I am sorry, you've been having problems. I will investigate
>> why this fails intermittently.
>
> It fails all the time :(.
>> In order to not get impacted because of problems with other portions
>> of the source tree, it may be possible to just check out the portion
>> that you actively develop ...
>> If you develop module A, B and C, isn't it better to check out only
>> those, *most of the time* rather than checking out entire V3 code-
>> base?
>> (I thought that's what modular system is about).
>
> It's now so fast to build all, and I need the changes in at least 3
> modules, so it was easier to update and build all.
>
> Also, I never know where the pieces are nowadays, so it's convinient
> for the search ;).
>
> thanks,
> -marina
>
>> - Kedar
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>