How is this a problem in 1.7? We don't have a .ompi_ignore in
1.7.4. That is there to prevent mtt failures while I fix some
outstanding bcol issues.
I will clean this up on trunk and add it to the cmr.
On Thu, Feb 06, 2014 at 08:42:27PM -0800, Ralph Castain wrote:
> As many of you will have noticed, I have been struggling most of the evening with breakage on the trunk. This was initiated by adding .ompi_ignore to the coll/ml component, but the root cause of the problem is a blatant disregard for OMPI design rules in the bcol framework. Component-level headers from the coll/ml area have been included in multiple places throughout the bcol framework, making it impossible to separate these two areas.
> Unfortunately, this problem has now been propagated to the 1.7 branch. As release manager, I'm afraid that places me in a difficult position, and I'm going to have to insist that this either is fixed immediately (i.e., in next 24 hours), or I have to rescind/delete that area from the 1.7 branch and release an immediate 1.7.5 (with attendant apologies to the community for the screwup). We will then proceed with our intended plan, minus the bcol code.
> I'd appreciate someone letting me know if this problem (a) can even be fixed, given the degree of cross-connection I see in the bcol code, and (b) if it can, then by when.
> devel mailing list
- application/pgp-signature attachment: stored