Hi, Ethan, Ethan Quach ??: > Jeffrey, > > I'm filling in for Sundar this week, so just catching up. I have > a couple of questions/comments about the test results ... > > 1. What does the result code of "Uninitialized" mean? Are > these failures we need to look at and address as bugs? > What does the result code of "Other" mean?
Thanks very much to look into the report details. The "Uninitialized" of this test suite happened when adding a test manifest to AI service, caused by 2 reasons: 1. product bugs that failed to add certain manifest to service. 2. Test env of last execution is not very well cleaned Now, I am manually verifying above cases if "Uninitialized" happened, I will improve the clean up process so only manifest bugs will cause uninitialized. "Other" caused by 2 reasons: 1. Test case aborted by unexpected reason. ( We will improve individual case to avoid them) 2. Disk partition features not supported on SPARC platform. These cases should be reported as Unsupported, unfortunately, the TET/CTI report harness can not identify it.) > > 2. In the summary.html Details section, it would be nice if the > Fail/Other column was split out into three columns -- > Fail, Unintialized, and Other so that we can quickly find the > kind we're looking for. Yes, 3 columns would be much better, we plan to improve the report in 2 two ways: 1. Enhance TET/CTI report harness to list category in different columns and also identify unsupported cases. 2. We also manually add notation to the failed cases with further detailed info in next test report. > > 3. Just a language nit - "Know Issues" should be "Known Issues" Fixed, thanks. > > >> http://opg-qe.central.sun.com/wiki/index.php/Install_ai:osol-0906-b2 >> >> Those failed cases that maybe bugs are listed in know issues, other >> failed cases caused >> either by test suite itself or execution environment limitation, we will >> continue improve >> the test suite. >> >> Last week's test was based on build 111 release, both x86/sparc, virtual >> box and LDOM >> installation have been tested. >> >> This week, we will upload latest SUNWinstalladm-tool and nightly ai >> image, and also will >> try sparc platform as AI server. >> > > If you're going to be using the same install server, and just > updating the latest SUNWinstalladm-tools pkgs, or even just > updating the entire system, note the Heads-Up message sent > out last week: > > http://www.opensolaris.org/jive/thread.jspa?threadID=99407&tstart=60 > >> BTW, in build 111, I see AI manifest supports install package other than >> default build in repo, >> seems this feature is not from the design doc, also it is not covered by >> our test plan and test suite right >> now. >> > > Need clarification. Are you referring to the list of packages which > are now in the default manifest? i.e: > > <ai_install_packages> > <pkg name="SUNWcsd"/> > <pkg name="SUNWcs"/> > <pkg name="babel_install"/> > <pkg name="entire"/> > </ai_install_packages> > <ai_uninstall_packages> > <pkg name="babel_install"/> > <pkg name="slim_install"/> > </ai_uninstall_packages> > > > > thanks, > -ethan > -- Great Thanks & Best Regards --- Jeffrey Huang SWAN: x51683, Ext: 0086-10-62673683 Solaris QE Group Email: jeffrey.huang at sun.com China Engineering & Research Institute, Sun Microsystems 7/F Chuang Xin Plaza, Tsinghua Science Park, Beijing China
