Hi Erik,

Erik LaFever wrote:
> Jan Damborsky wrote:
>> Glenn Lagasse wrote:
>>> * Karen Tung (Karen.Tung at Sun.COM) wrote:
>>>  >
>>>>> Does this mean that the above would also get printed to the
>>>>> screen? If so, I think it's too long and confusing.
>>>>> How about if this was only printed to the detailed log and
>>>>> something simpler to the simple log and the screen?
>>>>>
>>>>> Jean
>>>> Depending on how we do it, we can certainly only print the command
>>>> to the detail log, and not to
>>>> the screen or the simple log at all.  Even just printing them to the
>>>> detail log, I am not sure whether all
>>>> the extra output will confuse people and let other useful data be 
>>>> missed.
>>>
>>> We've already got one report that it's confusing.  Erik Lafever ran 
>>> into
>>> this while doing DC regression testing for VMC.
>>
>> Do you happen to know, what was the reason those messages were found
>> confusing - was it due to the misleading prefix or were there other
>> reasons ?
> They were following a pkg: prefix and I was looking at them in a terminal
> window which was wrapping the message over several lines.  This was 
> followed
> by a Traceback that was hiding the string that I was looking for which
> identified the root cause of the failure.  I have a test that inserts 
> a package
> name (which does not exist on the publisher) into the pkg list.  The 
> error that used
> to be in the logs identified the package that was causing the 
> problem.  Now there is a
> Traceback that reports a general error without identifying the package 
> that was the
> problem.  This is seen the the VMC bits when regression testing DC.

I have given this try for standard x86 DC AI build with latest DC bits
(based on slim_source tip646). When non-existing package 'SUNWbge_foo'
was added to the list of packages, DC failed with following messages
on console:

# /usr/bin/distro_const build ai_x86_7057_128_Erik.xml
/usr/share/distro_const/DC-manifest.defval.xml validates
/tmp/ai_x86_7057_128_Erik_temp_21533.xml validates
Simple Log: 
/export/home/dc/ai/ai_x86_7057_128_noext_package/logs/simple-log-2009-11-23-14-18-33
Detail Log: 
/export/home/dc/ai/ai_x86_7057_128_noext_package/logs/detail-log-2009-11-23-14-18-33
Build started Mon Nov 23 14:18:33 2009
Distribution name: automated_installer_image
Build Area dataset: rpool/dc/ai/ai_x86_7057_128_noext_package
Build Area mount point: /export/home/dc/ai/ai_x86_7057_128_noext_package
==== im-pop: Populate the image with packages
Initializing the IPS package image area: 
/export/home/dc/ai/ai_x86_7057_128_noext_package/build_data/pkg_image
Setting preferred authority: opensolaris.org
    Origin repository: http://tio.czech:10128
Verifying the contents of the IPS repository
pkg: no packages matching 'SUNWbge_foo' known
Unable to verify the contents of the specified IPS repository
Build completed Mon Nov 23 14:18:52 2009
Build failed.


And detailed log file looks like:


Build started Mon Nov 23 14:18:33 2009
Distribution name: automated_installer_image
Build Area dataset: rpool/dc/ai/ai_x86_7057_128_noext_package
Build Area mount point: /export/home/dc/ai/ai_x86_7057_128_noext_package
==== im-pop: Populate the image with packages
Initializing the IPS package image area: 
/export/home/dc/ai/ai_x86_7057_128_noext_package/build_data/pkg_image
Setting preferred authority: opensolaris.org
        Origin repository: http://tio.czech:10128
pkg cmd: /usr/bin/pkg image-create -F -p 
opensolaris.org=http://tio.czech:10128 
/export/home/dc/ai/ai_x86_7057_128_noext_package/build_data/pkg_image
pkg cmd: /usr/bin/pkg -R 
/export/home/dc/ai/ai_x86_7057_128_noext_package/build_data/pkg_image 
set-property flush-content-cache-on-success True
Verifying the contents of the IPS repository
pkg cmd: /usr/bin/pkg -R 
/export/home/dc/ai/ai_x86_7057_128_noext_package/build_data/pkg_image 
list -a entire SUNWcsd SUNWcs BRCMbnx SUNW1394 SUNWPython 
SUNWPython-extra SUNWaac SUNWacc SUNWadmap SUNWadmlib-sysid SUNWadmr 
SUNWadpu320 SUNWafe SUNWagp SUNWahci SUNWamd8111s SUNWamr SUNWarcmsr 
SUNWatfs SUNWatheros SUNWatigfx SUNWauto-install SUNWbash SUNWbge 
SUNWbge_foo SUNWbip SUNWbtool SUNWbzip SUNWcakr SUNWcakrx SUNWcar 
SUNWcarx SUNWced SUNWcfcl SUNWcfpl SUNWchxge SUNWckr SUNWcnetr SUNWcpc 
SUNWcpcu SUNWcpp SUNWcpr SUNWcsl SUNWdcopy SUNWdmfe SUNWdrmr SUNWdsd 
SUNWdtrc SUNWdtrp SUNWesu SUNWfchba SUNWfcip SUNWfcmdb SUNWfcp SUNWfcprt 
SUNWfcsm SUNWfctl SUNWfmd SUNWfss SUNWfwflash SUNWgcmn SUNWgrub SUNWgzip 
SUNWhxge SUNWib SUNWibsdp SUNWibsdpib SUNWibsdpu SUNWigb SUNWinstall 
SUNWinstall-libs SUNWinstall-test SUNWintgige SUNWipf SUNWipkg SUNWipoib 
SUNWipw SUNWiscsi SUNWiscsitgt SUNWislcc SUNWiso-codes SUNWiwh SUNWiwi 
SUNWiwk SUNWixgb SUNWixgbe SUNWkey SUNWkrb SUNWkvm SUNWloc SUNWlsimega 
SUNWluxop SUNWlxml SUNWlxsl SUNWmd SUNWmdb SUNWmegasas SUNWmpathadm 
SUNWmpsvplr SUNWmv88sx SUNWmxfe SUNWnfsc SUNWnfsckr SUNWnge SUNWnis 
SUNWntp SUNWntxn SUNWnvsata SUNWnxge SUNWopenssl SUNWos86r SUNWp7zip 
SUNWpcan SUNWpcelx SUNWpcmci SUNWpcmcu SUNWpcmem SUNWpcser SUNWpcwl 
SUNWpd SUNWpicl SUNWpkgcmds SUNWpm SUNWpool SUNWpsdcr SUNWpsdir 
SUNWpsdpr SUNWqlc SUNWqlcu SUNWralink SUNWrcmdc SUNWrcmds SUNWrge 
SUNWrmodr SUNWrmodu SUNWroute SUNWrpcib SUNWrsync SUNWrtls SUNWrtw 
SUNWrum SUNWsbp2 SUNWscsa1394 SUNWsdcard SUNWses SUNWsfe SUNWsi3124 
SUNWslim-utils SUNWsmbfs SUNWsmbfskr SUNWsmedia SUNWsmpd SUNWsndm 
SUNWsolnm SUNWssh SUNWsshcu SUNWsshd SUNWswmt SUNWtavor SUNWtecla 
SUNWter SUNWtftp SUNWtls SUNWtnetc SUNWtoo SUNWuacm SUNWudf SUNWuedg 
SUNWugen SUNWuksp SUNWukspfw SUNWunzip SUNWuprl SUNWural SUNWusb 
SUNWusbs SUNWwbsup SUNWwget SUNWwlan SUNWwpa SUNWwpi SUNWxcu4 SUNWxge 
SUNWxvmpv SUNWzfs SUNWzfskr SUNWzip SUNWzlib SUNWzone SUNWzyd SUNWmkcd 
SUNWDTraceToolkit
pkg: no packages matching 'SUNWbge_foo' known
Unable to verify the contents of the specified IPS repository
Build completed Mon Nov 23 14:18:52 2009
Build failed.

I agree that 'pkg cmd:' message is really long, but since this is exactly
what DC does, why not have it captured in detailed log file for debugging
purposes ?
Since I don't see the traceback and failure message was not masked
in detailed log file, do you think it might be possible to provide me
with your testing DC bits, so that I could take a look why you see the
Traceback and that failure message is being hidden ?

Thank you,
Jan


Reply via email to