OpenArbor 13.1.0 Test Plan and Informal Report
About
OpenArbor Windows/Linux 13.1.0
SVN Revision: r111124
SVN Branch Name: mainline
Test Schedule
| Scheduled Test Runs | Start Date | Due Date | Delivered | Percentage Complete |
|---|---|---|---|---|
| Informal | 08-07-2025 | 08-19-2025 | 08-16-2025 | 100% |
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.1.0
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.1.0
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) | NH Linux development backup test machine |
|
| OALinux03 | Linux (64bit) | KT Linux development backup test machine |
|
| 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 | n/a | QEMU-ARM (qemu-arm) | n/a | Launcher | OAWin11-04 | lcj | Fail | Failed: 78 Passed: 659 Unrun: 0 Total: 737 Not Allowed: 45 See testing notes | |
| Deos | n/a | QEMU-PPC (qemu-ppc) | n/a | Launcher | OAWin11-01 | lcj | Fail | Failed: 61 Passed: 676 Unrun: 0 Total: 737 Not Allowed: 45 See testing notes | |
| Deos | n/a | QEMU-AARCH64 (qemu-aarch64) | n/a | Launcher | OALinux04 | lcj | Fail | Failed: 63 Passed: 674 Unrun: 0 Total: 737 Not Allowed: 45 See testing notes | |
| Deos | n/a | DeosS32G274A-2 (s32g2-aarch64) | n/a | Platform Integration | OALinux04 | lcj | Fail | Failed: 18 Passed: 204 Unrun: 0 Total: 227 Not Allowed: 27 See testing notes | |
| Deos | n/a | QEMU-80X86_64 (qemu-80x86_64) | n/a | Launcher | OALinux02 | lcj | Fail | Failed: 63 Passed: 674 Unrun: 0 Total: 737 Not Allowed: 45 See testing notes | |
| Deos | n/a | DeosIMX8QM (imx8qm) | n/a | Launcher | OALinux02 | lcj | Fail | Failed: 36 Passed: 726 Unrun: 0 Total: 762 Not Allowed: 34 See testing notes | |
| Deos | n/a | TBD | n/a | Customer workspace | OALinux04 | lcj | Pass | Test customer workspace here: https://deos.ddci.com/svn/DDCI/support/zhangmen/2425-project-layout-example/ Customer workspace builds cleanly, for details see: media:zhangmen-workspace-build-output.txt | |
| Deos | n/a | QEMU-PPC (qemu-ppc) | n/a | Launcher | OALinux04 | lcj | Fail | Failed: 58 Passed: 688 Unrun: 0 Total: 746 Not Allowed: 45 See testing notes |
Unreleased Packages
The Deos_Zhangmen_D1b wiki page lists the unreleased components that need to be included in the testing.
Linux
The environment for testing was encoded in the bdu64-modular-boot script:https://deos.ddci.com/scm/Deos/maintainer-tools/docker/branches/mainline/bdu64-modular-boot
bdu64-modular-boot --name=dds-docker-sales-deos-kismet-20250710 kismet customer-sales
Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | PZ | Linux | PCR:16078 | Known Failure | BuildAll.arinc653-partition BuildAll.blackboard_event BuildAll.demo653 BuildAll.interrupt BuildAll.vfile-aio-read-write BuildAll.vfile_demo BuildAll.zlib-compress |
DeosIMX8QM(imx8qm) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-imx8qm-BuildAll-arinc653-partition-log-08-06-2025.txt | Error: co-processor offset out of range To reproduce the problem, (1) integrate the example project with the platform project and (2) enable all build variants on the example project. PZ: See PCR 16078, Comment 78 |
| 2 | AL | Linux | DDCI_PCR:5471 | Pass | BuildAll.multi-wat-critical-process BuildAll.multi-wat-process2 BuildAll.multi-wat-process3 BuildAll.multi-wat-process4 Debug.multi-wat-critical-process |
DeosIMX8QM(imx8qm) | media:sales-informal-kismet-imx8qm-BuildAll-multi-wat-critical-process-log-08-06-2025.txt | Errors reported by pi. To reproduce the problem (1) in multi-wat-configuration, copy the content of multi-wat.fp.xml.4core into multi-wat.fp.xml (2) in basecon.pia.xml change number of cores to 4 (3) integrate multi-wat-configuration with the platform project Noted that a rebuild yields a clean build. Noted that changing the integrity key of the .fp.xml file in question did revalidate the .fp.xml file, but did not cause a registry build. pi: Error #1: File (vfile/libvfile-usage.fp.xml) cannot be located. [lcj 14-aug] Reran tests with updated OA/cdproc and the tests passed. |
| 3 | PZ | Linux | PCR:16078 | Known Failure | BuildAll.rtems-cpu-usage BuildAll.rtems-hm-partition1 BuildAll.rtems-partition1 BuildAll.rtems-partition2 BuildAll.rtems-partition3 BuildAll.rtems-partition4 BuildAll.rtems-socket-example |
DeosIMX8QM(imx8qm) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-imx8qm-BuildAll-rtems-cpu-usage-log-08-06-2025.txt | Errors reported during instrumenting examples. To reproduce the problem, (1) integrate the example project with the platform project and (2) enable all build variants on the example project. PZ: See PCR 16078, Comment 78 arm-rtems6-gcc -MP -MMD -B/rtems/tools/arm-rtems6/deos_arm/lib -qrtems -gdwarf-2 -march=armv7-a -mfloat-abi=hard -mfpu=neon -mthumb -fPIC -Wno-psabi -fdata-sections -ffunction-sections -O2 -idirafter/desk/include - idirafter/desk/arm/include -isystem/rtems/tools/arm-rtems6/deos_arm/lib/include -S -o sample.s_ ../../../code/sample.c /desk/bin/abc instrument --format GNU --arch ARM --index abc_index.json --insert ./insert.template sample.s_ -o inst_sample.s_ Opening assembly file sample.s_... Parsing the assembly file sample.s_ for points... Instrumenting assembly on points parsed... Writing output to file inst_sample.s_ Instrumentor Statistics 14 Label Entry Point 5 Load PC-relative Value w/ Immediate Offset 1 Return Subroutine (Branch and Exchange Instruction Set) 6 Subroutine Call 1 Unconditional Branch (uninstrumented) arm-rtems6-gcc -x assembler -c inst_sample.s_ -o sample.o inst_sample.s_: Assembler messages: inst_sample.s_:65: Error: selected processor does not support `adrl r3,.L5' in Thumb mode inst_sample.s_:69: Error: selected processor does not support `adrl r2,.L5+4' in Thumb mode inst_sample.s_:95: Error: selected processor does not support `adrl r6,.L5+8' in Thumb mode inst_sample.s_:364: Error: selected processor does not support `adrl r3,.L8' in Thumb mode inst_sample.s_:384: Error: selected processor does not support `adrl r2,.L8+4' in Thumb mode |
| 4 | AR | Linux | PCR:TBD | Fail | deos.PcieScannerTest | DeosIMX8QM(imx8qm) | media:sales-informal-kismet-imx8qm-PcieScannerTest -log-08-06-2025.txt | Unable to connect to the video stream To reproduce the problem (1) add a dependency on 'pcie-scanner' in the platform project AL spoke with ALR. This is a platform issue being worked by BSP team. No PCR available at this time. |
| 5 | Linux | PCR:16608 | Known Failure | Compile.a-deos-process Compile.arinc653-partition Compile.blackboard_event Compile.buffer_semaphore Compile.cpm-partition1 Compile.cpm-partition2 Compile.custom-io-library Compile.custom-io-partition1 Compile.custom-io-partition2 Compile.demo653 Compile.health_monitor Compile.hybrid-653-library Compile.hybrid-io-partition1 Compile.hybrid-ioi-library Compile.interrupt Compile.ipc-partition1 Compile.ipc-partition2 Compile.ipc-partition3 Compile.ipc-partition4 Compile.ist-partition-1 Compile.ist-partition1 Compile.ist-partition2 Compile.multi_partition1 Compile.multi_partition2 Compile.rtems-hm-partition1 Compile.rtems-partition1 Compile.rtems-partition2 Compile.rtems-partition3 Compile.rtems-partition4 Compile.sockets653 Compile.vfile_demo |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-Compile-a-deos-process-log-08-08-2025.txt | When integrated with a platform project, applications that have a 653.xml file cdproc-makefile reports: Warning: default namespace URI is not defined in schemaLocation in blackboard_config.653.xml, buffer_config.653.xml Mark S.:Namespace warnings from the 653 config tool should be ignored for now, the 653 config tool needs to be updated (See PCR). | |
| 6 | CP | Linux | DDCI_PCR:5444 | Known Failure | Compile.dvmsbasher-with-journaled-exfat Compile.dvmssimple-with-journaled-exfat Compile.dvmsthroughput-with-journaled-exfat |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) |
media:sales-informal-kismet-qemu-aarch64-Compile-dvmsbasher-with-journaled-exfat-log-08-08-2025.txt media:sales-informal-kismet-qemu-aarch64-Compile-dvmssimple-with-journaled-exfat-log-08-08-2025.txt media:sales-informal-kismet-qemu-aarch64-Compile-dvmsthroughput-with-journaled-exfat-log-08-08-2025.txt |
When integrated with a platform project, these examples display unexpected warnings. CP suggests this be deferred to a later release |
| 7 | Linux | PCR:15793 | Known Failure | Compile.mms_partition1 Compile.mms_partition2 Compile.mms_partition3 Compile.mms_partition4 |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) |
media:sales-informal-kismet-qemu-aarch64-Compile-mms_partition1-log-08-08-2025.txt | When integrated with a platform project, these examples display unexpected warnings. | |
| 8 | LJ | Linux | DDCI_PCR:5469 | Known Pass | Compile.multi-wat-critical-process Compile.multi-wat-process2 Compile.multi-wat-process3 Compile.multi-wat-process4 |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) |
media:sales-informal-kismet-qemu-aarch64-Compile-multi-wat-critical-process-log-08-08-2025.txt | When integrated with a platform project, these examples display unexpected warnings.
RDR/GK: The warning are actually part of the example. This shows the user that its possible for their threads
to not be schedulable in certain WAT configurations. The shown warning are expected and intended. /.*Window placement in WAT \(reconfig-wat\) does not support period \(50000 uSec\) needed by scheduler \(scheduler.*\).*/gm /.*Window placement in WAT \(reconfig-wat\) does not support period \(50000 uSec\) needed by scheduler \(default-core.*\).*/gm /.*Window placement in WAT \(reconfig-wat\) does not support period \(100000 uSec\) needed by scheduler \(scheduler.*\).*/gm /.*Window placement in WAT \(reconfig-wat\) does not support period \(100000 uSec\) needed by scheduler \(default-core.*\).*/gm [lcj 12-aug] Test update needed |
| 9 | CP | Linux | PCR:4340 - comment #23 added for this issue | Known Failure | Compile.vfile_logbook_partition1 | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) |
media:sales-informal-kismet-qemu-aarch64-Compile-vfile_logbook_partition1-log-08-08-2025.txt | When integrated with a platform project, these examples display unexpected warnings. CP suggests this be deferred to a later release |
| 10 | Linux | DDCI_PCR:5281 (comment #54) | Known Failure | Run.vfile_logbook_partition1 | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) DeosS32G274A-2 (s32g2-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 | |
| 11 | Linux | PCR:15344 | Known Failure | Run.zlib-compress | All targets | media:sales-informal-kismet-qemu-aarch64-Run-zlib-compress-log-08-08-2025.txt | Output appears to overlap, "zlib-compress example: starting...' gets overwritten by other output.
zlib-compress example: finished!ceLen=4A52E | |
| 12 | Linux | PCR:15789 | Known Failure | deos.ConfigureRapita | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) |
media:sales-informal-kismet-qemu-aarch64-ConfigureRapita-log-08-08-2025.txt | Rapita RVS Root is not installed. | |
| 13 | LJ/PZ | Linux | PCR:16078 | Known Failure | deos.DeosABCTest.one deos.DeosABCTest.multi |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) DeosS32G274A-2 (s32g2-aarch64) |
media:sales-informal-kismet-qemu-aarch64-DeosABCTest-one-log-08-08-2025.txt | Unexpected 'misses' are reported Test updated needed to verify correct results in the abc report coverage result. abc no longer reports 'reportCoverage DONE' If we could have a pass/fail result reported by the tool that would be helpful. PZ: See PCR 16078, Comment 78 /bin/python3 /desk/desk-environment.py abc report /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/hitmap.bin /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos- kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/abc_index.json /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/hello-world.map /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/hello-world.exe ******************** ABC REPORT CONFIGURATIONS ******************** Build Directory: /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented Built Binary: /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/hello-world.exe Linker Map: /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/hello-world.map Instrumentation Index: /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/abc_index.json Supplemental Search Paths: Discovered Coverage Data - /home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_aarch64_qemu/workspace/hello-world/output/aarch64-elf/instrumented/hitmap.bin ******************** END REPORT CONFIGURATIONS ******************** Reading instrumentation index... Reading in coverage logs into memory... Determing hit state of points index with coverage data... Searching for associated source file referenced in assembly: ../../../code/hello-world.cpp Searching for associated source file referenced in assembly: /desk/include/videobuf.h Searching for associated source file referenced in assembly: /desk/include/stddef.h Searching for associated source file referenced in assembly: /desk/include/stdint.h Searching for associated source file referenced in assembly: /desk/include/systyp.h Searching for associated source file referenced in assembly: /desk/include/fcntl.h Searching for associated source file referenced in assembly: /desk/include/stdlib.h Searching for associated source file referenced in assembly: /desk/include/thrdapi.h Searching for associated source file referenced in assembly: /desk/include/sysapi.h Rendering report to output directory... Rendering report summary... Rendering report framed view... Rendering report coverage subject hello-world.cpp... Rendering report coverage notes... Rendering static content... Rendering abcJavascriptUtils.js... Rendering FileSystem.js... Rendering favicon.ico... |
| 14 | AL | Linux | PCR:TBD | Fail | deos.DeosGdbLaunchConfigurations.deosGdbMultipleRemoteTargets | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-deosGdbMultipleRemoteTargets-log-08-08-2025.txt | Makeboot command text box has be removed from the UI Need more discussion on what the test should do, and what should be done for the alternate solution. AL suggests this be deferred to a later release |
| 15 | Linux | DDCI_PCR:5476 | Known Failure | deos.IntegrationDetailsViews | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-IntegrationDetailsViews-log-08-08-2025.txt media:sales-informal-kismet-qemu-aarch64-IntegrationDetailsViews-log-08-23-2025.txt |
gdb-server, ioi-simple-binder and names.dat are not showing up properly in the 'Included By' view due to exported path not being in the list of kernel files generated by cdproc-makefile AL suggests this be deferred to a later release [lcj 25-aug] OpenArbor needs an update | |
| 16 | LJ | Linux | DDCI_PCR:5417 | Known Failure | deos.NewProjectValidation.checkInvalidComponentDescriptor | QEMU-AARCH64 (qemu-aarch64) | media:sales-informal-kismet-qemu-aarch64-checkInvalidComponentDescriptor-log-08-08-2025.txt | invalid cd.xml file error is not being reported as expected [lcj 08-aug] Updated test. |
| 17 | Linux | PCR:15231 (see comment #14) |
Known Failure | StatusMonitor | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) DeosS32G274A-2 (s32g2-aarch64) |
media:sales-informal-kismet-qemu-arm-StatusMonitor-log-08-08-2025.txt | The Names column is not populated with the process names mainProcess, firstProcess and secondProcess as expected by the test when the rtems-653-configuration example is integrated with the platform project. From JK:The API from OAR no longer gives us the name of a thread, so we have it falling back to just display the thread ID. We'll want to see if OAR can start giving us the names again. | |
| 18 | Linux | PCR:16634 | Known Failure | gdb.GdbVariables.Deos653 | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-GdbVariables-Deos653-log-08-08-2025.txt | ||
| 19 | Linux | PCR:16633 | Known Failure | gdb.GdbVariables.MultipleThreadsRMA gdb.GdbVariables.OneThreadRMA |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-GdbVariables-MultipleThreadsRMA-log-08-08-2025.txt | l_tl_var1's value is empty, when it shouldn't be. This is due to an issue with gdb -- local scoped thread_local variables could not correctly be looked up to display in the variables view. Global thread_local variables were not affected by the issue. | |
| 20 | Linux | DDCI_PCR:16300 | Known Failure | gdb.GdbVariables.Rtems | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-GdbVariables-Rtems-log-08-08-2025.txt | ||
| 21 | Linux | DDCI_PCR:4922 | Known Failure | managedBuild.ManagedBuild.BareAarch64Test managedBuild.ManagedBuild.testLinkWithCdt managedBuild.ManagedBuildProperties.BareAarch64PropertiesTest managedBuild.ManagedBuild.BareX86_64Test |
QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) |
media:sales-informal-kismet-qemu-aarch64-BareAarch64Test-log-08-08-2025.txt | 64-bit managed builds are not yet supported | |
| 22 | Linux | n/a | Known Failure | other.AboutDDCITools | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-aarch64-AboutDDCITools-log-08-08-2025.txt | Testing with unreleased OA, not a DDS made with populateDDS script. The label.txt file is not included in the docker image. | |
| 23 | AL/GK | Linux | PCR:16422 | Known Failure | MinimalFileSystem.multiple-exes | QEMU-AARCH64 (qemu-aarch64) QEMU-80X86_64 (qemu-80x86_64) QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
Media:sales-informal-kismet-qemu-aarch64-MinimalFileSystem-multiple-exes-log-08-08-2025.txt | multiple exe's with the same name, configured in different mfs' is not supported in this release. |
| 24 | LJ | Linux | DDCI_PCR:5454 | Known Failure | other.PerformanceTest | QEMU-AARCH64 (qemu-aarch64) | media:sales-informal-kismet-qemu-aarch64-PerformanceTest-log-08-08-2025.txt | Test updated needed? Test is reporting that 'Clean' is too slow [lcj 11-aug] Updated test |
| 25 | ALR/PZ | Linux | DDCI_PCR:16689 | Known Failure | DeosS32G274A-2 board setup | DeosS32G274A-2 (s32g2-aarch64) | (1) The DeosS32G274A-2 target does not ping by name. [lcj 11-aug] Kevin L fixed both the -1 and -2 board to ping by name (2) The tftp-update.sh script fails dkr mainline$ tftp-update.sh DeosS32G274A-2 -b s32g2-aarch64 -----------------------------* TFTP-Update Tool START *----------------------------- * Searching for 'DeosS32G274A-2' in targets data file at TFTP server... scoretest@linux03.ddci.com's password: tftp-update-targets.txt 100% 11KB 5.8MB/s 00:00 * Target found! * Selected BSP to upload Deos Boot: s32g2-aarch64 * ERROR: /desk/platform/s32g2-aarch64/boot/deosBoot.bin NOT found. ------------------------------* TFTP-Update Tool END *------------------------------ dkr mainline$ [alr 11-aug] This has been fixed in unreleased tftp-update 1.4.0 | |
| 26 | RDR | Linux | PCR:16388 | Known Failure | Debug.mms_partition4 | QEMU-80X86_64 (qemu-80x86_64) | media:sales-informal-kismet-qemu-80x86_64-Debug-mms_partition4-log-08-09-2025.txt | norm-proc4 was NOT found in the video stream RDR: Was able to confirm that this works on vm/real x86_64; however, will likely require a regex similar to #8 and video-stream is part of the threads which do not run. |
| 27 | RDR | Linux | PCR:16388 | Known Failure | Run.blackboard_event | QEMU-80X86_64 (qemu-80x86_64) | media:sales-informal-kismet-qemu-80x86_64-Run-blackboard_event-log-08-10-2025.txt | Blackboard empty was NOT found in the video stream RDR: Confirmed to be a QEMU x86_64 timing issue. |
| 28 | Linux | PCR:16388 DDCI_PCR:5446 |
Known Failure | Run.interrupt | QEMU-80X86_64 (qemu-80x86_64) | media:sales-informal-kismet-qemu-80x86_64-Run-interrupt-log-08-10-2025.txt | proc2 was NOT found in the video stream platreg.s indicates the number of PAL interrupts is 17, so the test update that will be done on PCR 5446 wouldn't help here .long 17 /* Number of PAL interrupts */ [from MS 15-aug]Some 653 examples struggle to run on the qemu-80x86_64 due to timing issues and the display on the video stream is often incomplete. | |
| 29 | CP | Linux | DDCI_PCR:TBD | Fail | Debug.dvmsthroughput-with-journaled-exfat | QEMU-PPC (qemu-ppc) | media:sales-informal-kismet-qemu-ppc-Debug-dvmsthroughput-with-journaled-exfat-log-08-10-2025.txt media:sales-informal-kismet-qemu-ppc-Debug-dvmsthroughput-with-journaled-exfat-screenshot-08-16-2025.png |
[lcj 11-aug] updated test. [lcj 15-aug]Test failed when rerun on OALinux04 [lcj 16-aug] following a cold start, the example takes too long to launch a debugging session on qemu-ppc. CP suggests this be deferred to a later release. The example is a slack consumer and runs to completion while consuming as much slack as possible, thus potentially starving network threads and thus the debugger. |
| 30 | LJ | Linux | Pass | deos.DeosTargetManager.testF11 | QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-ppc-DeosTargetManager-testF11-log-08-11-2025.txt | TimeoutException: Timeout after: 2000 ms.: waiting for dialog: Debug As [lcj 15-aug] Test passed when rerun on OALinux04 | |
| 31 | LJ | Linux | Pass | deos.timemap.TimeMapUI | QEMU-PPC (qemu-ppc) QEMU-ARM (qemu-arm) |
media:sales-informal-kismet-qemu-ppc-timemap-TimeMapUI-log-08-11-2025.txt | Hover over tooltiptext did not contain the expected output [lcj 15-aug] Test passed when rerun on OALinux04 | |
| 32 | LJ | Linux | Pass | deos.CopyForEditing | QEMU-ARM (qemu-arm) | media:sales-informal-kismet-qemu-arm-CopyForEditing-log-08-11-2025.txt | Undo CopyForEditing of platreg->libansi.fp.xml failed [lcj 15-aug] Test passed when rerun on OALinux04 | |
| 33 | LJ | Linux | Pass | deos.DeosCrittimeTest | QEMU-ARM (qemu-arm) | media:sales-informal-kismet-qemu-arm-DeosCrittimeTest-log-08-11-2025.txt | Crittime kernel was not enabled [lcj 15-aug] Test passed when rerun on OALinux04 | |
| 34 | LJ | Linux | DDCI_PCR:5453 | Pass | deos.DeosGdbLaunchConfigurations.deosGdbLaunching | QEMU-ARM (qemu-arm) | media:sales-informal-kismet-qemu-arm-deosGdbLaunching-log-08-11-2025.txt | Hello count was not updated [lcj 15-aug] Test failed when rerun on OALinux04 [lcj 16-aug]test passes after updating the test to use the video stream timeout when checking the video stream content. |
| 35 | Linux | DDCI_PCR:5468 | Pass | compileRunDebug.Run.file-parser | QEMU-ARM (qemu-arm) DeosS32G274A-2 (s32g2-aarch64) |
media:sales-informal-kismet-qemu-arm-Run-file-parser-log-08-14-2025.txt | No Pattern Defined for file-parser Test needs to be updated to add regex for expected output [lcj 16-aug] Updated test, passes now. | |
| 36 | Linux | DDCI_PCR:5470 | Pass | compileRunDebug.Run.a-deos-process compileRunDebug.Run.hybrid-io-partition1 deos.Sybil |
QEMU-ARM (qemu-arm) DeosS32G274A-2 (s32g2-aarch64) |
media:sales-informal-kismet-qemu-arm-Run-a-deos-process-log-08-15-2025.txt | Per MS, the example's output was updated Test needs to be updated to modify the existing regex for expected output [lcj 16-aug] Updated tests, they pass now. | |
| 37 | Linux | Pass | com.ddci.openarbortests.deos.NewProjectValidation.checkPlatformProjectCreationValidation | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-NewProjectValidation-checkPlatformProjectCreationValidation-log-08-15-2025.txt | [lcj 15-aug] Fix a bug in OA, passed when rerun. | ||
| 38 | Linux | Pass | com.ddci.openarbortests.deos.NewProjectValidation.createChildPlatformProject | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-NewProjectValidation-createChildPlatformProject-log-08-15-2025.txt | [lcj 15-aug] Fix a bug in OA, passed when rerun. | ||
| 39 | Linux | Pass | com.ddci.openarbortests.deos.NewProjectValidation.createPlatformProjectOutsideDDCIDeskTree | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-NewProjectValidation-createPlatformProjectOutsideDDCIDeskTree-log-08-15-2025.txt | [lcj 15-aug] Fix a bug in OA, passed when rerun. | ||
| 40 | Linux | Pass | projectOptions.other.DeosOptionTabs.integrationToolTabTest | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-DeosOptionTabs-integrationToolTabTest-log-08-15-2025.txt | [lcj 15-aug] Fix a bug in OA, passed when rerun. | ||
| 41 | Linux | Pass | projectOptions.other.DeosOptionTabs.kernelFileSystemsTabTest | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-DeosOptionTabs-kernelFileSystemsTabTest-log-08-15-2025.txt | [lcj 15-aug] Updated test, passed when rerun. | ||
| 42 | Linux | Pass | projectOptions.other.DeosOptionTabs.publicHeadersTabTest | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-DeosOptionTabs-publicHeadersTabTest-log-08-15-2025.txt | [lcj 15-aug] Fix a bug in OA, passed when rerun. | ||
| 43 | DDCI_PCR:5454 | Linux | Pass | Run.mms_partition4 | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-Run-mms_partition4-log-08-15-2025.txt | [lcj 15-aug] Updated test, passed when rerun. Test needed to wait for the resource change listener after updating the wats related pia file. | |
| 44 | LJ | Linux | DDCI_PCR:5471 | Known Failure | com.ddci.openarbortests.gdb.GdbBreakAtStartup.653 | DeosS32G274A-2 (s32g2-aarch64) | media:sales-informal-kismet-s32g2-aarch64-gdb-GdbBreakAtStartup-log-08-15-2025.txt | [lcj 16-aug] The Debug stackframe does not contain the expected items Steps to reproduce: (1) In s32g2-aarch64, 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) One of the first thread's items in the stack frame should contain "_start()" [lcj 25-aug] Updated OA to trigger a platform project rebuild when a dependent project's .653.xml file changes. |
| 45 | Linux | DDCI_PCR:5471 | Known Failure | projectOptions.other.ConfigurationsTest | QEMU-PPC (qemu-ppc) | media:sales-informal-kismet-qemu-ppc-other-ConfigurationsTest-log-08-23-2025.txt | The ConfigTest project is not properly displayed in the Components View.
cdproc-query: Error: No file found matching etc/ConfigTest.cd.xml in subdirectories ['platform/qemu-ppc', 'ppc', ], of desk roots ['/home/lcj/oaTestHarness/workspace/ddses/DDS-docker-sales-deos-kismet-20250710/deos_ppc_qemu/workspace/ConfigTest/output/desk', '/desk' [lcj 25-aug] Updated OA to copy a non-platform project's cd.xml file to it's output/desk/etc folder when the project is created or built. |