Bugzilla – Full Text Bug Listing
| Summary: | Validation error message: missing information | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] CBI | Reporter: | Miles Daffin <miles.daffin> | ||||||
| Component: | CBI p2 Repository Aggregator | Assignee: | Project Inbox <b3.aggregator-inbox> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | thomas | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Bug Depends on: | 352530 | ||||||||
| Bug Blocks: | |||||||||
| Attachments: |
|
||||||||
Updating to blocker since I cannot easily debug current set of builds without this information. In some cases there is no type 3 hierarchy information at all (see BUG352237 for information types). We just get validation errors with types 1, 2 and 4. The attached model (issue01.b3aggr) fails validation under configuration linux,gtk,x86. The error message consistently has no hierarchy info. Created attachment 199825 [details]
Validation fails with conflicts but no hierarchical information in error message.
Fixed in rev. 1533. Confirmed fixed for the model in attachment 199825 [details], which has 3 conflicting versions of the same bundle. We now have 3 model hierarchies so we can see where each conflicting version of the bundle comes from. However, in some other models, we still only have a maximum of 2 hierarchies irrespective of the number of reported conflicts. See attachment.
Created attachment 199924 [details]
Model with 4 conflicts but only 2 diagnostic hierarchies.
When analyzing this I found that the reason for the lack of hierarchies is that p2 only spits out detailed explanations for two branches of the four branches. I'm reporting this as a bug in p2. From the chat on BUG352530 it seems like this may not be fixed by P2. The workaround for now, for cases where more than 2 conflicting items are found, may be to note the hierarchies, disable stuff and re-validate. Not ideal though. (In reply to comment #8) > From the chat on BUG352530 it seems like this may not be fixed by P2. The > workaround for now, for cases where more than 2 conflicting items are found, > may be to note the hierarchies, disable stuff and re-validate. Not ideal > though. I agree it's not ideal, but that seems to be the only option. I'm closing this as a WONTFIX. I don't understand why the model in attachment 199825 [details] has one hierarchy for each of the 3 conflicting IUs. In this case P2 would seem to be providing information for all branches, not just 2. Why is this?
There are actually just two branches but one of them contains a patch. The patch itself reveals a third branch so b3 is able to report this using an additional piece of logic. . [Bookkeeping change only. Moving bugs to the new "home" of aggregator, CBI. Made no changes to assignee's for closed bugs, even though some were old inbox.] |
The validation error reporting was recently improved to help the user understand where in the model errors were coming from by formatting the information in a hierarchical manner reflecting the structure of the model. I am consistently seeing missing information when reporting conflicts in the aggregation. A maximum of 2 diagnostic hierarchies are reported even if the number of conflicting IUs exceeds 2. For example: ---- Problems while verifying configuration: win32,win32,x86 Only one of the following can be installed at once: Scala IDE for Eclipse 2.0.0.beta08-28-201107121559-7d78460 (org.scala-ide.sdt.feature.feature.jar 2.0.0.beta08-28-201107121559-7d78460) Scala IDE for Eclipse 2.0.0.beta08-29-201107121555-7d78460 (org.scala-ide.sdt.feature.feature.jar 2.0.0.beta08-29-201107121555-7d78460) Scala IDE for Eclipse 2.0.0.nightly-29-201107150011-6914a14 (org.scala-ide.sdt.feature.feature.jar 2.0.0.nightly-29-201107150011-6914a14) org.scala-ide.sdt.feature.feature.jar 2.0.0.beta08-28-201107121559-7d78460 is required by: Contribution(Scala IDE 2.8 Beta) MappedRepository(http://download.scala-ide.org/releases-28/2.0.0-beta/) Feature(org.scala-ide.sdt.feature.feature.group [2.0.0.beta08-28,2.0.0.beta08-29)) org.scala-ide.sdt.feature.feature.jar 2.0.0.nightly-29-201107150011-6914a14 is required by: Contribution(Scala IDE 2.9 Nightly) MappedRepository(http://download.scala-ide.org/nightly-update-wip-experiment-2.9.0-1) Feature(org.scala-ide.sdt.feature.feature.group 2.0.0.nightly) ----