Subject: Re: [boost] [testing] How do you interpret the SHA1 revision(outdated results)?
From: Vladimir Prus (ghost_at_[hidden])
Date: 2014-01-23 06:50:00
On 23.01.2014 15:18, John Maddock wrote:
>> 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.
> Great. Two questions:
> 1) How come the Mac tests are being run on 2 month old sources?
Sorry for being vague above. They are run on master branch of the super project, which points to master
branch of regex, which is that old. I am unsure what's the value of testing master branch of superproject
at this point. It's too early.
> 2) How did you figure that out?
> If I run the git ls-tree command above on my working system I get a "not a valid object name" error, plus not everyone has a Unix command
> line to hand...
Did you do "git fetch" in the superproject? As for Unix command line, the approach that Michael used will work as well - look at the
tree at github and it should have subproject references, like so:
- Go to https://github.com/boostorg/boost/commit/3d21a16db5ada89d4c5875074a87ba81239048a0
- Click 'browse code'
- Go to 'libs' and record the short id of regex.
- Manually paste that id into URL, like so: https://github.com/boostorg/regex/commit/a3075dd
Yes, it's ugly roundabout way.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk