Hi,

Sanity tests for DIY run 'snv_117-k93t0702' passed fine. I've attached 
install script and install logs for sparcs.

I've now submitted the full batch of tests under build name 
'snv_117-k93r0702'.

Regards,

Thomas


On 07/03/09 13:11, thomas palud - Sun Microsystems - Dublin Ireland wrote:
> Hi,
>
> I've submitted a couple of sanity tests in DIY under the name 
> 'snv_117-k93t0702'
>
> When completed and verified I will submit the full batch of tests.
>
> Note that DIY is very busy at the moment with over 1000 tests waiting 
> to run ... it may take a while before it gets to run.
>
> Cheers,
>
> Thomas
>
> On 07/02/09 21:09, Roland Mainz wrote:
>> Milan Jurik wrote:
>>   
>>> Roland Mainz p????e v ??t 02. 07. 2009 v 20:22 +0200:
>>>     
>> [snip]
>>   
>>>> 2. The current set of binaries passes the following tests:
>>>> - Building SFWNV (SPARC+x86), both normal and with /sbin/sh==ksh93
>>>> (excluding the issue described in
>>>> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6817601
>>>> (which I manually worked-around))
>>>> - Booting SXB110 with ksh93 updated but not /sbin/sh+/usr/bin/sh updated
>>>> to ksh93: Ok on SPARC and x86 two times for each platform
>>>> - Booting SXB110 with ksh93 updated _and_ /sbin/sh+/usr/bin/sh updated
>>>> to ksh93: Ok on SPARC and x86 two times for each platform
>>>> - bldenv compiling OS/Net with ksh93 updated but not
>>>> /sbin/sh+/usr/bin/sh updated to ksh93: Ok on SPARC and x86 two two for
>>>> each platform
>>>> - bldenv compiling OS/Net with ksh93 updated _and_ /sbin/sh+/usr/bin/sh
>>>> updated to ksh93: Ok on SPARC and x86 two times for each platform
>>>> - "nightly" compiling OS/Net with ksh93 updated but not
>>>> /sbin/sh+/usr/bin/sh updated to ksh93: Ok on SPARC and x86 three times
>>>> for SPARC and two times for x86
>>>> - "nightly" compiling OS/Net with ksh93 updated _and_
>>>> /sbin/sh+/usr/bin/sh updated to ksh93: Ok on SPARC and x86 three times
>>>> for each platform
>>>> - compiling FOX with ksh93 updated but not /sbin/sh+/usr/bin/sh updated
>>>> to ksh93: Ok on SPARC and x86
>>>> - compiling FOX with ksh93 updated _and_ /sbin/sh+/usr/bin/sh updated to
>>>> ksh93: Ok on SPARC and x86
>>>> - compiling+using KDE with ksh93 updated but not /sbin/sh+/usr/bin/sh
>>>> updated to ksh93: Ok on SPARC and x86
>>>> - compiling+using KDE with ksh93 updated _and_ /sbin/sh+/usr/bin/sh
>>>> updated to ksh93: Ok on SPARC and x86
>>>> - bldenv SFWNV with ksh93 updated but not /sbin/sh+/usr/bin/sh updated
>>>> to ksh93: Ok on SPARC and x86 two times for each platform
>>>> - bldenv SFWNV with ksh93 updated _and_ /sbin/sh+/usr/bin/sh updated to
>>>> ksh93: Ok on SPARC and x86
>>>> - "nightly" SFWNV with ksh93 updated but not /sbin/sh+/usr/bin/sh
>>>> updated to ksh93: Ok on SPARC and x86
>>>> - "nightly" SFWNV with ksh93 updated _and_ /sbin/sh+/usr/bin/sh updated
>>>> to ksh93: Ok on SPARC and x86
>>>>
>>>> * Missing tests:
>>>> - SXCE update using ksh93-integration update tarballs and _then_ use
>>>> LiveUpgrade to update to SXCE_next (Milan has to do this since I have no
>>>> disk space)
>>>> - dtrace test suite (tried to contact the dtrace people but they didn't
>>>> reply yet). Can't do it myself since it repeatedly blows-up VMware
>>>> similar to
>>>> http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6609054
>>>> - UNIX98 and UNIX03 std tests for the commands we replace (excluding
>>>> ksh93 itself). Needs to be done by Milan since the tests are for the
>>>> paying audience only... ;-(
>>>> - DIY testing is still pending
>>>> - <milan: What did I forgot ?>
>>>>       
>>> Send me all nightly logs from your builds ;-)
>>>     
>>
>> Erm... I only have the emails, not the full logs anymore (I've removed
>> the trees (not enougth disk space) and therefore the matching log/
>> directories... sorry) ... but I cam regenerate the stuff (only needs a
>> could of days - all builds need to be done serially+manually to handle
>> the disk space restructions here)
>>
>>   
>>> I will do some additional nightlies of ON on my build machines. LU and
>>> VSC testing also. DIY testing is done by Thomas or should I do them?
>>>     
>>
>> I've poked Thomas already for the "DIY" ([1]) ...
>>
>> [1]=For those who don't know what this means: "DIY" is "Do It Yourself",
>> some Sun-internal test system which grabs a BFU tarball, installs it and
>> then runs some tests on the resulting machine...
>>
>> ----
>>
>> Bye,
>> Roland
>>
>>   
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/attachments/20090706/a45a2568/attachment.html>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ksh93_install.log
URL: 
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/attachments/20090706/a45a2568/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: install.ksh
URL: 
<http://mail.opensolaris.org/pipermail/ksh93-integration-discuss/attachments/20090706/a45a2568/attachment-0001.ksh>

Reply via email to