Subject: Re: [Boost-build] meaning of "rev" in test report
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-27 12:18:25
On 27.10.2016 11:46, Rene Rivera wrote:
> On Thu, Oct 27, 2016 at 10:37 AM, Stefan Seefeld <stefan_at_[hidden]
> <mailto:stefan_at_[hidden]>> wrote:
> the test report matrix reports a "rev" attribute for each test run,
> presumably showing a git SHA. However, I'm somewhat doubtful about
> repository that is referring to. For example I'd expect the revs in
> correspond to SHAs in the https://github.com/boostorg/python
> <https://github.com/boostorg/python> repo.
> However, I can't seem to find a single match, i.e. none of the SHAs I
> see in the matrix appears in my git log.
> If that's not the repo whose revision is being reported, which repo is
> being used ? And how can I map that to the revision of the module
> tested (Boost.Python in this case) ?
> (The reason I'm asking is that now that the NumPy tests trickle in, I
> see a bunch of failures, but looking at the error I notice an issue I
> fixed a week (or so) ago, yet the test runs are more recent than
> that. I
> think it's crucial for the test report to give a clear indication
> of the
> tested module's SHA to make it possible to attempt to reproduce the
> tests locally.
> The main rev you see in the reports is the SHA of the superproject
> <https://github.com/boostorg/boost>. If you look at the info for each
> tester there's a list of each of the submodules with a SHA of the
> submodule version that was pulled in that superproject rev. For
> example in
> scroll down past the tester env info and you'll see a table of "Repo"
> and "Revision" entries like this:
> Repo Revision
> The first entry if the Boost Build version used to drive the testing.
> The second is the regression tools used. The third is the same as the
> one reported in the main result pages (ie the superproject). And the
> rest are the ones for submodule.
It does indeed. :-)
-- ...ich hab' noch einen Koffer in Berlin...
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk