OpenArbor 10.4.3 Test Plan and Report Informal
From DDCIDeos
Jump to navigationJump to search
About
OpenArbor Windows 10.4.3
SVN Revision: r100481
SVN Branch Name: 10.4.3
Test Schedule
| Scheduled Test Runs | Start Date | Due Date | Delivered | Percentage Complete |
|---|---|---|---|---|
| Formal Run | TBD | TBD | TBD | 0% |
Introduction
The automated test suites for Eclipse, supports Eclipse 2020-R-12, which OpenArbor is built upon. The tests were run the on build mentioned above.
A list of PCRs corrected for this release can be found here: OpenArbor_10.4.3
See below for a list of machines that will be used to reproduce/fix test failures.
The test logs can be viewed at:
- \\nx3000\openarbor\TestResults\Release10.4.3
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 7 (64bit) | |
| OATESTLAP | Windows 10 (64bit) | |
| TESTW10E1 | Windows 10 (64bit) | |
| TESTW10E2 | Windows 10 (64bit) | |
| TESTW7P2 | Windows 7 (64bit) |
Executed Formal Test Runs
The automated OpenArbor Test Suites are executed for each entry in the table below. The "Test Suites" column will indicate what tests were run. The full set of OpenArbor tests are indicated by the name Launcher. A second test suite, CompileRunDebug is used to just test compilation, linking, running and debugging the example projects. The PlatformIntegration test suite is a small set of tests that exercise the more common operations customers use in interacting with the platform.
| Product | DDS Release | Timestamp | Target Architecture |
Available Boards |
Test Suites | Test Machine | Who | Formal Results |
Comments |
|---|---|---|---|---|---|---|---|---|---|
| Deos | DDS-celestial-deos-jupiter-20220828 | TBD | ppc | DeosCelestial-2 (celestial) | platformIntegration | OATESTLAP | LCJ | X | See Testing Notes |
| Deos | DDS-celestial-deos-jupiter-20220828 | TBD | ppc | QEMU-PPC (qemu-ppc) | Launcher | OATEST | LCJ | X | See Testing Notes |
| Deos | DDS-docker-celestial-deos-jupiter-20220828 | TBD | ppc | QEMU-PPC (qemu-ppc) | Launcher | testlinux01 | LCJ | X | See Testing Notes |
| Deos | DDS-docker-celestial-deos-jupiter-20220828 | TBD | ppc | DeosCelestial-2 (celestial) | Launcher | testlinux02 | LCJ | X | See Testing Notes |
Informal Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | Windows | DDCI_PCR:14475 | Known Issue | BuildAll.get-clock Compile.get-clock Debug.get-clock Run.get-clock MakeExport.get-clock Clean.get-clock |
Deos-Celestial (celestial) | Media:get-clock-build-errors.txt | The Time example get-clock source code has build errors. These examples are expected to run on the celestial bsp. This example was removed from the workspace under test. | |
| 2 | Windows | DDCI_PCR:14475 | Known Issue | BuildAll.set-clock Compile.set-clock Debug.set-clock Run.set-clock MakeExport.set-clock Clean.set-clock |
Deos-Celestial (celestial) | Media:set-clock-build-errors.txt | The Time example set-clock source code has build errors. These examples are expected to run on the celestial bsp. This example was removed from the workspace under test. | |
| 3 | Windows | DDCI_PCR:8379 | Known Issue | BuildAll.harrys-integration-demo Debug.harrys-integration-demo Run.harrys-integration-demo MakeExport.harrys-integration-demo Clean.harrys-integration-demo |
Deos-Celestial (celestial) | Media:harrys-integration-demo-celestial-build-errors.txt | The celestial bsp fails to build when the TDL example harrys-integration-demo is integrated. This is a Harrys customer specific example and should not be tested for the Celestial customer. This example was removed from the workspace under test. | |
| 4 | Windows | DDCI_PCR:8379 DDCI_PCR:11802 |
Known Issue | BuildAll.hosmer-integration-demo-ppc Compile.hosmer-integration-demo-ppc Debug.hosmer-integration-demo-ppc Run.hosmer-integration-demo-ppc MakeExport.hosmer-integration-demo-ppc Clean.hosmer-integration-demo-ppc |
Deos-Celestial (celestial) | Media:hosmer-integration-demo-ppc-build-errors.txt | The TDL example hosmer-integration-demo-ppc source code has build errors. This is a Hosmer customer specific example and should not be tested for the Celestial customer. This example was removed from the workspace under test. | |
| 5 | Windows | DDCI_PCR:4345 | Known Issue | BuildAll.ioi-simple-consumer Debug.ioi-simple-consumer Run.ioi-simple-consumer MakeExport.ioi-simple-consumer Clean.ioi-simple-consumer BuildAll.ioi-simple-data-formatter Debug.ioi-simple-data-formatter Run.ioi-simple-data-formatter MakeExport.ioi-simple-data-formatter Clean.ioi-simple-data-formatter BuildAll.ioi-simple-producer Debug.ioi-simple-producer Run.ioi-simple-producer MakeExport.ioi-simple-producer Clean.ioi-simple-producer |
Deos-Celestial (celestial) | Media:ioi-simple-celestial-build-errors.txt | The IOI example ioi-simple is configured to integrate only with a bsp that as a system tick of 12500. Since the celestial bsp has a system tick rate of 20000, this example was removed from the workspace under test. | |
| 6 | Windows | DDCI_PCR:8379 DDCI_PCR:12879 |
Known Issue | BuildAll.load-crc-test-ppc Compile.load-crc-test-ppc Debug.load-crc-test-ppc Run.load-crc-test-ppc MakeExport.load-crc-test-ppc Clean.load-crc-test-ppc |
Deos-Celestial (celestial) | Media:load-crc-test-ppc-build-errors.txt | The TDL example load-crc-test-ppc source code has build errors. This example is not expected to work on the Celestial bsp. TDL should only be run on boards that have TDL. This example was removed from the workspace under test. | |
| 7 | Windows | PCR:14468 | Known Issue | BuildAll.multi-wat-critical-process Debug.multi-wat-critical-process Run.multi-wat-critical-process BuildAll.multi-wat-process2 Debug.multi-wat-process2 Run.multi-wat-process2 BuildAll.multi-wat-process3 Debug.multi-wat-process3 Run.multi-wat-process3 BuildAll.multi-wat-process4 Debug.multi-wat-process4 Run.multi-wat-process4 |
DeosCelestial (celestial) | Media:updated-multi-wat-configuration-integration-errors.txt | pi: Error #1: WAT (reconfig-wat) contains a gap or collision of pi.xml defined windows: window at (6000..12499) and window at (20000..21999) pi: Error #2: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (6000..12499) and window at (20000..21999) | |
| 8 | Windows | Expected Failure | BuildAll.trasher Debug.trasher Run.trasher BuildAll.worker Debug.worker Run.worker |
All Targets | Media:TrasherWorkerBuildFailure2.png | Platform project fails to build when the Multicore-memory-pools example projects trasher and worker are integrated into the out of the box single core and/or single pool platform. The MulticoreIntegration test performs the BuildAll, Run and Debug tests for the multicore memory pools examples in a multicore/multi memory pool environment. | ||
| 9 | Windows | DDCI_PCR:TBD | Unexpected Failure | Run.cffs_logbook_partition1 Run.cffs_logbook_partition2 |
DeosCelestial (celestial) | Media:run-cffs-logbook-partition-1-output.png | The expected output is not displayed on the Video Stream. These example tests pass when run with QEMU-PPC. These tests passed when informally tested on 8/18. The expected output is getting overwritten by the additional network information displayed on the celestial target. The second ACT network line overwrites this information on line 22. | |
| 10 | Windows | DDCI_PCR:TBD | Unexpected Failure | compileRunDebug.Deos653GdbTest | DeosCelestial (celestial) | Media:deos653-gdb-step-over-fails.txt | After configuring the system ticks to be 12500, launching a debug session on the demo653 example, and issuing a step over after setting bp fails. Thread #2 is not in the Debug View as expected. | |
| 11 | Windows Linux |
DDCI_PCR:4537 | Known Issue | ExternalDebugging.noLoadListMfs | DeosCelestial (celestial) | FTP compare of files between target/host takes too long Update the OA test to wait longer | ||
| 12 | Windows | DDCI_PCR:4545 DDCI_PCR:4345 |
Known Issue | Debug.vfile_demo Run.vfile_demo |
DeosCelestial (celestial) | Media:vfile_demo_integration_errors.txt | The celestial bsp fails to build when this example is integrated into the platform project. The documentation for using these examples are in the /desk/help/vfile-api653p2-examples-user-guide.htm. Reviewing the example user guide, it says to copy for editing the dvms-mal component, but that component is not in the DDS. | |
| 13 | Windows | DDCI_PCR:4545 DDCI_PCR:4345 |
Known Issue | Debug.vfile_logbook_partition1 Run.vfile_logbook_partition1 |
DeosCelestial (celestial) | Media:vfile_logbook_integration_errors.txt | The celestial bsp fails to build when this example is integrated into the platform project. The documentation for using these examples are in the /desk/help/vfile-api653p2-examples-user-guide.htm. Reviewing the example user guide, it says to copy for editing the dvms-mal component, but that component is not in the DDS. | |
| 14 | Windows Linux |
PCR:TBD | Unexpected Failure | compileRunDebug.Debug 40+ examples (debugging with gdb) gdb.LaunchGdbTest |
QEMU-PPC (qemu-ppc) | Media:debug-interrupt-failed.png | Launching a debug session on the examples, and issuing a suspend results in an Interrupt Error dialog being displayed. Also manually tested QEMU-PPC with two different DDS' (celestial and deserteagle) and got the same error. To reproduce (1) integrate blackboard_event into qemu-ppc, (2) Updated Target Load (if needed), (3)debug the .exe with gdb, and (4) click Suspend. This is not a problem on qemu-arm. | |
| 15 | Windows | PCR:TBD | Unexpected Failure | 10+ mld tests | QEMU-PPC (qemu-ppc) | Media:mld_command_queue_log_go_command.txt | MLD fails to respond when specific commands are sent. OpenArbor displays 'Sending Command' in the Progress view, but never gets a response. This behavior was observed when issuing a Step Continue and GO TO FILE POSITION when debugging photon.exe. | |
| 16 | Windows Linux |
Expected Failure | Run.di2c-nxp-read Run.di2c-nxp-write Run.espi-nxp-read Run.espi-nxp-write Debug.di2c-nxp-read Debug.di2c-nxp-write Debug.espi-nxp-read Debug.espi-nxp-write |
QEMU-PPC (qemu-ppc) | The di2c-nxp-read, di2c-nxp-write, espi-nxp-read, and espi-nxp-write projects fail to build. These examples only work on the nai68ppc2 bsp (per CP). | |||
| 17 | Windows Linux |
Expected Failure | Run.gpio-nai-fpga-demo Debug.gpio-nai-fpga-demo |
QEMU-PPC (qemu-ppc) | These examples are only expected to run on DeosCelestial. |
