OpenArbor 10.4.2 Test Plan and Report Celestial D4d

From DDCIDeos
Jump to navigationJump to search


About

OpenArbor Windows 10.4.2
SVN Revision: r99352
SVN Branch Name: 10.4.2

Test Schedule

Scheduled Test Runs Start Date Due Date Delivered Percentage Complete
Formal Run 08/12/2022 08/15/2022 08/16/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.2

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.2

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-20220812 1660349914 ppc DeosCelestial-2 (celestial) PlatformIntegration TESTW10E1 LCJ Pass 87 failed of 200
See Testing Notes
Deos DDS-docker-celestial-deos-jupiter-20220812 1660349914 ppc DeosCelestial-2 (celestial) PlatformIntegration testlinux02 LCJ, NH Pass See Testing Notes


Testing Notes

ID Priority OS PCR Status Affected Tests Target Screenshot Comments
1 Windows
Linux
DDCI_PCR:4041 Known Issue DeosOptionTabs.integrationToolTabTest All Targets binder.xml files are not currently being validated in OpenArbor.
2 Windows
Linux
Expected Failure Debug.trasher
Debug.worker
Run.trasher
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
Linux
DDCI_PCR:4483 Known Issue Run.ist-partition1
Run.blackboard_event
Run.ist-partition-1
Run.rtems-hm-partition1
Debug.blackboard_event
Debug.ist-partition-1
Debug.rtems-hm-partition1
DeosCelestial (celestial) Media:celestial-fastestPeriodUsec-slowestPeriodUsec-failures.txt pi: Error #1: Caused by feature provider content to file (/desk/platform/celestial/etc/platreg.pi.xml): Scheduler (ist-partition-1) has a fastestPeriodUsec (12500) that is not one of the supported periods. Supported periods are: [20000, 40000, 80000, 160000]

pi: Error #2: Caused by feature provider content to file (/desk/platform/celestial/etc/platreg.pi.xml): Scheduler (ist-partition-1) has a slowestPeriodUsec (12500) that is not one of the supported periods. Supported periods are: [20000, 40000, 80000, 160000]
Fixed in OA 10.4.3

4 Windows
Linux
DDCI_PCR:4483 Known Issue Run.arinc653-partition
Run.buffer_semaphore
Run.cffs_demo
Run.cffs_logbook_partition1
Run.cffs_logbook_partition2
Run.custom-io-partition1
Run.custom-io-partition2
Run.demo653
Run.health_monitor
Run.ipc-partition1
Run.ipc-partition2
Run.ipc-partition3
Run.ipc-partition4
Run.ist-partition1
Run.ist-partition2
Run.multi_partition1
Run.multi_partition2
Run.rtems-partition1
Run.rtems-partition2
Run.rtems-partition3
Run.rtems-partition4
Run.sockets653
Debug.arinc653-partition
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.health_monitor
Debug.ipc-partition1
Debug.ipc-partition2
Debug.ipc-partition3
Debug.ipc-partition4
Debug.ist-partition1
Debug.ist-partition2
Debug.multi_partition1
Debug.multi_partition2
Debug.rtems-partition1
Debug.rtems-partition2
Debug.rtems-partition3
Debug.rtems-partition4
Debug.sockets653
MulticoreIntegration
StatusMonitor
DeosCelestial (celestial) Media:celestial-window-gap-failures.txt pi: Error #1: WAT (default-wat) contains a gap or collision of pi.xml defined windows: window at (37500..42499) and window at (40000..59999)

pi: Error #2: WAT (default-wat) contains a gap or collision of pi.xml defined windows: window at (40000..59999) and window at (42500..49999)
pi: Error #3: WAT (default-wat) contains a gap or collision of pi.xml defined windows: window at (55000..39999) and window at (60000..62499)
pi: Error #4: WAT (default-wat) contains a gap or collision of pi.xml defined windows: window at (137500..142499) and window at (140000..159999)
pi: Error #5: WAT (default-wat) contains a gap or collision of pi.xml defined windows: window at (140000..159999) and window at (142500..149999)
Fixed in OA 10.4.3

5 Windows
Linux
DDCI_PCR:4483 Known Issue Run.a-deos-process
Run.hybrid-io-partition1
Run.ioi-simple-consumer
Run.ioi-simple-producer
Debug.a-deos-process
Debug.hybrid-io-partition1
Debug.ioi-simple-consumer
Debug.ioi-simple-producer
Deos653GdbTest
Run.mutexes
DeosCelestial (celestial) Media:celestial-systemTickUsec-failures.txt pi: Error #1: Feature set (ioi-feature-set), feature (oncePerPlatform) has an assert action that returned false: Table.field (platformAttributes.systemTickUsec), value (12500), scope () has a value of (20000)
Fixed in OA 10.4.3
6 Windows
Linux
PCR:14468 Known Issue Debug.multi-wat-critical-process
Debug.multi-wat-process2
Debug.multi-wat-process3
Debug.multi-wat-process4
Run.multi-wat-critical-process
Run.multi-wat-process2
Run.multi-wat-process3
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)
pi: Error #3: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (26000..32499) and window at (40000..41999)
pi: Error #4: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (46000..52499) and window at (60000..61999)
pi: Error #5: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (66000..72499) and window at (80000..81999)
pi: Error #6: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (86000..92499) and window at (100000..101999)
pi: Error #7: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (106000..112499) and window at (120000..121999)
pi: Error #8: WAT (normal-wat) contains a gap or collision of pi.xml defined windows: window at (126000..132499) and window at (140000..141999)
The multi-wat.fp.xml.4core feature provider file is configured for a platform with a single core enabled and with a system tick interval of 12500 matching most DDC-I reference platforms.

7 Windows
Linux
DDCI_PCR:4480 Known Issue Run.mms_partition1
Run.mms_partition2
Run.mms_partition3
Run.mms_partition4
Debug.mms_partition1
Debug.mms_partition2
Debug.mms_partition3
Debug.mms_partition4
DeosCelestial (celestial) Media:celestial-mms-partition-failures.txt pi: Error #1: Feature set (deos653UserGroup), feature (oncePerPlatform) has an assert action that returned false: Table.field (windowActivationTable.name), value (normal-schedule), scope (name = 'normal-schedule')

pi: Error #2: Feature set (deos653UserGroup), feature (oncePerPlatform) has an assert action that returned false: Table.field (windowActivationTable.name), value (reconfig-schedule), scope (name = 'reconfig-schedule')
Fixed in OA 10.4.3

8 Windows
Linux
DDCI_PCR:4534 Known Issue Run.mutexes DeosCelestial (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.
9 Windows
Linux
Testing Note Time Examples
TDL Examples
DeosCelestial (celestial) The Time and TDL examples were not tested. They were intentionally not included in this DDS.
10 Windows
Linux
DDCI_PCR:4482 Known Issue Run.di2c-nxp-read
Run.di2c-nxp-write
DeosCelestial (celestial) OA Test Update needed to provide expected output patterns for these examples.
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
Linux
DDCI_PCR:4536 Known Issue Run.multicast-ist-ioi DeosCelestial (celestial) OA test update needed to provide expected output pattern for the new example.
13 Linux DDCI_PCR:4538 Known Issue LinkedResources.testSymbolicLinkProjects DeosCelestial (celestial) Media:sf_temp_testlinux02.png Test is failing due to incorrect test resource folders on testlinux02. This test passed on Windows.