Re: Jenkins build is unstable: moose-latest-dev #891

50 failed tests.
Since I am familiar with Mondrian, I checked some of the failed tests of it.
Most of the error happens because of some collection comparison. Is it due to the last change of the collection hierarchy? Camillo?

The sunit integration in Nautilus really need some work. The images easily hangs. Apparently the tests are run in the background or something. Nor sure whether this is necessary. If you have 10 failed tests, then you end up with 10 opened debuggers.

Cheers,
Alexandre


On 17 Mar 2012, at 17:52, [hidden email] wrote:

> See <http://hudson.moosetechnology.org/job/moose-latest-dev/891/>
>
>

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

On Mar 18, 2012, at 7:40 PM, Alexandre Bergel wrote:

> 50 failed tests.
> Since I am familiar with Mondrian, I checked some of the failed tests of it.
> Most of the error happens because of some collection comparison. Is it due to the last change of the collection hierarchy? Camillo?

Probably.
Can you have a look and let us know.
I looked at the change of union: and I like it because you can union: more than set.

> The sunit integration in Nautilus really need some work. The images easily hangs.

Do you have situation that we can repeat because the images easily hangs has no information to make progress.

> Apparently the tests are run in the background or something. Nor sure whether this is necessary.
This is to avoid to block the system while running your tests.

> If you have 10 failed tests, then you end up with 10 opened debuggers.




_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

>> The sunit integration in Nautilus really need some work. The images easily hangs.
>
> Do you have situation that we can repeat because the images easily hangs has no information to make progress.

Not really because the imaged hanged. I run the test of Mondrian, many debugger got opened, and it hanged.

>> Apparently the tests are run in the background or something. Nor sure whether this is necessary.
> This is to avoid to block the system while running your tests.

I think that making such a feature is really difficult. It does not simply consist in running the test in the background.
Currently, tests are slower to execute (because they are run in the background), and Nautilus seems a bit shaky with all the update in its columns. Not sure why. Maybe because I have run some tests that create and deletes classes and methods. Simply having a progress bar with a X to click on to interrupt the test execution is something that I would personally appreciate. Right now, I prefer the test runner to run them.

Cheers,
Alexandre

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev