Re: Random unit test fail during build
Use your local archiva as a mirror of central :-). Start archiva. In ~/.m2/settings.xml mirrors mirror namearchiva/name mirrorOfcentral/mirrorOf idarchiva-mirror/id urlhttp://localhost:9091/archiva/repository/internal//url /mirror /mirrors and build a project using an empty repo: add -Dmaven.repo.local=path to an empty repo this will populate your archiva instance. 2012/3/1 Eric Barboni barb...@irit.fr: Just a question how to have some artifact inside the new UI to test? -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : jeudi 1 mars 2012 12:47 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/3/1 Eric Barboni barb...@irit.fr: Yep not so much failure. Cool :-) I have implemented some filtering on search. Have a look :-) Don't miss -U I have changed few things in redback too. I move from jdk7.0 to jdk7.3 but they are still random test failure. Is Jenkins able to build only one artifact for example archiva-scheduler-repository (which fail random) and do a lots of clean build to see if at least on fail :p ? Something like checkout + 100 * mvn clean install -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mercredi 29 février 2012 18:26 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/29 Eric Barboni barb...@irit.fr: Well I think I found one more difficult to investigate in ArchivaRepositoryScanningTaskExecutor :p. I will take a look. Weird you have so much unit failures. Is there a web site where current svn trunk reports (surefire,...) are generated ? nope :-) You have Jenkins which execute builds on various os/jdk here: https://builds.apache.org/view/A-F/view/Archiva/ and not so much failures. -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mercredi 29 février 2012 16:17 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/29 Eric Barboni barb...@irit.fr: Sorry for the too local patch but was not capable of doing that for unknown reason. Unclear what the top repo is. Seems to work in all/archiva will do that for next one. As I will have other test failing cause ordering I want to know if issue https://jira.codehaus.org/browse/MRM-1609 can be reopen a rename as something more generic to store the faulty tests ? reopened. I can open another issue otherwise. -Message d'origine- De : Eric Barboni [mailto:barb...@irit.fr] Envoyé : mercredi 29 février 2012 12:11 À : dev@archiva.apache.org Objet : RE: Random unit test fail during build For the one of the test see issue https://jira.codehaus.org/browse/MRM-1609 -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mardi 28 février 2012 19:23 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/28 Eric Barboni barb...@irit.fr: I have limited knowledge of surefire so not sure if I am right Seems to me that runOrder=alphabetical is only for class ordering and not for method ordering. org.apache.maven.surefire.util.DefaultRunOrderCalcultator.java in surefire-api correct ! So I'm puzzled with your issue. :-( I try to run new UI with modifying template to see if it works even with test unit not working. Yup no problem you can still run the webapp Seems I can try to propose the patch for browser part (in a close future). (will write an enhancement issue to keep trace) Good !!! and Thanks ! Eric -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mardi 28 février 2012 15:00 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/28 Eric Barboni barb...@irit.fr: I log some info during test on Archiva Base :: Repository Interface Layer It seems that the two following tests are executed in random order. public void testGatherSnapshotVersionsA() public void testGatherSnapshotVersionsAWithProxies() If testGatherSnapshotVersionsA before testGatherSnapshotVersionsAWithProxies Test run OK But testGatherSnapshotVersionsAWithProxies before testGatherSnapshotVersionsA leads to 1.0-alpha-11-20070315.033030-10 present on the test repository and messing the test. weird as surefire is configured to runOrder=alphabetical -- On the UI (Long and not easy to explain only by text) Cannot yet help in coding. Not fluent in the framework yet. I like the idea about separate browsing vs search with query parameters (I'm currently working on the search I hope to have finish this week) BTW the autocomplete/filtering on browsing looks to be a nice idea (something like http://www.screencast.com/t/01FIwaVTr ? ) (I have just committed that) Looks cool Some other idea to have in the new UI -- browser with more complete list (list of full path group + -- artifact + version) with filtering according to current search quick
Re: Random unit test fail during build
something you can do to have more results in the search: go to remote repositories mngt screen and schedule a remote index download. (can take long :-) ) 2012/3/1 Olivier Lamy ol...@apache.org: Use your local archiva as a mirror of central :-). Start archiva. In ~/.m2/settings.xml mirrors mirror namearchiva/name mirrorOfcentral/mirrorOf idarchiva-mirror/id urlhttp://localhost:9091/archiva/repository/internal//url /mirror /mirrors and build a project using an empty repo: add -Dmaven.repo.local=path to an empty repo this will populate your archiva instance. 2012/3/1 Eric Barboni barb...@irit.fr: Just a question how to have some artifact inside the new UI to test? -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : jeudi 1 mars 2012 12:47 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/3/1 Eric Barboni barb...@irit.fr: Yep not so much failure. Cool :-) I have implemented some filtering on search. Have a look :-) Don't miss -U I have changed few things in redback too. I move from jdk7.0 to jdk7.3 but they are still random test failure. Is Jenkins able to build only one artifact for example archiva-scheduler-repository (which fail random) and do a lots of clean build to see if at least on fail :p ? Something like checkout + 100 * mvn clean install -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mercredi 29 février 2012 18:26 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/29 Eric Barboni barb...@irit.fr: Well I think I found one more difficult to investigate in ArchivaRepositoryScanningTaskExecutor :p. I will take a look. Weird you have so much unit failures. Is there a web site where current svn trunk reports (surefire,...) are generated ? nope :-) You have Jenkins which execute builds on various os/jdk here: https://builds.apache.org/view/A-F/view/Archiva/ and not so much failures. -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mercredi 29 février 2012 16:17 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/29 Eric Barboni barb...@irit.fr: Sorry for the too local patch but was not capable of doing that for unknown reason. Unclear what the top repo is. Seems to work in all/archiva will do that for next one. As I will have other test failing cause ordering I want to know if issue https://jira.codehaus.org/browse/MRM-1609 can be reopen a rename as something more generic to store the faulty tests ? reopened. I can open another issue otherwise. -Message d'origine- De : Eric Barboni [mailto:barb...@irit.fr] Envoyé : mercredi 29 février 2012 12:11 À : dev@archiva.apache.org Objet : RE: Random unit test fail during build For the one of the test see issue https://jira.codehaus.org/browse/MRM-1609 -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mardi 28 février 2012 19:23 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/28 Eric Barboni barb...@irit.fr: I have limited knowledge of surefire so not sure if I am right Seems to me that runOrder=alphabetical is only for class ordering and not for method ordering. org.apache.maven.surefire.util.DefaultRunOrderCalcultator.java in surefire-api correct ! So I'm puzzled with your issue. :-( I try to run new UI with modifying template to see if it works even with test unit not working. Yup no problem you can still run the webapp Seems I can try to propose the patch for browser part (in a close future). (will write an enhancement issue to keep trace) Good !!! and Thanks ! Eric -Message d'origine- De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mardi 28 février 2012 15:00 À : dev@archiva.apache.org Objet : Re: Random unit test fail during build 2012/2/28 Eric Barboni barb...@irit.fr: I log some info during test on Archiva Base :: Repository Interface Layer It seems that the two following tests are executed in random order. public void testGatherSnapshotVersionsA() public void testGatherSnapshotVersionsAWithProxies() If testGatherSnapshotVersionsA before testGatherSnapshotVersionsAWithProxies Test run OK But testGatherSnapshotVersionsAWithProxies before testGatherSnapshotVersionsA leads to 1.0-alpha-11-20070315.033030-10 present on the test repository and messing the test. weird as surefire is configured to runOrder=alphabetical -- On the UI (Long and not easy to explain only by text) Cannot yet help in coding. Not fluent in the framework yet. I like the idea about separate browsing vs search with query parameters (I'm currently working on the search I hope to have finish this week) BTW the autocomplete/filtering on browsing looks to be a nice idea (something like http://www.screencast.com/t/01FIwaVTr ? ) (I have just
