Bug #2156
Changing rst-converters-python branch to 0.11 from master leads to a DEPLOYMENT-ERROR
Status: | Rejected | Start date: | 01/13/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Moringen | % Done: | 0% | |
Category: | Build System | |||
Target version: | - |
Description
When changing the used rst-converters-python
branch in the distribution file (CSRA) the following error occurs during job-configuration:
1 problem during DEPLOY/PROJECT phase: DEPLOYMENT-ERROR: Error during deployment of #<PROJECT rst-converters-python {100D76DE23}> » #<VERSION rst-converters-python:0.11 {100D774DF3}> » #<JOB rst-converters-python:0.11:toolkit-nightly-nightly {1008F4FCE3}> Caused by: > #<CLOSURE (LAMBDA (&REST ALEXANDRIA.0.DEV::MORE) :IN ALEXANDRIA.0.DEV:RCURRY) {1008B8087B}> does not define a partial order on > (#<JENKINS.API:BUILDER/SHELL find . -mindepth 1 -maxdepth 1 -not -name "python" -exec rm -rf {} \; {1008A6EDE3}> #<JENKINS.API:BUILDER/SHELL PYTHON=python2.7 {1008A6EE03}> > #<JENKINS.API:BUILDER/SHELL rm -rf /vol/csra/releases/trusty/nightly/releases/trusty/nightly/lib/python2.7/site-packages/rstconverters-*.egg {1008A6EE23}>). > Problems: > * #<BUILDER/SHELL find . -mindepth 1 -maxdepth 1 -not -name "python" -exec rm -rf {} \; {1008A6EDE3}> - #<BUILDER/SHELL > rm -rf /vol/csra/releases/trusty/nightly/releases/trusty/nightly/lib/python2.7/site-packages/rstconverters-*.egg > {1008A6EE23}> > * #<BUILDER/SHELL PYTHON=python2.7 {1008A6EE03}> - #<BUILDER/SHELL rm -rf /vol/csra/releases/trusty/nightly/releases/trusty/nightly/lib/python2.7/site-packages/rstconverters-*.egg {1008A6EE23}>
(see this link for more detail)
Some important notes:- the error does not occur with the
rst-converters-cpp
project. The change to 0.11 was without problems - we also changed the prefix during this, but this should actually not be any issue here
- our branch of
rst-proto
(rst-proto-csra
) is still set to master, as we do not have done the branching ourselves yet - however, the job was generated anyways (we don't know if it will build - check this URL soon: here)
- in previous job-configuration runs this error never occured
History
#1 Updated by J. Moringen over 9 years ago
- Status changed from New to Rejected
This is a problem of the current recipe/build-generator combination, not related to Robotics Systems Types.
See http://opensource.cit-ec.de/issues/341 and "Aktueller Stand build-generator" email thread on the citk-dev mailing list.
#2 Updated by N. Köster over 9 years ago
also, there was an error in the prefix:
/vol/csra/releases/trusty/nightly/releases/trusty/nightly/
my bad :(