Re: [boost] [testing] How do you interpret the SHA1 revision (outdated results)?

Subject: Re: [boost] [testing] How do you interpret the SHA1 revision (outdated results)?
From: Vladimir Prus (ghost_at_[hidden])
Date: 2014-01-23 05:35:13

On 23.01.2014 14:14, John Maddock wrote:
> So... I'm looking into Boost.Regex and I'm seeing some failures which appear to refer to outdated sources (line numbers are all wrong for
> current source), for example:
> http://www.boost.org/development/tests/develop/developer/output/marshall-mac-boost-bin-v2-libs-regex-test-regex_regress_noeh-test-clang-darwin-4-2-1-debug-exception-handling-off-link-static-threading-multi-regress.html
>
>
> But how on earth do I check this?  Reported run date is yesterday, but this was fixed/changed on Dec 20th: almost a month ago.  And the
> revision listed on the page is a SHA1 which I can't seem to relate to anything useful?

This SHA1 is superproject one:

        commit 3d21a16db5ada89d4c5875074a87ba81239048a0
        Author: Automated Commit <automated_at_[hidden]>
        Date:   Mon Jan 20 04:30:03 2014 -0500

            Update phoenix.

And it's on master branch. Here's the corresponding regex revision:

$ git ls-tree 3d21a16db5ada89d4c5875074a87ba81239048a0:libs | grep regex
160000 commit a3075dd98ffa4ffea8cf6331e1ef19dc1b42459e	regex

That revision is the tip of the master branch, and is indeed, from Dec 7.

- Volodya