|
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):
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. Do you have re-tested it since my changes on fetch groups?
kenney, do you know if this is still a problem after your build queue work?
I can't reproduce it with 1.1
|
||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Task
Closed
Major
stopping continuum when builds are in progress /queued causes duplicates on restart
i think it appears only for project in progress, but it's very strange because the only place in continuum code that call the storage of a project is in AddProject method in DefaultContinuum. This method is called only from web interface.
i think it appears only for project in progress, but it's very strange because the only place in continuum code that call the storage of a project is in AddProject method in DefaultContinuum. This method is called only from web interface.