Hey all, I was wondering if there was any way to query for the Last Known Good Revision of the Boost trunk? It would be great if there was a file or something on the website that had the revision number of the latest build to compile cleanly and pass all tests, either for all platforms, or one file for each platform. For an example of this in practice elsewhere, see the Chromium project: https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#... <https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#TOC-LKGR> Thanks.
On 3/18/2011 11:51 AM, Joshua Boyce wrote:
Hey all, I was wondering if there was any way to query for the Last Known Good Revision of the Boost trunk? It would be great if there was a file or something on the website that had the revision number of the latest build to compile cleanly and pass all tests, either for all platforms, or one file for each platform.
You're going to be disappointed. There is no such file. Firstly, trunk is the wild west, and no effort is made to make it "known good", ever. That's what the release branch is for. Second, even on the release branch, there is never a time when boost is passing all its tests, for all libraries, on all platforms. Even if you narrow your search to a single library on a single platform, you may find that there was never a time when it passed *all* its tests. A better question would be: is a snapshot of the regression results kept for each official boost release? If it were, then you could see if the features of the libraries on the platforms that are important to you are passing. I don't actually know the answer to that. -- Eric Niebler BoostPro Computing http://www.boostpro.com
Haha, don't worry, I didn't set my hopes very high. I knew it was a pretty crazy thing to ask for. Snapshots would solve my problem though. I only want to know if a certain subset of the Boost libraries passed the tests on a specific compiler for any given revision (so I can find the latest revision that meets my criteria). Hrm... Thanks for the quick response. On Fri, Mar 18, 2011 at 4:04 PM, Eric Niebler <eric@boostpro.com> wrote:
On 3/18/2011 11:51 AM, Joshua Boyce wrote:
Hey all, I was wondering if there was any way to query for the Last Known Good Revision of the Boost trunk? It would be great if there was a file or something on the website that had the revision number of the latest build to compile cleanly and pass all tests, either for all platforms, or one file for each platform.
You're going to be disappointed. There is no such file. Firstly, trunk is the wild west, and no effort is made to make it "known good", ever. That's what the release branch is for. Second, even on the release branch, there is never a time when boost is passing all its tests, for all libraries, on all platforms. Even if you narrow your search to a single library on a single platform, you may find that there was never a time when it passed *all* its tests.
A better question would be: is a snapshot of the regression results kept for each official boost release? If it were, then you could see if the features of the libraries on the platforms that are important to you are passing. I don't actually know the answer to that.
-- Eric Niebler BoostPro Computing http://www.boostpro.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 18/03/2011 05:51, Joshua Boyce wrote:
Hey all, I was wondering if there was any way to query for the Last Known Good Revision of the Boost trunk? It would be great if there was a file or something on the website that had the revision number of the latest build to compile cleanly and pass all tests, either for all platforms, or one file for each platform.
For an example of this in practice elsewhere, see the Chromium project: https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#...
<https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code#TOC-LKGR> Thanks.
Running the tests on each commit would allow to tell the status on a per-commit basis, and thus find the last commit where everything is green, but I do not think the regression testing system of Boost is fast enough to do that with current resources.
participants (3)
-
Eric Niebler -
Joshua Boyce -
Mathias Gaunard