OpenArbor 13.2.1 Test Plan and Report Sales Kismet 25C

From DDCIDeos
Jump to navigationJump to search


About

OpenArbor Windows/Linux 13.2.1
SVN Revision: r112319
SVN Branch Name: 13.2.1

Test Schedule

Scheduled Test Runs Start Date Due Date Delivered Percentage Complete
Formal TBD TBD TBD 1%

Introduction

The automated test suites for Eclipse, supports Eclipse 2025-03-R, 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_13.2.1

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\Release13.2.1

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.
Must Fix The issue with this test must be fixed prior to a release to a customer.
Not scheduled to be tested for this release.
X Scheduled to be tested for this release.
Fail The test failed. The problem causing the failure has been fixed, but the entry will remain on the report for documentation purposes.
Not Supported.

Test Machines

Machine OS Comments
OATESTLAP Windows 10 (64bit)
OATEST Windows 11 (64bit)
TESTW10E1 Windows 10 (64bit)
TESTW10E2 Windows 10 (64bit)
testlinux01 Linux (64bit)
testlinux02 Linux (64bit)
OAWin11-01 WSL
OAWin11-02 WSL
OAWin11-03 WSL
OAWin11-04 WSL
OAWin11-05 WSL
OALinux01 Linux (64bit) LCJ Linux development
OALinux02 Linux (64bit)
OALinux03 Linux (64bit)
OALinux04 Linux (64bit) Actual Linux Machine - fast!
OATEST-W11VM Windows 11 (64bit) Unusable
media:oatest-w11vm.txt
TESTW10E3 Windows 10 (64bit) VM, slow
TESTW10E4 Windows 10 (64bit) Unusable
media:testw10e4.txt
TESTW11E1 Windows 11 (64bit) Unusable
media:testw11e1.txt
OATEST Windows 7 (64bit) Retired
TESTW7P2 Windows 7 (64bit) Retired

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-docker-sales-deos-kismet-20251218 TBD arm DeosZCU102-3 (zcu102) PlatformIntegration OAWin11-01 KT Fail Failed: 15 Passed: 185 Unrun: 0 Total: 201 Not Allowed: 18
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD arm DeosNAI68ARM2-1 (nai-ultrascale) PlatformIntegration testlinux01 KT Fail Failed: 30 Passed: 208 Unrun: 0 Total: 238 Not Allowed: 16
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD aarch64 DeosZCU102-1 (zcu102-aarch64) MiniPlatformIntegration oalinux02 KT Fail Failed: 8 Passed: 74 Unrun: 0 Total: 82 Not Allowed: 9
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD aarch64 DeosNAI68ARM2-2 (nai-ultrascale-aarch64) PlatformIntegration testlinux01 KT Fail Failed: 21 Passed: 210 Unrun: 0 Total: 231 Not Allowed: 23
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD arm DeosLS1043ARDB-1 (ls1043ardb) PlatformIntegration oalinux02 KT In progress Failed: 20 Passed: 219 Unrun: 0 Total: 239 Not Allowed: 15
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD arm DeosLS1088ARDB-1 (ls10x8ardb) MiniPlatformIntegration oalinux04 KT Fail Failed: 6 Passed: 77 Unrun: 0 Total: 83 Not Allowed: 7
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD arm DeosT1042D4RDB-1 (t10xx) PlatformIntegration oalinux02 KT Fail Failed: 18 Passed: 215 Unrun: 0 Total: 233 Not Allowed: 25
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD x86_64 DeosCOMe-cTL6-2 (come-ctl6-x86_64) PlatformIntegration oalinux04 KT Fail Failed: 14 Passed: 162 Unrun: 0 Total: 176 Not Allowed: 25
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD x86_64 DeosNAI68INT6-1 (nai68int6-x86_64) PlatformIntegration oalinux03 KT Fail Failed: 26 Passed: 203 Unrun: 0 Total: 229 Not Allowed: 25
See Testing Notes
Deos DDS-docker-sales-deos-kismet-20251218 TBD arm DeosIMX8QM (imx8qm) PlatformIntegration oalinux04 KT Fail Failed: 19 Passed: 217 Unrun: 0 Total: 236 Not Allowed: 18
See Testing Notes

Testing Notes

ID Priority OS PCR Status Affected Tests Target Screenshot Comments
1 CP Linux DDCI_PCR:5530 Fail dvmsbasher-with-exfat
dvmsbasher-with-journaled-exfat
DvmsMal.dvms-basher
All targets media:sales25c-kismet-nai68int6-x86-64-Build-dvmsbasher-with-exfat-log-12-19-2025.txt Error: 'struct dirent' has no member named 'name'; did you mean 'd_name'? dvms-demo.cpp /dvmsbasher-with-exfat/code line 323

There are 90 warnings for a deprecated print function:
warning: 'int fdprintf(int, const char*, ...)' is deprecated: Use dprintf instead. [-Wdeprecated-declarations]
79 | fdprintf(videofd,"DEMO_DISK: %s\n",disk);

3 Linux DDCI_PCR:TBD TBD Debug.mms_partition1
Debug.mms_partition2
Debug.mms_partition3
Debug.mms_partition4
Run.mms_partition1
Run.mms_partition2
Run.mms_partition3
Run.mms_partition4
DeosNAI68ARM2-1 (nai-ultrascale)
DeosZCU102-3 (zcu102)
DeosT1042D4RDB-1 (t10xx)
DeosNAI68INT6-1 (nai68int6-x86_64)
DeosNAI68ARM2-2 (nai-ultrascale-aarch64)
DeosLS1043ARDB-1 (ls1043ardb)
DeosIMX8QM (imx8qm)
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-mms_partition1-testLog-20251219.txt loading examples onto platform cause build errors:

pi: Error #1: The window starting at (0) in WAT (default-wat) does not have a scheduler for every core.
pi: Error #2: The window starting at (5000) in WAT (default-wat) does not have a scheduler for every core.
pi: Error #3: The window starting at (12500) in WAT (default-wat) does not have a scheduler for every core.
pi: Error #4: The window starting at (17500) in WAT (default-wat) does not have a scheduler for every core.
pi: Error #5: The window starting at (25000) in WAT (default-wat) does not have a scheduler for every core.

RLF: platform has 2 cores. Is this a test issue that it's using the 1core files?
KT 1-6-25: Confirmed this is a test issue, fixed under https://deos.ddci.com/ddcibugzilla/show_bug.cgi?id=5518 (comment #11) and re-running.

4 Linux PCR:16784 Known Failure Debug.zlib-compress
Run.zlib-compress
Debug.zlib-uncompress
Run.zlib-uncompress
All targets media:zhangmen-kismet-come-ctl6-x86_64-Debug-zlib-compress-log-12-16-2025.txt Build error when examples are integrated into the platform project:

Error: Process Template (zlib-compress) is using Feature (deos-zlib) in Feature Set (deos-zlib), and required parameter (processInstanceName) is not specified.
Error: Process Template (zlib-uncompress) is using Feature (deos-zlib) in Feature Set (deos-zlib), and required parameter (processInstanceName) is not specified.

Media/Comment taken from entry #3 of https://deos.ddci.com/ddciWiki/OpenArbor_13.2.1_Test_Plan_and_Report_Zhangmen_Kismet_D3.

5 Linux DDCI_PCR:4593 Known Failure StatusMonitor All targets media:sterling-25a-kismet-naiUltrascale-statusMonitor-Log-10022025txt.txt FAIL Wed Oct 01 21:12:13 MST 2025: Pool Low Water Mark value changed

Note: media taken from entry #5 of https://deos.ddci.com/ddciWiki/OpenArbor_13.1.0_Test_Plan_and_Report_Throne_C1C.

6 Linux DDCI_PCR:TBD Fail Debug.nai-i2c-read-write
Run.nai-i2c-read-write
DeosNAI68ARM2-1 (nai-ultrascale)
DeosNAI68ARM2-2 (nai-ultrascale-aarch64)
DeosLS1043ARDB-1 (ls1043ardb)
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-nai-i2c-read-write-testLog-20251219.txt example has build errors:

../../../code/nai-i2c-read-write.cpp:11:10: fatal error: fpga_nai_prl.h: No such file or directory
11 #include <fpga_nai_prl.h>

RLF: currently nai-fpga-prl is onl shipped in katerina and savianos DDS. Need to decide if that should be added to Sales, and if so via customer-sales or nai-ultrascale package.

7 Linux DDCI_PCR:TBD Fail Run.uart-coordination-partition
Run.uart-partition-1
Run.uart-partition-2
Run.uart-single-partition
All targets media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-uart-coordination-partition-testLog-20251219.txt
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-uart-partition-1-testLog-20251219.txt
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-uart-partition-2-testLog-20251219.txt
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-uart-single-partition-testLog-20251219.txt
The test system does not have regex set for these examples yet. Need to meet with example developers to discuss expected output.
8 Linux DDCI_PCR:TBD Fail Deos653GdbTest DeosNAI68ARM2-1 (nai-ultrascale)
DeosZCU102-1 (zcu102-aarch64)
DeosZCU102-3 (zcu102)
DeosT1042D4RDB-1 (t10xx)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosNAI68INT6-1 (nai68int6-x86_64)
DeosNAI68ARM2-2 (nai-ultrascale-aarch64)
DeosLS1043ARDB-1 (ls1043ardb)
DeosIMX8QM (imx8qm)
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Deos653GdbTest-testLog-20251222.txt
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Deos653GdbTest-threadsNeverHitBp-20251222.png
In the debug session, the threads never hit the breakpoint as expected. Steps to reproduce:

(1) set demo653_configuration dependency on platform
(2) cold start -> hit 'Edit Attributes' button, set registry to platreg, check 'honor debug services' and 'force cold start' boxes, hit 'OK'
(3) select 'demo653' in project tree, right click, Debug As->Debug Deos Executable Using Gdb
*debug is suspended at start*
(4) open demo653.cpp
(5) set bp on line 142: thisProcessLoopCount++;
(6) resume the debug
*breakpoint will not be hit by any threads*

8.1 Linux DDCI_PCR:TBD Fail GdbBreakAtStartup.653
GdbBreakAtStartup.rma
GdbBreakAtStartup.rtems
DeosNAI68ARM2-1 (nai-ultrascale)
DeosZCU102-1 (zcu102-aarch64)
DeosT1042D4RDB-1 (t10xx)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosNAI68INT6-1 (nai68int6-x86_64)
DeosNAI68ARM2-2 (nai-ultrascale-aarch64)
DeosLS1043ARDB-1 (ls1043ardb)
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-GdbBreakAtStartup653-testLog-20251222.txt Similar issue to entry #8. In the debug session, the threads never hit the breakpoint as expected. Steps to reproduce for the 653 subtest:

(1) In platform project, add a dependency on ipc-653-configuration
(2) In ipc-653-configuration's ipc_config.653.xml file set BreakAtStartup="true"
(3) In ipc-653-configuration's ipc_config.653.xml file set InDebugSet=false for each partition (ipc-partition1,ipc-partition2,ipc-partition3,ipc-partition4)
(4) From the Status Monitor, launch a debugging session on ipc-partition1.exe
(5) One of the first thread's items in the stack frame should contain "debuggerSuspend"
(6) Press Resume (Go). The test expects the _start breakpoint to be hit, but it never occurs. Test fails when Suspend is not seen.

9 Linux DDCI_PCR:TBD Expected Deviation MulticoreIntegration DeosNAI68ARM2-1 (nai-ultrascale)
DeosT1042D4RDB-1 (t10xx)
DeosNAI68ARM2-2 (nai-ultrascale-aarch64)
DeosIMX8QM (imx8qm)
media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-MulticoreIntegration-testLog-20251222.txt *** FAIL Fri Dec 19 11:21:41 MST 2025: Multicore Integration testing cannot be performed on the nai-ultrascale platform, it's maxCoreIndex is: 0x1
10 Linux DDCI_PCR:TBD Fail Run.vfile_demo All targets media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-Run-vfileDemo-testLog-20251222.txt Error reported in video stream:

tester1 Test - 1: OPEN_DIRECTORY: 'fs1rw' - dir_id: 1 - NOT OK! - ret_code: 3 -
errno: 20 (0x14)

11 Linux DDCI_PCR:5527 Known Failure NewProjectValidation.createNewMakefileProjectWithExistingCode DeosNAI68ARM2-1 (nai-ultrascale) media:sales-25c-kismet-deos-nai68arm2-1-nai-ultrascale-NewProjectValidation-createNewMakefileProjectWithExistingCode-testLog-20251222.txt [12-23-25 KT]: Test passes after updates.

The fail is due to a test issue. A makefile creates an error and warning that should show up in the Problems View, and the test checks they are present. The check for the warning fails, because the Problems View filter is set to only show 100 items, and the warning is not in the first 100 items.

The test should be updated to uncheck the 'limit to 100 items' box in the filter settings for the problems view for this test, and re-check it during test cleanup.

12 Linux DDCI_PCR:5281 (comment #54) Known Failure Run.vfile_logbook_partition1 DeosCOMe-cTL6-2 (come-ctl6-x86_64)
DeosNAI68INT6-1 (nai68int6-x86_64)
DeosNAI68ARM2-2 (nai-ultrascale-aarch64)
media:sales-informal-kismet-qemu-aarch64-vfile_logbook_partition1-08-08-2025.txt Unexpected output:
Arinc 653 Logbook Partition 1 Test                                              
Volume: /mount/hd0 formatting...OK  OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, 
OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK, OK,Line Number 302 -
 NOT OK! - ret_code: 0,  OK,Read Msg = ing, Testing!                            
Exp Msg  = Testing, Testing!                                                    
Msg Size = 104 Exp = 17                                                         
Line Number 302 - NOT OK! - ret_code: -1 

Note: media/comment taken from entry #10 of: https://deos.ddci.com/ddciWiki/OpenArbor_13.1.0_Test_Plan_and_Informal_Report.