Smoke [5.11.0] 2008122014420798474738698849397877363453 FAIL(m) linux 2.6.22.5-49.fc6 [fedora] (i686/1 cpu)
Automated smoke report for 5.11.0 patch 2008122014420798474738698849397877363453 kirk.peters.homeunix.org: Intel(R) Celeron(R) CPU 2.00GHz (GenuineIntel 1994MHz) (i686/1 cpu) onlinux - 2.6.22.5-49.fc6 [fedora] using icc version smoketime 42 minutes 37 seconds (average 2 minutes 39.812 seconds) Summary: FAIL(m) O = OK F = Failure(s), extended report at the bottom X = Failure(s) under TEST but not under harness ? = still running or test results not (yet) available Build failures during: - = unknown or N/A c = Configure, m = make, M = make (after miniperl), t = make test-prep 2008122014420798474738698849397877363453 Configuration (common) -Dcc=icc --- - m - m - m - m - -Duse64bitint m - m - -Duselongdouble m - m - -Dusemorebits m - m - -Duseithreads m - m - -Duseithreads -Duse64bitint m - m - -Duseithreads -Duselongdouble m - m - -Duseithreads -Dusemorebits | | | +- PERLIO = perlio -DDEBUGGING | | +--- PERLIO = stdio -DDEBUGGING | +- PERLIO = perlio +--- PERLIO = stdio Locally applied patches: DEVEL SMOKE2008122014420798474738698849397877363453 MANIFEST did not declare 'Porting/git-find-p4-change' MANIFEST did not declare 'Porting/switch_to_perforce_id.pl' MANIFEST did not declare 'lib/autodie/exception.pm' MANIFEST did not declare 'lib/autodie/exception/system.pm' -- Report by Test::Smoke v1.19_83 build 980 running on perl 5.10.0 (Reporter v0.026 / Smoker v0.029)
Re: Smoke [5.11.0] 2008122014420798474738698849397877363453 FAIL(m) linux 2.6.22.5-49.fc6 [fedora] (i686/1 cpu)
2008/12/20 Abigail abig...@abigail.be: On Sat, Dec 20, 2008 at 09:43:00AM -0600, st...@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/
Re: Smoke [5.11.0] 2008122014420798474738698849397877363453 FAIL(m) linux 2.6.22.5-49.fc6 [fedora] (i686/1 cpu)
On Sat, Dec 20, 2008 at 09:43:00AM -0600, st...@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? Abigail
