OpenArbor 10.4.3 Test Plan and Report Celestial D4e
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 | 09-06-2022 | 09-08-2022 | 09-08-2022 | 100% |
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-20220902 | 1662155091 | ppc | DeosCelestial-2 (celestial) | platformIntegration | OATESTLAP | LCJ | Known Issue | See Testing Notes |
| Deos | DDS-celestial-deos-jupiter-20220902 | 1662155091 | ppc | QEMU-PPC (qemu-ppc) | Launcher | OATEST | LCJ | Known Issue | See Testing Notes |
| Deos | DDS-docker-celestial-deos-jupiter-20220902 | 1662155091 | ppc | QEMU-PPC (qemu-ppc) | Launcher | testlinux01 | LCJ | Known Issue | See Testing Notes |
| Deos | DDS-docker-celestial-deos-jupiter-20220902 | 1662155091 | ppc | DeosCelestial-2 (celestial) | Launcher | testlinux02 | LCJ | Known Issue | See Testing Notes |
| Deos | DDS-docker-celestial-deos-jupiter-20220906 | 1662494800 | ppc | DeosCelestial-4 (celestial) | platformIntegration | testlinux01 | NH | Known Issue | See Testing Notes |
| Deos | DDS-celestial-deos-jupiter-20220906 | 1662494800 | ppc | DeosCelestial-4 (celestial) | platformIntegration | OATESTLap | NH | Known Issue | See Testing Notes |
Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | Windows Linux |
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 |
DeosCelestial-4 (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. | |
| 2 | Windows Linux |
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-4 (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) | |
| 3 | Windows Linux |
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. | ||
| 4 | Windows Linux |
DDCI_PCR:4548 PCR:14501 |
Known Issue | Run.cffs_logbook_partition1 Run.cffs_logbook_partition2 |
DeosCelestial-4 (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. | |
| 5 | Windows Linux |
PCR:14500 | Known Issue | compileRunDebug.Deos653GdbTest | DeosCelestial-4 (celestial) | Media:deos653GdbTest-before-setting-bp.png Media:deos653GdbTest-after-hitting-bp.png 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. | |
| 6 | Windows Linux |
DDCI_PCR:4537 | Known Issue | ExternalDebugging.noLoadListMfs | DeosCelestial-4 (celestial) | FTP compare of files between target/host takes too long Update the OA test to wait longer | ||
| 7 | Windows Linux |
PCR:14500 | Known Issue | Debug.a-deos-process Debug.arinc653-partition Debug.blackboard_event Debug.buffer_semaphore Debug.cffs_demo Debug.cffs_logbook_partition1 Debug.cffs_logbook_partition2 Debug.custom-io-partition1 Debug.custom-io-partition2 Debug.demo653 Debug.except Debug.health_monitor Debug.hello-world-ist Debug.hybrid-io-partition1 Debug.ipc-partition1 Debug.ipc-partition2 Debug.ipc-partition3 Debug.ipc-partition4 Debug.mms_partition1 Debug.mms_partition2 Debug.mms_partition3 Debug.multi_partition1 Debug.multi_partition2<brDebug.photon Debug.rtems-partition1 Debug.rtems-partition2 Debug.rtems-partition3 Debug.rtems-partition4 Debug.rtems-socket-example Debug.semaphore-sharedQ2 Debug.sockets653 Debug.stacks Debug.Ddeos653GdbTest 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. | |
| 8 | Windows Linux |
PCR:14500 | Known Issue | mld.Call mld.MultiThread mld.StepOperatios.basic mld.commands.EnableDisableTrace mld.commands.Go mld.commands.SetBreakAtAddressCounter mld.expression.ExpressionFormatting |
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. | |
| 9 | Windows Linux |
Expected Failure | BuildAll.di2c-nxp-read Debug.di2c-nxp-read Run.di2c-nxp-read BuildAll.di2c-nxp-write Debug.di2c-nxp-write Run.di2c-nxp-write BuildAll.espi-nxp-read Debug.espi-nxp-read Run.espi-nxp-read BuildAll.espi-nxp-write Debug.espi-nxp-write Run.espi-nxp-write |
QEMU-PPC (qemu-ppc) | Media:di2c-nxp-read-qemu-ppc-failure.txt Media:di2c-nxp-write-qemu-ppc-failure.txt Media:espi-nxp-read-qemu-ppc-failure.txt Media:espi-nxp-write-qemu-ppc-failure.txt |
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). | ||
| 10 | Windows Linux |
Expected Failure | BuildAll.gpio-nai-fpga-demo Run.gpio-nai-fpga-demo Debug.gpio-nai-fpga-demo |
QEMU-PPC (qemu-ppc) | Media:gpio-nai-fpga-demo-qemu-ppc-failure.txt | These examples are only expected to run when integrated with the celestial bsp. | ||
| 11 | Windows Linux |
Expected Failure | BuildAll.serial-echo Debug.serial-echo Run.serial-echo |
QEMU-PPC (qemu-ppc) | Media:serial-echo-qemu-ppc-failure.txt | pi: Error #1: Caused by feature provider content to file (/desk/platform/qemu-ppc/etc/platreg.pi.xml): Process Instance (serial-echo-process) owns undefined memory mapped resource (duart_nxp0) Per CP: This example is specific to nai68ppc2, t2080rdb, or the lsxxx targets. | ||
| 12 | Windows Linux |
Expected Failure | BuildAll.tx-duart-nxp Debug.tx-duart-nxp Run.tx-duart-nxp |
QEMU-PPC (qemu-ppc) | Media:tx-duart-nxp-qemu-ppc-failure.txt | pi: Error #1: Caused by feature provider content to file (/desk/platform/qemu-ppc/etc/platreg.pi.xml): Process Instance (tx-duart-nxp-process) owns undefined memory mapped resource (duart_nxp0) Per CP, this example is not expected to build when integrated into the qemu-ppc bsp. This example is only expected to work for ls1043A, ls1048a, t10xx and de-gpu. | ||
| 13 | Windows Linux |
PCR:14500 | Known Issue | compileRunDebug.MulticoreIntegration | QEMU-PPC (qemu-ppc) | On Windows, after configuring the bsp for multicore, running the ipc-partition1 example, the video stream is blank. On Linux, when launching a debug session on the ipc-partition1 example, issuing a suspend results in an Interrupt Error dialog being displayed. This problem is likely related to #7 above. | ||
| 14 | Windows Linux |
PCR:14500 | Known Issue | Debug.ist-partition-1 | QEMU-PPC (qemu-ppc) | Media:debug-ist-partition-1-failure.png | Integrating the ist-653-to-host-configuration project into the bsp, updating lwip.config and launching a debugging session on the ist-partition-1.exe Gdb reports "Protocol error: QStartNoAcMode" (see screenshot) | |
| 15 | Windows Linux |
PCR:14500 | Known Issue | Debug.ist-partition1 Debug.ist-partition2 |
QEMU-PPC (qemu-ppc) | Media:debug-ist-partition1-failure.png | Integrating the ist-simple-configuration project into the bsp, updating lwip.config and launching a debugging session on the ist-partitionn.exe Gdb reports error message from debugger backend (see screenshot) | |
| 16 | Windows Linux |
Testing Note | Time Examples TDL Examples |
n/a | The Time and TDL examples were not tested. They were intentionally not included in this DDS. | |||
| 17 | Windows Linux |
DDCI_PCR:4538 | Known Issue | LinkedResources.testSymbolicLinkProjects | QEMU-PPC (qemu-ppc) DeosCelestial-4 (celestial) |
Unable to create symbolic link from a linux vm. | ||
| 18 | Linux | DDCI_PCR:4203 | Known Issue | Debug.udp-vs-tcp | DeosCelestial-4 (celestial) | Media:udp-vs-tcp.png | Failed to execute Mi command: -exec-interrupt | |
| 19 | Windows Linux |
DDCI_PCR:4534 | Known Issue | Run.mutexes | DeosCelestial-4 (celestial) | The mutexes output does not match what is expected. "Main Routine Started" is never displayed. The display of the new lwip stacks overwrites the example output of 'Main Routine Started', causing the OA automated test to fail. | ||
| 20 | Linux | Pass | StatusMonitor | DeosCelestial-4 (celestial) | StatusMonitor test gets stuck after enabling 'Auto Update'. It checks to make sure that the Thread table has been updated and the values are changing. Test passes when run manually. | |||
| 21 | Windows | DDCI_PCR:4100 | Known Issue | DeosTargetManager.testCauseColdStart | DeosCelestial-4 (celestial) | Test update needed. | ||
| 22 | Windows | PCR:14500 | Known Issue | MultiProcessDebugging.testBreakpointForSharedObject | DeosCelestial-4 (celestial) | Launching with MLD does not launch the debugger on the duplicated auto-tune.exe (dup-auto-tune.exe). Gets stuck at 'Launching MLD 20%'. | ||
| 23 | Windows | PCR:14500 | Known Issue | ExternalDebugging.partialLoadList ExternalDebugging.noLoadList |
DeosCelestial-4 (celestial) | Media:external-debugging-celestiald4e.png | Unable to click on stack frame [autoTuneWaitUntilNextPeriod], in the first thread. The test expects the first thread to be [autoTuneWaitUntilNextPeriod], but instead the first thread is [waitUntilNextPeriod]. |
