Continuum

Failing to build project in right order or failing to recognize a svn change in the right order

Details

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

Description

Here's what happened.

The error is because it's finding a class that's been renamed in the "Cargo Core Container API" module. Note that this module is defined to be built before the two modules in error above.

What's also strange is that C shows a lot of modules in error (the red crosses) but if you look in the build results these modules are building fine. I'm attaching a screenshot to this issue.

What can I do more to help debu this? This makes C unusable for me as I consider these 2 emails as false positives. Is there something I don't understand?

Thanks

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Massol added a comment -

What I find strange is that if this were a problem lots of people should be experiencing it but it doesn't seem to be a known problem. Which leads me to believe it might a problem with either Cargo or me but I can't find the solution...

Thanks for any help you bring on this.

Show
Vincent Massol added a comment - What I find strange is that if this were a problem lots of people should be experiencing it but it doesn't seem to be a known problem. Which leads me to believe it might a problem with either Cargo or me but I can't find the solution... Thanks for any help you bring on this.
Hide
Permalink
Vincent Massol added a comment -

As you can see there's no problem with Cargo SVN. This seems to confirms that there's a bug with Continuum or that instance.

Show
Vincent Massol added a comment - As you can see there's no problem with Cargo SVN. This seems to confirms that there's a bug with Continuum or that instance.
Hide
Permalink
Brian Fox added a comment -

I have seen this and it's precisely why I had to remove all modules except the higest parent in each tree and then clear the non-recursive flag. That and it was annoying to get 100 emails if a simple error occured

Show
Brian Fox added a comment - I have seen this and it's precisely why I had to remove all modules except the higest parent in each tree and then clear the non-recursive flag. That and it was annoying to get 100 emails if a simple error occured
Hide
Permalink
Vincent Massol added a comment -

Brian, I've have just done exactly this: removed all modules except the top level one. I hope continuum will be able to work with modules in the near future though as this provides a quicker feedback loop.

Show
Vincent Massol added a comment - Brian, I've have just done exactly this: removed all modules except the top level one. I hope continuum will be able to work with modules in the near future though as this provides a quicker feedback loop.
Hide
Permalink
Jesse McConnell added a comment -

http://www.nabble.com/build-scheduling-issues-tf2592068.html#a7235065

vincent, any feedback you would like to make on that thread?

Show
Jesse McConnell added a comment - http://www.nabble.com/build-scheduling-issues-tf2592068.html#a7235065 vincent, any feedback you would like to make on that thread?
Hide
Permalink
Jesse McConnell added a comment -

emm fixed this a while back I believe

Show
Jesse McConnell added a comment - emm fixed this a while back I believe

People

Vote (0)
Watch (0)

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.