[M3devel] Fwd: Output from "cron" command

Jay K jay.krell at cornell.edu
Thu Jul 14 22:40:35 CEST 2011


I agree that the relationship is missing or tenuous. But I was going to be quiet and polite.

OP implied question: is modula3.org up?
Daniel: run cvsup against modula3.org to see if it is up.
Daniel: Talk about cvsup and its unusual behavior wrt threads, and then other hardware and software systems...

But I go off on tangents also.

On the OP, though, there is very little information to go on. Just that the cron job failed, somehow. That has bugged me a few times.
But, one can often go look at Tinderbox or Hudson, for more information, usually clear there. Which I haven't yet.
But there have also been almost no changes lately, thus the conjecture as to the problem...and the tangent.
Much talk. Little time for code.

 - Jay


From: felipevaldez at gmail.com
Date: Thu, 14 Jul 2011 14:48:28 -0500
To: dabenavidesd at yahoo.es
CC: m3devel at elegosoft.com
Subject: Re: [M3devel] Fwd: Output from "cron" command

I'm not sure that the message posted by Daniel, is in any way related to the OP.



perhaps I'm too dumb?



On Thu, Jul 14, 2011 at 2:44 PM, Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es> wrote:


Hi all:
This is to say why threads behaved seamengly for so many years in that fashion (apart of Win32, but as far as I know cygwin doesn't know cvsup, and if so how could one implement Unix API without using same NT thread support or at most would get the same old behaviour if so) but ALPHA_OSF, which  John Polstra wrote needed the @M3nopreemption RTParams, I wonder why that's.


Anyway, thus the only working-well behaved platform is that only and how one could run someone else. Perhaps reworking the SPIN threads to target everything else (if is enough layered we can somehow think that but would of course need their sources support besides figuring out how to build them) the other way would be Alphas hardware like for NIC, routers, etc (Jay's collection might have some data on that). I know for something the virtual terminals are in another business
 company, but all net-ware I don't where's about wherever that is, although I remember something about Gigabit ATM servers software that they used to run and develop algorithms of Charles Tacker.  
Thanks in advance




--- El jue, 14/7/11, Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es> escribió:



De: Daniel Alejandro Benavides D. <dabenavidesd at yahoo.es>
Asunto: Re: [M3devel] Fwd: Output from "cron" command
Para: "m3devel developers" <m3devel at elegosoft.com>, "Tony Hosking" <hosking at cs.purdue.edu>


Fecha: jueves, 14 de julio, 2011 11:41



Hi all:
I don't know but I haven't tried the cvsup since I was hit by other problems (such as recompiling DEC-SRC sources like  user space threads but was able before because are broken, meaning I can't afford the loosely compatibility and don't want apply to lose the system so quickly).


I would like the path to an approach for solving this issues before going forward.

test at fbd-desktop:~/cm3$ ../bin/cvsup cvsup.cm3
Name lookup failure for "modula3.elegosoft.com": Host name lookup failed


Will retry at 11:40:54


--- El jue, 14/7/11, Tony Hosking <hosking at cs.purdue.edu> escribió:



De: Tony Hosking <hosking at cs.purdue.edu>
Asunto: [M3devel] Fwd: Output from "cron" command
Para: "m3devel developers"
 <m3devel at elegosoft.com>
Fecha: jueves, 14 de julio, 2011 08:38

Issues with the server?


Begin forwarded message:
From: Tony Hosking <hosking at cs.purdue.edu>


Date: July 14, 2011 8:17:22 AM EDT


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:

GMAKE=gmake


export GMAKE
TAR=gtar
export
 TAR
TESTHOSTNAME=niagara
WS=/homes/hosking/work/cm3-ws/niagara-2011-07-10-10-30-03
LASTREL=5.8.6
INSTROOT_REL=/homes/hosking/work/cm3-inst/niagara/rel-5.8.6
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-bin-min-SOLgnu-5.8.6.tgz


CM3CVSSERVER=birch.elegosoft.com
CM3CVSROOT=birch.elegosoft.com:/usr/cvs
BINDISTMIN_NAME=cm3-bin-min-SOLgnu-5.8.6.tgz
BINDISTMIN=/homes/hosking/work/cm3-bin-min-SOLgnu-5.8.6.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-20110710-063005-RRa4C1/log.txt

---

checkout, compile and test of cm3 ...
2011.07.10 06:30:05 -- checkout in progress.


[start checkout 2011.07.10 06:30:08]
cd /tmp/build-cm3-20110710-063005-RRa4C1/build
cvs return value: 1
[end checkout 2011.07.13 16:56:51]
CHECKOUT_RETURN = 1
*** CHECKOUT FAILED
removing build tree /tmp/build-cm3-20110710-063005-RRa4C1 ...


cleaning CM3 workspaces...
/homes/hosking/work/cm3-ws/niagara-*
cleanup_all_but_last_n
cleanup_all_but_last_n

cleaning regression test log files...
/homes/hosking/tmp/cm3/niagara/cm3-rlog-*
cleanup_all_but_last_n


cleanup_all_but_last_n

cleaning m3test log
 files...
/homes/hosking/tmp/cm3/niagara/m3tests-*.stdout
cleanup_all_but_last_n
cleanup_all_but_last_n

/homes/hosking/tmp/cm3/niagara/m3tests-*.stderr
cleanup_all_but_last_n
cleanup_all_but_last_n



/homes/hosking/tmp/cm3/niagara/m3tests-*.stderr.extract
cleanup_all_but_last_n
cleanup_all_but_last_n

cleaning snapshot files...
/homes/hosking/tmp/cm3/niagara/cm3-min-POSIX-SOLgnu-*-*.tgz
cleanup_all_but_last_n


cleanup_all_but_last_n

cleaning package reports...
/tmp/cm3-pkg-report-SOLgnu-*.html
cleanup_all_but_last_n
cleanup_all_but_last_n

done with cleanup_all
GMAKE=gmake
export GMAKE
TAR=gtar


export
 TAR
TESTHOSTNAME=niagara
WS=/homes/hosking/work/cm3-ws/niagara-2011-07-13-20-56-57
LASTREL=5.8.6
INSTROOT_REL=/homes/hosking/work/cm3-inst/niagara/rel-5.8.6
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-bin-min-SOLgnu-5.8.6.tgz


CM3CVSSERVER=birch.elegosoft.com
CM3CVSROOT=birch.elegosoft.com:/usr/cvs
BINDISTMIN_NAME=cm3-bin-min-SOLgnu-5.8.6.tgz
BINDISTMIN=/homes/hosking/work/cm3-bin-min-SOLgnu-5.8.6.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-20110713-165659-qeaGbN/log.txt

---

checkout, compile and test of cm3 ...
2011.07.13 16:56:59 -- checkout in progress.


[start checkout 2011.07.13 16:57:02]
cd /tmp/build-cm3-20110713-165659-qeaGbN/build
cvs return value: 1
[end checkout 2011.07.14 08:17:06]
CHECKOUT_RETURN = 1
*** CHECKOUT FAILED
removing build tree /tmp/build-cm3-20110713-165659-qeaGbN ...


cleaning CM3 workspaces...
/homes/hosking/work/cm3-ws/niagara-*
cleanup_all_but_last_n
cleanup_all_but_last_n /homes/hosking/work/cm3-ws/niagara-2011-07-12-14-46-51

cleaning regression test log files...


/homes/hosking/tmp/cm3/niagara/cm3-rlog-*
cleanup_all_but_last_n
cleanup_all_but_last_n

cleaning m3test log
 files...
/homes/hosking/tmp/cm3/niagara/m3tests-*.stdout
cleanup_all_but_last_n
cleanup_all_but_last_n

/homes/hosking/tmp/cm3/niagara/m3tests-*.stderr
cleanup_all_but_last_n
cleanup_all_but_last_n



/homes/hosking/tmp/cm3/niagara/m3tests-*.stderr.extract
cleanup_all_but_last_n
cleanup_all_but_last_n

cleaning snapshot files...
/homes/hosking/tmp/cm3/niagara/cm3-min-POSIX-SOLgnu-*-*.tgz
cleanup_all_but_last_n


cleanup_all_but_last_n

cleaning package reports...
/tmp/cm3-pkg-report-SOLgnu-*.html
cleanup_all_but_last_n
cleanup_all_but_last_n

done with cleanup_all





-- 
312-444-2124Skype: f3l.headhunterCasa: 8043901





 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20110714/d33b37ed/attachment-0002.html>


More information about the M3devel mailing list