[M3devel] Short status of CM3 Hudson regression testing on opencsw.org machines

Olaf Wagner wagner at elegosoft.com
Mon Aug 9 12:28:56 CEST 2010


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

> Very nice.
>
> Copying & cvs could be separate tasks, run on login? ("login" being   
> a machine, not a "time").
Copying out will probably be no problem, but CVS is tightly integrated
into Hudson and needs to be (for impact tracking). I already considered
running cvs on login.opencsw.org, but don't know how to configure that.

> In fact these all share one filesystem &  could share workspaces,  
> albeit with serialization? The problem isn't  sharing without  
> serialization?

No, the workspaces are different (hostname in paths).

That would be an imaginable setup, too. But Hudson likes to keep
jobs separate and isolated, so it would be even more work I think.

> The other interesting platforms are AMD64_SOLARIS and   
> SPARC64_SOLARIS. Should consider SPARC32_SOLARIS & drop SOLgnu &   
> SOLsun. It is already implemented.

Yes, I should have used SPARC32_SOLARIS instead of SOLsun; will change
that at the next opportunity.

Do I just need to set the TARGET to compile for those platforms (including
AMD64/SPARC64) on those machines?

Olaf

>> Date: Mon, 9 Aug 2010 10:21:36 +0200
>> From: wagner at elegosoft.com
>> To: m3devel at elegosoft.com
>> Subject: [M3devel] Short status of CM3 Hudson regression testing   
>> on	opencsw.org	machines
>>
>> After several weeks (months?) of little activity I was able to setup
>> some more build and regression test jobs on the opencsw.org machines.
>>
>> There are now sets of jobs for
>>
>>    SOLsun built on Solaris 10 (works) run on current10s.opencsw.org
>>    SOLsun built on Solaris 9 (seems now to work, too) run on current9s
>>    I386_SOLARIS built on Solaris 10 (still several problems) run on  
>>  current10x
>>
>> For the instruction and exhilaration of those willing to read on I'll
>> give some details.
>>
>> One of the problems was entirely my own fault. In the regression defs.sh
>> script, about a dozen error messages were written to 1>2 instead of 1>&2.
>> The second correct form redirects stdout to stderr, while the first just
>> writes the contents to a file named 2 :-/ It's not that I haven't got
>> enough experience with writing shell scripts (in fact I've done that
>> hundreds of times), but I must have made a typo in one place in the
>> original file version and copied that to many other locations. It is
>> interesting that I didn't notice that for years, though I've looked
>> at it all the time. I was getting desparate about unexplained stops
>> in the scripts tonight when finally a veil seems to have been removed
>> from my eyes.
>>
>> Currently I know of two other problems running our builds and tests
>> on the opencsw machines.
>>
>> 1. cvs update does not work on current10x (Solaris on x86) when run from
>>     Hudson.
>>     It does work on current10s and current9s.
>>     It does work if I disable compression (but can do that only for  
>>  all jobs,
>>     which would be a bad pessimization).
>>     It does work if I run it from the command line.
>>     cvs co in Hudson works OK, too.
>>
>>     All attempts to update workspaces by Hudson fail with
>>
>>       [cm3] $ cvs -q -z3 update -PdC -D "Sunday, August 8, 2010   
>> 8:59:46 PM UTC"
>>       ...
>>       cvs [update aborted]: end of file from server (consult above
>> messages if any)
>>       FATAL: CVS failed. exit code=1
>>
>>     Obviously, there are no above messages to consult.
>>     If anybody has any ideas what could be causing this, I'd like to
>>     hear it. Without update, all the jobs will run rather long on that
>>     machine.
>>     All machines run exactly the same version of CVS.
>>
>> 2. Copying any archive files out again via ssh and scp has not worked
>>     yet. I still need to investigate this, but have hope that I can make
>>     this work.
>>
>> Builds for more target platforms should be setup on those machines,
>> but it's tedious work. If anybody wants to take a try, that will be
>> appreciated.
>>
>> Olaf
-- 
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