Bugzilla – Full Text Bug Listing
| Summary: | importtargetdefinition doesn't complete in time when running from a .script file | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Stef bolton <stefan.bolton> |
| Component: | Buckminster | Assignee: | buckminster.core-inbox <buckminster.core-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | stefan.bolton |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
I should mention this wasn't occurring until a fourth installation site was added to the feature.target file. |
Build Identifier: 20100917-0705 Running the following commands on the commandline works: - buckminster -data buckminster.workspace importtargetdefinition -A feature.target buckminster -data buckminster.workspace import feature.cquery However, having them run from a script file causes the message "Resetting target platform Buckminster Default TP" to be output and our build then fails. This appears to be a timing issue where the target definition hasn't finished materialising before the cquery is materialised. I can work around this, by importing the target definition twice - this seems to give it enough time to resolve before the cquery is materialised. Reproducible: Always Steps to Reproduce: 1. As detailed above. Run a .script file with an importtargetdefinition command immediately followed by an import command - causes the error. 2. Run the two commands manually and the tp import works correctly.