On Sep 17, 2014, at 12:39 PM, Andrey Semashev
There were a lot of discussions about MPL recently, and I created a few pull requests to address issues:
I’d like to revert the MPL PR that caused our testing problems, and the one Edward just applied. It was wrong of me to commit the PR without any testing. There’s been some list discussion but my overall concern is that we can’t clearly explain why some develop testers are broken and others are working okay. The commit completely broke Darwin, Debian, FreeBSD, QNX and Windows. But what’s really worrying is that some RHEL testers are still merrily cycling while other RHEL testers are broken. Same for Ubuntu, some are cycling okay while some are broken. I think it’s too risky to apply a patch when we, honestly I, don’t understand why this is happening. While we could apply Andrey’s PR (below) I’m afraid that may mask real underlying problems that we may not find out about until this hits master, or worse, users. I’ll work with Andrey to get the MPL changes applied, perhaps in smaller PRs. Please let me know if you have concerns. — Noel
https://github.com/boostorg/boost/pull/39
Invoke 'headers' target before building testing tools. Note that several testers are currently failing to run because of this problem. Since this affects the testing process, I'd appreciate if someone familiar with it could take a look.
https://github.com/boostorg/boost/pull/38
Add MPL.Core tests to the test report. These tests are currently not run by testers.
https://github.com/boostorg/mpl/pull/12
Move a misplaced header from MPL to MPL.Core to resolve circular dependency between the two.
I believe the first PR is especially critical. Could someone with permissions merge these?
Thanks.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost