Continuum

stopping continuum when builds are in progress /queued causes duplicates on restart

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.3
  • Fix Version/s: 1.1-alpha-2
  • Component/s: Core system
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

I was able to reliably reproduce this.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Venisse added a comment -

I can't reproduce it

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.

Show
Emmanuel Venisse added a comment - I can't reproduce it 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.
Hide
Permalink
Brett Porter added a comment -

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.

Show
Brett Porter added a comment - 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.
Hide
Permalink
Emmanuel Venisse added a comment -

Do you have re-tested it since my changes on fetch groups?

Show
Emmanuel Venisse added a comment - Do you have re-tested it since my changes on fetch groups?
Hide
Permalink
Brett Porter added a comment -

yep, still reproducible

Show
Brett Porter added a comment - yep, still reproducible
Hide
Permalink
Jesse McConnell added a comment -

kenney, do you know if this is still a problem after your build queue work?

Show
Jesse McConnell added a comment - kenney, do you know if this is still a problem after your build queue work?
Hide
Permalink
Emmanuel Venisse added a comment -

I can't reproduce it with 1.1

Show
Emmanuel Venisse added a comment - I can't reproduce it with 1.1

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.