OpenArbor 12C1 Test Plan and Report

From DDCIDeos
Jump to navigationJump to search


About

OpenArbor – 12C1 Test Plan and Report
OpenArbor Windows 3.7 Build 301
SVN Revision 29971
August 2012

Test Schedule

Formal Test Run Start Date Due Date Delivered Percentage Complete
[2]Deos 08-20-2012 08-24-2012 08-30-2012 100%


Introduction

The automated test suites for Eclipse, generated by RFT, support Eclipse 3.7, which OpenArbor is built upon. The tests were run on

OpenArbor v3.7 build 301.

A list of PCRs corrected for this release is at the end of this document. The Ada, C, C++, Fortran, and Assembly languages will be tested (when applicable).

TESTW7P2, OATEST or T3400DELL will be used to reproduce/fix test failures.


The test logs can be viewed at:

\\nx3000\openarbor\TestResults\Release3.7.0_12C1

Legend

Pass The test passed.
Expected Deviation The test fails and a fix is not going to happen due to technical restrictions or restraints beyond our control.
Known Failure The test fails, but we have plans to fix the problem in a future release.
Fail The test failed.
Not scheduled to be tested for this release.
X Scheduled to be tested for this release.
Not Supported.

Test Machines

Machine OS
OATEST Windows XP
T3400DELL Windows XP
TESTW7P2 Windows 7 (64bit)

Executed Test Runs

The automated OpenArbor Test Suites are executed for each "X" marked in the table below. There are currently two test suites. One suite, Launcher is focused toward executing the entire OpenArbor interface. The second test suite, CompileRunDebug is used to just test compilation, linking, running and debugging the example projects.

Deos Test Runs

GCC Deos C/C++ and TRAC
DDS Release Dry Run Formal Test Test Machine Test Suites Available
Boards
Who Comments
80x86 Hosmer_Deos_Denali T3400DELL Launcher VMware
PPC Hosmer_Deos_Denali T3400DELL Launcher DeosEP8343 2-1
80x86 chino_Deos_FourPeaks 1 Failure
(DF5)
0 failures T3400DELL Launcher VMware BPH
80x86 DeosFit-pc2-1
DeosFit-pc2-2
PPC DeosEP440C
PPC chino_Deos_FourPeaks 1 Failure 0 failures TESTW7P2 Launcher DeosPPC750-1 LCJ
PPC DeosEP8280-1
MIPS chino_Deos_FourPeaks 2 Failure
(KP1)(DF5)
1 Failure
(KP1)
OATEST Launcher QEMU LCJ

Completed PCRs

OpenArbor_12C1#.5B3.5D_Completed_PCRs

Known Problems

(KP1) udp-vs-tcp example fails to build

FAIL com.ddci.openarbortests.compileRunDebug.Build.udp-vs-tcp
FAIL com.ddci.openarbortests.compileRunDebug.BuildAll.udp-vs-tcp
FAIL com.ddci.openarbortests.compileRunDebug.Compile.udp-vs-tcp
FAIL com.ddci.openarbortests.compileRunDebug.Debug.semaphore-sharedQ
FAIL com.ddci.openarbortests.compileRunDebug.Debug.udp-vs-tcp
FAIL com.ddci.openarbortests.compileRunDebug.Run.udp-vs-tcp
FAIL com.ddci.openarbortests.projectOptions.other.dumps.Disassemble.udp-vs-tcp
FAIL com.ddci.openarbortests.projectOptions.other.dumps.DwarfDump.udp-vs-tcp
FAIL com.ddci.openarbortests.projectOptions.other.dumps.ObjectDump.udp-vs-tcp
Unable to build example for MIPS
Per AL: This is because MTL and SAL are not yet ported to MIPS. This won't be fixed for this release.

Failures

None

Testing Notes

None

Corrected Failures

(DF1) com.ddci.openarbortests.compileRunDebug.Debug.semaphore-sharedQ

Unable to debug example -
Initializing debugger
Loaded library: libansi.so
Ready
DF-36-WARNING Not properly connected to program.
DF-42-ERROR Unable to execute this command when not connected to a program.
BC released new kernel examples that resolved this issue.


(DF3) com.ddci.openarbortests.deos.DeosTargetManager

FAIL PCR 1656: suggested hostname for VMware DDCI_PCR:2048
LCJ released a new OpenArbor build 297 that fixed this issue.


(DF4) com.ddci.openarbortests.deos.DeosABCTest.multi

This test fails because the coverage file for the auto-tune-library is not properly generated and displayed. PCR:7550?.
FAIL Output file does not exist: auto-tune-library/output/mips/instrumented/coverageSummary.html
Updated the test to use page aligned start address for all hitmaps.

(DF5) com.ddci.openarbortests.mld.MultiThread

This test fails because the stack frames are not displayed as expected.
An OpenArbor change as well as test update fixed this.