develooper Front page | perl.perl5.porters | Postings from December 2008

Re: Smoke [5.11.0] 2008122014420798474738698849397877363453 FAIL(m) linux 2.6.22.5-49.fc6 [fedora] (i686/1 cpu)

Thread Previous
From:
demerphq
Date:
December 20, 2008 09:30
Subject:
Re: Smoke [5.11.0] 2008122014420798474738698849397877363453 FAIL(m) linux 2.6.22.5-49.fc6 [fedora] (i686/1 cpu)
Message ID:
9b18b3110812200930j15605b67iaa19cbc66f99e664@mail.gmail.com
2008/12/20 Abigail <abigail@abigail.be>:
> On Sat, Dec 20, 2008 at 09:43:00AM -0600, steve@fisharerojo.org wrote:
>> Automated smoke report for 5.11.0 patch 2008122014420798474738698849397877363453
>
>
> Is there a meaning of this number? I assume the leading 8 digits are the
> date, possibly followed by a time.
>
> Is there a relationship between this number and the SHA1 of a git commit?

Yes, that number includes the date/time and all the decimal digits
from the SHA1.

It might even be unique. :-)

Anyway, I believe that Abeltje is fixing it right now to be something
more useful.

Also ive modified the .patch file generator to include the output of
git-describe. So a valid .patch file will look like:

eg: "blead 2008-12-20.17:22:02
a2450f8e38913ec23222dc5de2f3dae8f5591d33 GitLive-blead-45-ga2450f8"

I believe that the plan right now is to use the git-describe output
(possibly in conjunction with the date/time) in smoke reports
patchlevel stuff, and -V output, and things like that.

However we really have very minimal limits on what we can with stuff.
We can produce as complicated a setup as we wish. :-)


Yves


-- 
perl -Mre=debug -e "/just|another|perl|hacker/"

Thread Previous


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About