OpenArbor 10.4.7 Test Plan and Report Lockstock 22A
About
OpenArbor Windows 10.4.7
SVN Revision: r101598
SVN Branch Name: 10.4.7
Test Schedule
| Scheduled Test Runs | Start Date | Due Date | Delivered | Percentage Complete |
|---|---|---|---|---|
| Formal Run | 12/02/2022 | 12/09/2022 | 12/09/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.7
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.7
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 | Comments | |
|---|---|---|---|
| OATEST | Windows 7 (64bit) | ||
| OATESTLAP | Windows 10 (64bit) | ||
| TESTW10E1 | Windows 10 (64bit) | ||
| TESTW10E2 | Windows 10 (64bit) | ||
| TESTW10E3 | Windows 10 (64bit) | VM, slow | |
| TESTW7P2 | Windows 7 (64bit) | slow | |
| TESTW10E4 | Windows 10 (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-lockstock-deos-jupiter-20221202 | 1669985532 | arm | DeosZCU102-1 (zcu102) DeosCOMe-cTL6-1 (come-ctl6) DeosIMX8QM (imx8qm) |
BuildPlatformProjects DdsInstallerTest BuildBspDevKit |
OATESTLAP | LCJ | Fail | See Testing Notes |
Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | Windows | PCR:14663 | Known Issue | deos.DdsInstallerTest | All Targets | Media:lockstock22a-setup-log-full.txt Media:lockstock22a-setup-log-filtered.txt |
From AL: Here are the remaining items:
mount: /tmp: Invalid argument configureScoreDoc.py: warning: Cannot find SCORE installation The "mount" issue is a longstanding problem. I could add a filter rule for it, but some solution is probably warranted, I just don't know what it would be. Whether missing SCORE is an error I assume is a customer specific
issue. The message can certainly be filtered out unconditionally if
there is some other way to ensure the content of the DDS is complete.
The filtered output from the setup.log.full file's additional output lines were reviewed by AL and none are show-stoppers. | |
| 2 | Windows | PCR:14694 | Known Issue | BuildBspDevKit | DeosZCU102 (zcu102) | Media:deoszcu102-bsp-dev-kit-failure.txt | See media links for details about why each dev-kit failed to build Tested manually by modifying the build command to '-a zcu102' and the dev kit built without error. | |
| 3 | Windows | Unexpected Failure | BuildBspDevKit | DeosCOMe-cTL6-1 (come-ctl6) | Media:lockstock22a-come_ctl6--bsp-dev-kit-failure.txt | The DDS was rebuilt to remove the come-ctl6-dev-kit since it's broken. | ||
| 4 | Windows | n/a | Known Issue | BuildBspDevKit | DeosIMX8QM (imx8qm) | The openarbor.options file generated by building the dev-kit does not match the installed imx8qm's openarbor.options file. The one built by the dev-kit contains dependencies on dvms components. Work-around instructions will be provided with the shipped dds. |
