OpenArbor 10.4.7 Test Plan and Report TrickyFish 23A
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 | 02/02/2023 | 02/03/2023 | 02/03/2023 | 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-trickyfish-deos-kismet-20230202 | 1675344521 | arm | DeosSpearMX8-2 (imx8-tf) | PlatformIntegration | OATESTLAP | NH | Pass | 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:trickyfish-23a-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. | |
| 2 | Windows | Expected Failure | Debug.trasher Run.trasher 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. | ||
| 3 | Windows | DDCI_PCR:4593 | Known Issue | deos.StatusMonitor | All Targets | The StatusMonitor test needs an update. The test scenario for 'Pool Low Water Mark value changed' is consistently failing. The test was recently updated to work differently when testing with multiple cores, but it appears the the setting the Reset Pad dialog for the second value is not getting properly set in the dialog (possibly). Manual testing works. |
