OpenArbor 10.4.4 Test Plan and Report TrickyFish 22C
From DDCIDeos
Jump to navigationJump to search
About
OpenArbor Windows 10.4.4
SVN Revision: r100756
SVN Branch Name: 10.4.4
Test Schedule
| Scheduled Test Runs | Start Date | Due Date | Delivered | Percentage Complete |
|---|---|---|---|---|
| Formal Run | 09/20/2022 | 09/27/2022 | 09/27/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.4
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.4
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-trickyfish-deos-kismet-20220923 | 1663961500 | arm | QEMU-ARM (qemu-arm) | Launcher | OATESTLAP | NH | Pass | See Testing Notes |
| Deos | DDS-trickyfish-deos-kismet-20220923 | 1663961500 | arm | DeosIMX8QM (imx8qm) | platformIntegration | TESTW10E1 | NH | Pass | See Testing Notes |
Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | 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. | ||
| 2 | Windows | DDCI_PCR:4051 | Known Issue | ProjectConverter | QEMU‑ARM(qemu‑arm) | Test update is needed. | ||
| 3 | Windows | PCR:14080 | Known Issue | CacheTrasher | QEMU-ARM(qemu-arm) | Media:cacheTrasher-utl-details.png | Update Target load times out when attempting to run the cache trasher example. The test waits 60 seconds for the Update Target Load and reconnection to the Load List Manager to complete It takes longer than that, which is not expected. Tried manually and had same result - time out waiting for the update target load to complete. I tried manually creating a pal-ext-stub project in the workspace, but still have a time out error connecting to the load list manager after the update target load. I put a copy of the workspace here: \\nx3000\openarbor\Integration\workspace-cache-trasher.zip | |
| 4 | Windows | PCR:13694 | Known Issue | BuildAll.dvmssimple‑with‑exfat BuildAll.dvmssimple‑with‑journaled‑exfat BuildAll.vfile_demo BuildAll.vfile_logbook_partition1 Debug.dvmssimple-with-exfat Debug.dvmssimple-with-journaled-exfat Debug.vfile_demo Debug.vfile_logbook_partition1 Run.dvmssimple-with-exfat Run.dvmssimple-with-journaled-exfat Run.vfile_demo Run.vfile_logbook_partition1 |
QEMU-ARM(qemu-arm) | Media:trickyfish22c-time-failure.txt | Error #1: Add record has failed. Unable to invoke Feature Set (libtime) Feature (oncePerPlatform): Adding memoryMappedResource named TIME failed. That memoryMappedResource already exists, but the value for field startAddress differs (1155858432, 0). A workaround to copy for editing the platreg.pi.xml file, and remove the TIME and TIME_CONTROL memory mapped resources. PCR 13694's description mentions this pcr can't be fixed until the SMO based implementation in vfile is ready. | |
| 5 | Windows | DDCI_PCR:2608 | Known Issue | VariablesAndExpressionsViews.stringEditing | QEMU-ARM(qemu-arm) | OpenArbor should deal with large strings in slices for both display and assignment. | ||
| 6 | Windows | DDCI_PCR:4572 | Known Issue | TimeMapUI | QEMU-ARM(qemu-arm) | Test update is needed to more accurately retrieve time map information. | ||
| 7 | Windows | Expected Failure | CffsMal | DeosIMX8QM (imx8qm) | Mal file: [C:\oaTestHarness\workspace\DDS-list\DDS-trickyfish-deos-kismet-20220923\desk\etc\cffs-emmc-a.cd.xml] does not exist in the DDS desk\etc folder. |
