[M3devel] Fwd: Output from "cron" command

Olaf Wagner wagner at elegosoft.com
Sat Jul 25 21:52:13 CEST 2009


I don't see how that will help us... It worked for Tony for over
a year, and nothing obvious has changed. Or did something change on
your side, Tony (system upgrade, path setting, ...)?

It's not good to introduce arbitrary changes now without understanding
why it breaks.

Olaf

Quoting Jay K <jay.krell at cornell.edu>:

>
> Can I suggest the portable scripting language C?
>
>
> -bash-3.00$ cat date.c
> #include
> #include
> #include
> int main()
> {
>  printf("%lu\n", (unsigned long)time(NULL));
>  return 0;
> }
> -bash-3.00$ cc date.c -o ./mydate
> -bash-3.00$ ./mydate
> 1248549753
> -bash-3.00$ pwd
> /dev2/cm3/scripts
>
>
> use that instead?
>
>  - Jay
>
>
> ----------------------------------------
>> From: jay.krell at cornell.edu
>> To: wagner at elegosoft.com; hosking at cs.purdue.edu
>> Date: Sat, 25 Jul 2009 19:19:57 +0000
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] Fwd: Output from "cron" command
>>
>>
>> (two occurences of that)
>>
>> ----------------------------------------
>>> From: jay.krell at cornell.edu
>>> To: wagner at elegosoft.com; hosking at cs.purdue.edu
>>> CC: m3devel at elegosoft.com
>>> Subject: RE: [M3devel] Fwd: Output from "cron" command
>>> Date: Sat, 25 Jul 2009 19:19:11 +0000
>>>
>>>
>>> This line:
>>>
>>>
>>> echo tinderbox: timenow: `date +%s`
>>>
>>> needs to more like these lines:
>>>
>>> echo "`date '+%Y.%m.%d %H:%M:%S'` -- checkout in progress."
>>>
>>> echo "`date '+%Y.%m.%d %H:%M:%S'` -- checkout, compile and test run done."
>>>
>>>
>>> -bash-3.00$ date '+%Y.%m.%d %H:%M:%S'
>>> 2009.07.25 12:13:54
>>>
>>> -bash-3.00$ date '+%m.%d.%y %H:%M:%S'
>>> 07.25.09 12:14:33
>>>
>>> -bash-3.00$ date +%s
>>> %s
>>>
>>> - Jay
>>>
>>>
>>> ----------------------------------------
>>>> Date: Sat, 25 Jul 2009 20:44:38 +0200
>>>> From: wagner at elegosoft.com
>>>> To: hosking at cs.purdue.edu
>>>> CC: m3devel at elegosoft.com
>>>> Subject: Re: [M3devel] Fwd: Output from "cron" command
>>>>
>>>> Quoting Tony Hosking :
>>>>
>>>>> Perhaps I am confusing with the original change I made for 1.10 to the
>>>>> parameter to the "date" command.
>>>>>
>>>>> In any case, something changed so that my scripts did not run
>>>>> properly. It's been a long time since I've seen a sane tinderbox run
>>>>> for Solaris -- will things be stabilising soon?
>>>>
>>>> I broke the last one yesterday with $() (fixed soon afterwards), but
>>>> the one before succeeded:
>>>>
>>>> http://tinderbox.elegosoft.com/tinderbox/cgi-bin/gunzip.cgi?tree=cm3&brief-log=1248363757.16203
>>>>
>>>> I was hoping to get a green build from one of your systems today
>>>> (big-endian, different architecture) to finally fix the RC2 tag.
>>>> But if you cannot send your results to the tinderbox that will be
>>>> difficult :-/ I really don't understand why that should have stopped
>>>> working.
>>>>
>>>> The error below seems to be that the reported start time is 0, and
>>>> that cannot be according to the source. Could you set -x at the start
>>>> of the tinderbox script and try again?
>>>>
>>>> Jay, can you think of anything you have changed that may cause Tony's
>>>> problem?
>>>>
>>>> Olaf
>>>>
>>>>> -- Tony (not mobile)
>>>> :-)
>>>>
>>>>> On 25 Jul 2009, at 14:00, Olaf Wagner wrote:
>>>>>
>>>>>> Quoting Tony Hosking :
>>>>>>
>>>>>>> This is an old error for Solaris that I fixed a long time ago. Can
>>>>>>> someone restore?
>>>>>>
>>>>>> Hi Tony,
>>>>>>
>>>>>> as far as I can see nothing has changed regarding STARTTIME:
>>>>>>
>>>>>>
>>>>>>> % cvs ann scripts/regression/tinderbox-build.sh | egrep   
>>>>>>> 'STARTTIME| date'
>>>>>>
>>>>>> Annotations for scripts/regression/tinderbox-build.sh
>>>>>> ***************
>>>>>> 1.10 (hosking 09-Mar-08): NAME="build-${PROJECT}-`date
>>>>>> '+%Y %m%d-%H%M%S'`"
>>>>>> 1.8 (wagner 03-Feb-08): STARTTIME="$4"
>>>>>> 1.8 (wagner 03-Feb-08): if [ -z "${TREE_NAME}" -o -z
>>>>>> "$ {BUILD_NAME}" -o -z "${STATUS}" -o -z "${STARTTIME}" ]
>>>>>> 1.8 (wagner 03-Feb-08): echo "
>>>>>> date 'date +%s'"
>>>>>> 1.8 (wagner 03-Feb-08): echo tinderbox: starttime: $STARTTIME
>>>>>> 1.8 (wagner 03-Feb-08): echo tinderbox: timenow: `date + %s`
>>>>>> 1.8 (wagner 03-Feb-08): tinderbox_header "$
>>>>>> {TREENAME}" "${BUILDNAME}" "$1" "${STARTTIME}"
>>>>>> 1.1 (kschleis 06-Jan-08): STARTTIME=`date +%s`
>>>>>> 1.10 (hosking 09-Mar-08): echo "`date '+%Y.%m.%d %H:%M:
>>>>>> %S'` -- checkout in progress."
>>>>>> 1.10 (hosking 09-Mar-08): echo "[start checkout `date
>>>>>> '+ %Y.%m.%d %H:%M:%S'`]"
>>>>>> 1.10 (hosking 09-Mar-08): echo "[end checkout `date
>>>>>> '+%Y. %m.%d %H:%M:%S'`]"
>>>>>> 1.10 (hosking 09-Mar-08): echo "`date '+%Y.%m.%d
>>>>>> %H:%M: %S'` -- compile in progress."
>>>>>> 1.10 (hosking 09-Mar-08): echo "[start compile `date
>>>>>> '+ %Y.%m.%d %H:%M:%S'`]"
>>>>>> 1.10 (hosking 09-Mar-08): echo "[end compile `date '+%Y.
>>>>>> %m.%d %H:%M:%S'`]"
>>>>>> 1.10 (hosking 09-Mar-08): echo "`date '+%Y.%m.%d
>>>>>> %H:%M: %S'` -- tests in progress."
>>>>>> 1.10 (hosking 09-Mar-08): echo "[start run-tests `date
>>>>>> '+%Y.%m.%d %H:%M:%S'`]"
>>>>>> 1.10 (hosking 09-Mar-08): echo "[end run-tests `date
>>>>>> '+%Y. %m.%d %H:%M:%S'`]"
>>>>>> 1.10 (hosking 09-Mar-08): echo "`date '+%Y.%m.%d %H:%M:
>>>>>> %S'` -- checkout, compile and test run done."
>>>>>>
>>>>>> Nothing at all has changed in these scripts in July:
>>>>>>
>>>>>> % cvs ann scripts/regression/tinderbox-build.sh | egrep Jul-09
>>>>>>
>>>>>> Annotations for scripts/regression/tinderbox-build.sh
>>>>>> ***************
>>>>>> luthien [~/work/cm3] wagner
>>>>>> % cvs ann scripts/regression/cm3.bu | egrep Jul-09
>>>>>> cm3.build cm3.build~
>>>>>> luthien [~/work/cm3] wagner
>>>>>> % cvs ann scripts/regression/cm3.build | egrep Jul-09
>>>>>>
>>>>>> Annotations for scripts/regression/cm3.build
>>>>>> ***************
>>>>>> luthien [~/work/cm3] wagner
>>>>>>
>>>>>>
>>>>>> Perhaps I'm looking for the wrong thing. What exactly did you change
>>>>>> long ago to make it work? I'm at a loss now.
>>>>>>
>>>>>>> Sent from my iPhone
>>>>>>
>>>>>> You seem to be very `mobile' lately ;-)
>>>>>>
>>>>>>
>>>>>>> Begin forwarded message:
>>>>>>>
>>>>>>>> From: Tony Hosking
>>>>>>>> Date: July 25, 2009 5:30:35 AM CDT
>>>>>>>> To: hosking at cs.purdue.edu
>>>>>>>> Subject: Output from "cron" command
>>>>>>>>
>>>>>>>
>>>>>>>> Your "cron" job on niagara.cs.purdue.edu
>>>>>>>> $HOME/cm3/scripts/regression/cron.sh
>>>>>>>>
>>>>>>>> produced the following output:
>>>>>>>>
>>>>>>>> U regression-scripts/defs.sh
>>>>>>>> TESTHOSTNAME=niagara
>>>>>>>> WS=/homes/hosking/work/cm3-ws/niagara-2009-07-25-10-30-19
>>>>>>>> LASTREL=5.4.0
>>>>>>>> INSTROOT_REL=/homes/hosking/work/cm3-inst/niagara/rel-5.4.0
>>>>>>>> INSTROOT_POK=/homes/hosking/work/cm3-inst/niagara/prev-ok
>>>>>>>> INSTROOT_LOK=/homes/hosking/work/cm3-inst/niagara/last-ok
>>>>>>>> INSTROOT_CUR=/homes/hosking/work/cm3-inst/niagara/current
>>>>>>>> CM3_OSTYPE=POSIX
>>>>>>>> CM3_TARGET=SOLgnu
>>>>>>>> BINDISTMIN=/homes/hosking/work/cm3-min-POSIX-SOLgnu-5.4.0.tgz
>>>>>>>> CM3CVSSERVER=birch.elegosoft.com
>>>>>>>> CM3CVSROOT=birch.elegosoft.com:/usr/cvs
>>>>>>>> BINDISTMIN_NAME=cm3-min-POSIX-SOLgnu-5.4.0.tgz
>>>>>>>> BINDISTMIN=/homes/hosking/work/cm3-min-POSIX-SOLgnu-5.4.0.tgz
>>>>>>>> CM3CVSUSER=
>>>>>>>> testing ssh birch.elegosoft.com..
>>>>>>>> ssh birch.elegosoft.com ok
>>>>>>>> Building cm3.
>>>>>>>> Tinderbox Tree: "cm3"
>>>>>>>> Buildname: "SOLgnu SunOS 5.10 niagara release-build"
>>>>>>>>
>>>>>>>> creating log file /tmp/build-cm3-20090725-063023-tVaq2V/log.txt
>>>>>>>>
>>>>>>>> ---
>>>>>>>>
>>>>>>>> checkout, compile and test of cm3 ...
>>>>>>>> 2009.07.25 06:30:23 -- checkout in progress.
>>>>>>>> [Sat Jul 25 12:30:27 2009] Variable: 'tinderbox: timenow:', is
>>>>>>>> not of the form MM/DD/YY HH:MM:SS, or unix date, or your clock
>>>>>>>> is set incorrectly, or the mail was delayed for a long time.
>>>>>>>> variable timenow: 0, timenow: 1248517827, (-20808630.45 minutes)
>>>>>>>>
>>>>>>>> Error: Sending buildlog failed!
>>>>>>>> removing build tree /tmp/build-cm3-20090725-063023-tVaq2V ...
>>>>>>>> cleaning CM3 workspaces...
>>>>>>>> /homes/hosking/work/cm3-ws/niagara-*
>>>>>>>>
>>>>>>>> cleaning regression test log files...
>>>>>>>> /homes/hosking/tmp/cm3/niagara/cm3-rlog-*
>>>>>>>>
>>>>>>>> cleaning m3test log files...
>>>>>>>> /homes/hosking/tmp/cm3/niagara/m3tests-*.stdout
>>>>>>>>
>>>>>>>> /homes/hosking/tmp/cm3/niagara/m3tests-*.stderr
>>>>>>>>
>>>>>>>> /homes/hosking/tmp/cm3/niagara/m3tests-*.stderr.extract
>>>>>>>>
>>>>>>>> cleaning snapshot files...
>>>>>>>> /homes/hosking/tmp/cm3/niagara/cm3-min-POSIX-SOLgnu-*-*.tgz
>>>>>>>>
>>>>>>>> cleaning package reports...
>>>>>>>> /tmp/cm3-pkg-report-SOLgnu-*.html
>>>>>>>>
>>>>>>>> TESTHOSTNAME=niagara
>>>>>>>> WS=/homes/hosking/work/cm3-ws/niagara-2009-07-25-10-30-30
>>>>>>>> LASTREL=5.4.0
>>>>>>>> INSTROOT_REL=/homes/hosking/work/cm3-inst/niagara/rel-5.4.0
>>>>>>>> INSTROOT_POK=/homes/hosking/work/cm3-inst/niagara/prev-ok
>>>>>>>> INSTROOT_LOK=/homes/hosking/work/cm3-inst/niagara/last-ok
>>>>>>>> INSTROOT_CUR=/homes/hosking/work/cm3-inst/niagara/current
>>>>>>>> CM3_OSTYPE=POSIX
>>>>>>>> CM3_TARGET=SOLgnu
>>>>>>>> BINDISTMIN=/homes/hosking/work/cm3-min-POSIX-SOLgnu-5.4.0.tgz
>>>>>>>> CM3CVSSERVER=birch.elegosoft.com
>>>>>>>> CM3CVSROOT=birch.elegosoft.com:/usr/cvs
>>>>>>>> BINDISTMIN_NAME=cm3-min-POSIX-SOLgnu-5.4.0.tgz
>>>>>>>> BINDISTMIN=/homes/hosking/work/cm3-min-POSIX-SOLgnu-5.4.0.tgz
>>>>>>>> CM3CVSUSER=
>>>>>>>> testing ssh birch.elegosoft.com..
>>>>>>>> ssh birch.elegosoft.com ok
>>>>>>>> Building cm3.
>>>>>>>> Tinderbox Tree: "cm3"
>>>>>>>> Buildname: "SOLgnu SunOS 5.10 niagara lastok-build"
>>>>>>>>
>>>>>>>> creating log file /tmp/build-cm3-20090725-063032-xba4dW/log.txt
>>>>>>>>
>>>>>>>> ---
>>>>>>>>
>>>>>>>> checkout, compile and test of cm3 ...
>>>>>>>> 2009.07.25 06:30:32 -- checkout in progress.
>>>>>>>> [Sat Jul 25 12:30:35 2009] Variable: 'tinderbox: timenow:', is
>>>>>>>> not of the form MM/DD/YY HH:MM:SS, or unix date, or your clock
>>>>>>>> is set incorrectly, or the mail was delayed for a long time.
>>>>>>>> variable timenow: 0, timenow: 1248517835, (-20808630.5833333 minutes)
>>>>>>>>
>>>>>>>> Error: Sending buildlog failed!
>>>>>>>> removing build tree /tmp/build-cm3-20090725-063032-xba4dW ...
>>>>>>>> cleaning CM3 workspaces...
>>>>>>>> /homes/hosking/work/cm3-ws/niagara-*
>>>>>>>>
>>>>>>>> cleaning regression test log files...
>>>>>>>> /homes/hosking/tmp/cm3/niagara/cm3-rlog-*
>>>>>>>>
>>>>>>>> cleaning m3test log files...
>>>>>>>> /homes/hosking/tmp/cm3/niagara/m3tests-*.stdout
>>>>>>>>
>>>>>>>> /homes/hosking/tmp/cm3/niagara/m3tests-*.stderr
>>>>>>>>
>>>>>>>> /homes/hosking/tmp/cm3/niagara/m3tests-*.stderr.extract
>>>>>>>>
>>>>>>>> cleaning snapshot files...
>>>>>>>> /homes/hosking/tmp/cm3/niagara/cm3-min-POSIX-SOLgnu-*-*.tgz
>>>>>>>>
>>>>>>>> cleaning package reports...
>>>>>>>> /tmp/cm3-pkg-report-SOLgnu-*.html
>>>>>>>>
>>>>>> --
>>>>>> Olaf Wagner -- elego Software Solutions GmbH
>>>>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>>>>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23
>>>>>> 45 86 95
>>>>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>>>>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:
>>>>>> DE163214194
>>>> --
>>>> Olaf Wagner -- elego Software Solutions GmbH
>>>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>>>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
>>>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>>>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr:   
>>>> DE163214194
>>>>



-- 
Olaf Wagner -- elego Software Solutions GmbH
                Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
phone: +49 30 23 45 86 96  mobile: +49 177 2345 869  fax: +49 30 23 45 86 95
    http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194




More information about the M3devel mailing list