<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>Do I just need to set the TARGET to compile for those platforms (including<br>AMD64/SPARC64) on those machines?<br><br>Um, yes, should just work? (famous lie..). Should even be able to use the same cm3cg.<br><br> - Jay<br><br>> Date: Mon, 9 Aug 2010 12:28:56 +0200<br>> From: wagner@elegosoft.com<br>> To: jay.krell@cornell.edu<br>> CC: m3devel@elegosoft.com; dam@baltic-online.de<br>> Subject: Re: [M3devel] Short status of CM3 Hudson regression testing on opencsw.org machines<br>> <br>> Quoting Jay K <jay.krell@cornell.edu>:<br>> <br>> > Very nice.<br>> ><br>> > Copying & cvs could be separate tasks, run on login? ("login" being <br>> > a machine, not a "time").<br>> Copying out will probably be no problem, but CVS is tightly integrated<br>> into Hudson and needs to be (for impact tracking). I already considered<br>> running cvs on login.opencsw.org, but don't know how to configure that.<br>> <br>> > In fact these all share one filesystem & could share workspaces, <br>> > albeit with serialization? The problem isn't sharing without <br>> > serialization?<br>> <br>> No, the workspaces are different (hostname in paths).<br>> <br>> That would be an imaginable setup, too. But Hudson likes to keep<br>> jobs separate and isolated, so it would be even more work I think.<br>> <br>> > The other interesting platforms are AMD64_SOLARIS and <br>> > SPARC64_SOLARIS. Should consider SPARC32_SOLARIS & drop SOLgnu & <br>> > SOLsun. It is already implemented.<br>> <br>> Yes, I should have used SPARC32_SOLARIS instead of SOLsun; will change<br>> that at the next opportunity.<br>> <br>> Do I just need to set the TARGET to compile for those platforms (including<br>> AMD64/SPARC64) on those machines?<br>> <br>> Olaf<br>> <br>> >> Date: Mon, 9 Aug 2010 10:21:36 +0200<br>> >> From: wagner@elegosoft.com<br>> >> To: m3devel@elegosoft.com<br>> >> Subject: [M3devel] Short status of CM3 Hudson regression testing <br>> >> on opencsw.org machines<br>> >><br>> >> After several weeks (months?) of little activity I was able to setup<br>> >> some more build and regression test jobs on the opencsw.org machines.<br>> >><br>> >> There are now sets of jobs for<br>> >><br>> >> SOLsun built on Solaris 10 (works) run on current10s.opencsw.org<br>> >> SOLsun built on Solaris 9 (seems now to work, too) run on current9s<br>> >> I386_SOLARIS built on Solaris 10 (still several problems) run on <br>> >> current10x<br>> >><br>> >> For the instruction and exhilaration of those willing to read on I'll<br>> >> give some details.<br>> >><br>> >> One of the problems was entirely my own fault. In the regression defs.sh<br>> >> script, about a dozen error messages were written to 1>2 instead of 1>&2.<br>> >> The second correct form redirects stdout to stderr, while the first just<br>> >> writes the contents to a file named 2 :-/ It's not that I haven't got<br>> >> enough experience with writing shell scripts (in fact I've done that<br>> >> hundreds of times), but I must have made a typo in one place in the<br>> >> original file version and copied that to many other locations. It is<br>> >> interesting that I didn't notice that for years, though I've looked<br>> >> at it all the time. I was getting desparate about unexplained stops<br>> >> in the scripts tonight when finally a veil seems to have been removed<br>> >> from my eyes.<br>> >><br>> >> Currently I know of two other problems running our builds and tests<br>> >> on the opencsw machines.<br>> >><br>> >> 1. cvs update does not work on current10x (Solaris on x86) when run from<br>> >> Hudson.<br>> >> It does work on current10s and current9s.<br>> >> It does work if I disable compression (but can do that only for <br>> >> all jobs,<br>> >> which would be a bad pessimization).<br>> >> It does work if I run it from the command line.<br>> >> cvs co in Hudson works OK, too.<br>> >><br>> >> All attempts to update workspaces by Hudson fail with<br>> >><br>> >> [cm3] $ cvs -q -z3 update -PdC -D "Sunday, August 8, 2010 <br>> >> 8:59:46 PM UTC"<br>> >> ...<br>> >> cvs [update aborted]: end of file from server (consult above<br>> >> messages if any)<br>> >> FATAL: CVS failed. exit code=1<br>> >><br>> >> Obviously, there are no above messages to consult.<br>> >> If anybody has any ideas what could be causing this, I'd like to<br>> >> hear it. Without update, all the jobs will run rather long on that<br>> >> machine.<br>> >> All machines run exactly the same version of CVS.<br>> >><br>> >> 2. Copying any archive files out again via ssh and scp has not worked<br>> >> yet. I still need to investigate this, but have hope that I can make<br>> >> this work.<br>> >><br>> >> Builds for more target platforms should be setup on those machines,<br>> >> but it's tedious work. If anybody wants to take a try, that will be<br>> >> appreciated.<br>> >><br>> >> Olaf<br>> -- <br>> Olaf Wagner -- elego Software Solutions GmbH<br>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany<br>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95<br>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin<br>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194<br>> <br> </body>
</html>