Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 277161 - [planner] Reenable MissingOptionalWithDependencies3
Summary: [planner] Reenable MissingOptionalWithDependencies3
Status: RESOLVED WONTFIX
Alias: None
Product: Equinox
Classification: Eclipse Project
Component: p2 (show other bugs)
Version: 3.5   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: P2 Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 276133
Blocks:
  Show dependency tree
 
Reported: 2009-05-20 11:56 EDT by Pascal Rapicault CLA
Modified: 2020-02-20 03:55 EST (History)
8 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2009-05-20 11:56:31 EDT
The fix for bug #276133 introduced an intermittent failure of test MissingOptionalWithDependencies3.
Daniel explains the intermittent failure in the following way

Here is the explanation why some of us pass the test an others do not.

There are too equally good solutions according to the optimization function
(with a value of -7):

Abs_B 1.0.0,A 1.0.0,D 1.0.0,C 2.0.0,Noop_D 1.0.0,1242834377753
0.0.0.1242834377753

B 1.0.0,A 1.0.0,Noop_B 1.0.0,D 1.0.0,Abs_D 1.0.0,C 2.0.0,1242834377753
0.0.0.1242834377753

It is important to note that the rewards are given on Abs_X variables and
penalties are given on Noop_X variables.

Since the two solutions have the same number of Abs_ variables and Noop_X
variables, they are equivalent to the solver.

The one that comes first depend on the order in which the constraints are
entered in the solver.

Since the order of the IUs depends basically on their address in memory, you
can understand that such order might change depending on the VM or the
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:31:48 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 2 Ed Merks CLA 2020-02-20 03:55:51 EST
I'll assume this issue is no longer current.