[ http://jira.codehaus.org/browse/CONTINUUM-641?page=comments#action_62176 ]
Brett Porter commented on CONTINUUM-641: ---------------------------------------- There seems to be a couple of things. I can't find what led to the problem on the one I tried to reproduce it on - it was in fact just the "in progress" one. Steps to reproduce (on ubuntu breezy VMWare machine running on windows): - fresh install - add a bunch of projects, wait for checkout - build all - kill the app (not Ctrl-C, just a normal kill that got trapped by JSW and Continuum shutdown) - restart Continuum - one dupe, building projects does not cause a dupe For cheddar, I got more information yesterday. It's not an addProject call - it seems a problem with JDO when it tries to get the project for building the next time. This might just be that the original database was corrupted, so I'm not really concerned about it. > stopping continuum when builds are in progress /queued causes duplicates on > restart > ----------------------------------------------------------------------------------- > > Key: CONTINUUM-641 > URL: http://jira.codehaus.org/browse/CONTINUUM-641 > Project: Continuum > Type: Task > Components: Core system > Versions: 1.0.3 > Reporter: Brett Porter > Priority: Blocker > Fix For: 1.0.3 > > > I was able to reliably reproduce this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
