OpenArbor 12.3.0 Test Plan and Report Sales Kismet 24A

From DDCIDeos
Jump to navigationJump to search


About

OpenArbor Windows/Linux 12.3.0
SVN Revision: r107077
SVN Branch Name: 12.3.0

Test Schedule

Scheduled Test Runs Start Date Due Date Delivered Percentage Complete
Formal 6-19-24 7-16-24 7-16-24 100%

Introduction

The automated test suites for Eclipse, supports Eclipse 2023-06-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_12.3.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\Release12.3.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.
Not scheduled to be tested for this release.
X Scheduled to be tested for this release.
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)
OALinux01 Linux (64bit) LCJ Linux development
OALinux02 Linux (64bit) NH Linux development
backup test machine
OALinux03 Linux (64bit) KT Linux development
backup test machine
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-20240620 1718923503 X86_64 QEMU-X86_64 (qemu-x86_64) Launcher testlinux01 KT Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 ARM DeosLS1043ARDB-1 (ls1043ardb) Platform Integration testlinux02 LJ Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 PPC DeosNAI68PPC2 (nai68ppc2) Platform Integration testlinux01 KT Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 ARM DeosZCU102-2 (zcu102) Platform Integration testlinux02 LJ Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 PPC DeosT1042D4RDB-1 (t10xx) Platform Integration oalinux02 LJ Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 X86 DeosCOMe-cTL6-1 (come-ctl6) Platform Integration testlinux02 LJ Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 X86_64 DeosCOMe-cTL6-2 (come-ctl6-x86_64) Platform Integration oalinux02 LJ Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 ARM DeosIMX8QM-3 (imx8qm) Platform Integration oalinux03 KT Fail See testing notes
Deos DDS-docker-sales-deos-kismet-20240620 1718923503 AARCH64 DeosShakaMX8-1* (imx8qm-aarch64) Platform Integration oalinux03 KT Fail See testing notes
Deos DDS-sales-deos-kismet-20240620 1718923503 X86_64 QEMU-X86_64 (qemu-x86_64) Launcher testw10e1 LJ Known Failure Unable to test
See testing notes, item #2
Deos DDS-sales-deos-kismet-20240620 1718923503 ARM DeosLS1088ARDB-1 (ls10x8ardb) Platform Integration oatest KT Fail See testing notes
Deos DDS-sales-deos-kismet-20240620 1718923503 PPC DeosT2080RDB (t2080rdb) Platform Integration testw10e1 KT Fail See testing notes
Deos DDS-sales-deos-kismet-20240620 1718923503 ARM DeosNAI68ARM2-1 (nai-ultrascale) Platform Integration testw10e1 LJ Known Failure See testing notes
Deos DDS-sales-deos-kismet-20240620 1718923503 80X86 DeosNAI68INT6-1 (nai68int6) Platform Integration testw10e2 KT Fail See testing notes
Deos DDS-sales-deos-kismet-20240620 1718923503 AARCH64 DeosShakaMX8-1* (imx8qm-a72-aarch64) Platform Integration oatestlap LJ Known Failure See testing notes
Deos DDS-sales-deos-kismet-20240711 1720651242 AARCH64 QEMU-AARCH64 (qemu-aarch64) dvms-examples
IST examples
GdbVariables 		oatestlap LJ Known Failure See Testing Notes
Deos DDS-sales-deos-kismet-20240711 1720651242 ARM QEMU-ARM (qemu-arm) dvms-examples
IST examples
GdbVariables 		testw10e1 LJ Known Failure See Testing Notes
Deos DDS-sales-deos-kismet-20240711 1720651242 X86 QEMU-X86 (qemu-x86) dvms-examples
IST examples
GdbVariables 		testw10e2 KT Known Failure See Testing Notes
Deos DDS-sales-deos-kismet-20240711 1720651242 PPC QEMU-PPC (qemu-ppc) dvms-examples
IST examples
GdbVariables 		oatest KT Known Failure See Testing Notes
Deos DDS-docker-sales-deos-kismet-20240711 1720651242 ARM QEMU-ARM (qemu-arm) loadPlatformIntegration testlinux01 LJ Known Failure See testing notes
Deos DDS-docker-sales-deos-kismet-20240711 1720651242 X86_64 QEMU-X86_64 (qemu-x86_64) loadPlatformIntegration testlinux02 KT Known Failure See testing notes
Deos DDS-docker-sales-deos-kismet-20240711 1720651242 X86 QEMU-X86 (qemu-x86) loadPlatformIntegration oalinux02 KT Known Failure See testing notes
Deos DDS-docker-sales-deos-kismet-20240711 1720651242 PPC QEMU-PPC (qemu-ppc) loadPlatformIntegration oalinux02 KT Known Failure See testing notes
Deos DDS-docker-sales-deos-kismet-20240711 1720651242 AARCH64 QEMU-AARCH64 (qemu-aarch64) loadPlatformIntegration oalinux03 LJ Known Failure See testing notes

Testing Notes

ID Priority OS PCR Status Affected Tests Target Screenshot Comments
1 JD Windows PCR:15743 Known Failure deos.DdsInstaller DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosZCU102-1 (zcu102)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosNAI68ARM2-1 (nai-ultrascale)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosShakaMX8-1* (imx8qm-aarch64)
DeosT2080RDB (t2080rdb)
DeosNAI68INT6-1 (nai68int6) 		media:setup_log_full-20240620.txt
media:sales-kismet-24a-windows-ls10x8ardb-setup-log-full-6-26-2024.txt
media:sales-kismet-24a-windows-setup-log-full-20240701.txt 		Several post install scripts report unxpected errors.
Of particular note these two:

/etc/postinstall/0p_100_update_desk_xml_files.sh: /etc/postinstall/python3-argcomplete.sh: line 9: python3: command not found
/etc/postinstall/desk.sh: grep: /etc/fstab: No such file or directory
sed: can't read /etc/fstab: No such file or directory
/bin/mv: cannot stat '/etc/fstab': No such file or directory
mount: /tmp: Invalid argument
A subdirectory or file C:\ProgramData\Microsoft\Windows\Start Menu\Programs/DDC-I/oaTestHarness/workspace/DDS-list/DDS-sales-deos-kismet-20240611 already exists.

LJ 07/01 retested with DDS built on 07/01, and the zp-100_update_desk_xml_file.sh script ran without error. The desk.sh script is reporting the same errors about /etc/fstab.

2 Windows PCR:15799 Known Failure Launching qemu emulator QEMU-X86_64 (qemu-x86_64) media:windows-qemu-x86_64-emulator-failure-20240621.txt
media:windows-qemu-x86_64-emulator-failure-20240621.png 		qemu x86_64 emulator fails to launch.
Per AL, qemu-x86_64 will not run in a cygwin environment.

This is acceptable for this Sales release. We will ensure x86_64 evals are on Docker. Long term mgmt is asking customers if WSL vs Cygwin is acceptable at this point in time. Plan was by laplata corporate infrastructure would allow WSL+Docker.

2.5 SD Linux PCR:15796 Known Failure Launching qemu emulator QEMU-X86_64 (qemu-x86_64) media:sales-kismet-24a-linux-qemuX86_64-build-warnings-7-8-2024.txt Warning messages displayed when launching the emulator on Linux:

Warning: ${CGAVideoMemoryAddress} is not defined. The NULL string will be used.
Warning: ${CGAVideoMemoryLengthInPages} is not defined. The NULL string will be used.
And:
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX.avx512-vpopcntdq [bit 14]
qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX.la57 [bit 16]
qemu-system-x86_64: warning: host doesn't support requested feature: MSR(10AH).taa-no [bit 8]

3 CP Linux PCR:15768 Known Failure Run.di2c-nxp-read DeosT1042D4RDB-1 (t10xx)
DeosT2080RDB (t2080rdb) 		media:t10xx -with-di2c-nxp-read-example-output-20240623.txt Expected output for the example is not displayed on the video stream. Address phase of AT24C256 is two-bytes but example only uses one byte address. Full pass criteria for this example requires di2c-nxp-write execution prior to it, but that example also has the wrong address phase size so the writes fail.
4.5 DDCI's SPS Linux (oalinux03)
Windows (oatestlap) 		DDCI_PCR:5212 Known Failure Run.dvmssimple-with-journaled-exfat DeosT1042D4RDB-1 (t10xx) media:t10xx-with-dvmssimple-with-journaled-exfat-example-output-20240701.txt
media:t10xx-with-dvmssimple-with-journaled-exfat-example-output-20240715.txt 		Expected output for the example is not displayed on the video stream. Usage of

std::atomic with bool type appears to be the culprit.
LJ 07/01 retested with DDS built on 07/01, and the test fails due to the expected output not being displayed.
LJ 07/15: DDCI_PCR:5183 is marked resolved, retested with DDS built on 7/11 on linux, and the test fails due to the expected output not being displayed
LJ 07/15: DDCI_PCR:5183 is marked resolved, retested with DDS built on 7/11 on windows, and the test fails due to the expected output not being displayed
RLF 07/15: We can release with a cover letter update for PPC. We will likely need multiple PCRs. It looks like there may be kernel and gnu-language limitations coming. We should not rush to create those PCRs since the language needs to be very precise. DVMS journal may be able to create a PCR to workaround the issue and eliminate its generation of the problematic relocation.

5.5 DDCI's SPS Linux (oalinux03)
Windows (oatestlap) 		DDCI_PCR:5212 Known Failure Run.dvmsthroughput-with-journaled-exfat DeosT1042D4RDB-1 (t10xx) media:t10xx-with-dvmsthroughput-with-journaled-exfat-example-output-20240701.txt
media:t10xx-with-dvmsthroughput-with-journaled-exfat-example-output-20240715.txt 		Expected output for the example is not displayed on the video stream. Usage of

std::atomic with bool type appears to be the culprit.
LJ 07/01 retested with DDS built on 07/01, and this test fails due to the expected output not being displayed.
LJ 07/15: DDCI_PCR:5183 is marked resolved, retested with DDS built on 7/11 on linux, and the test fails due to the expected output not being displayed
LJ 07/15: DDCI_PCR:5183 is marked resolved, retested with DDS built on 7/11 on windows, and the test fails due to the expected output not being displayed
RLF 07/15: We can release with a cover letter update for PPC. We will likely need multiple PCRs. It looks like there may be kernel and gnu-language limitations coming. We should not rush to create those PCRs since the language needs to be very precise. DVMS journal may be able to create a PCR to workaround the issue and eliminate its generation of the problematic relocation.

6 CP Linux DDCI_PCR:4728 Known Failure Run.vfile_logbook_partition1 DeosT1042D4RDB-1 (t10xx) media:t10xx -with-vfile_logbook_partition1-example-output-20240623.txt Expected output for the example is not displayed on the video stream.
Per CP, The 653p2 logbook stuff for DVMS is not in good shape.
This example is not ready for prime time
7 Linux PCR:15344 Known Failure Run.zlib-compress DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosNAI68PPC2 (nai68ppc2)
DeosZCU102-1 (zcu102)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosIMX8QM-3 (imx8qm)
DeosNAI68ARM2-1 (nai-ultrascale)
DeosCOMe-cTL6-1 (come-ctl6)
DeosCOMe-cTL6-2 (come-ctl6-x86_64)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosShakaMX8-1* (imx8qm-aarch64)
QEMU-X86_64 (qemu-x86_64)
DeosT2080RDB (t2080rdb)
DeosNAI68INT6-1 (nai68int6)
QEMU-ARM (qemu-arm)
QEMU-AARCH64 (qemu-aarch64)
QEMU-PPC (qemu-ppc)
QEMU-X86 (qemu-x86) 		Media:t10xx with-run-zlib-compress-example-output-20240623.txt No Pattern Defined for zlib-compress.

Output appears to be incomplete
8 MR Linux (qemu-arm) PCR:15789 Known Failure deos.ConfigureRapita DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosNAI68PPC2 (nai68ppc2)
DeosZCU102-1 (zcu102)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosIMX8QM-3 (imx8qm)
DeosNAI68ARM2-1 (nai-ultrascale)
DeosCOMe-cTL6-1 (come-ctl6)
DeosCOMe-cTL6-2 (come-ctl6-x86_64)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosShakaMX8-1* (imx8qm-aarch64)
DeosNAI68INT6-1 (nai68int6)
QEMU-ARM (qemu-arm)
QEMU-AARCH64 (qemu-aarch64)
QEMU-PPC (qemu-ppc)
QEMU-X86 (qemu-x86)
QEMU-X86_64 (qemu-x86_64) 		media: configureRapita-installation-failure-20240628.png
media: rapitaError.png
media:configureRapita-errors-20240708.txt 		Timeout after: 5000 ms.: Problems view does not contain \QNo RVS data is available from Critical Time Data\E
LJ 06/28 On 6/21 MR installed Rapita on testlinux02, I modified the test to continue on if a test scenario fails unexpectedly, and to only run the test for QEMU bsps.
The test reports that RVS is not installed.

MR 06/28 When following the video instructions that Mike H. provided, I ran into unexpected errors. I contacted Daniel from Rapita, but he wasn't familiar enough with the tools to identify the errors. He said he would ask around the office to see if anyone could help. I'll follow up with him to see if he found a support contact for us.
LJ 07/08 I was able to get past the license error on Windows, but now get an error running create_project.py


9 LJ Linux (qemu-arm) DDCI_PCR:5137 Known Failure deos.DvmsMal DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosCOMe-cTL6-1 (come-ctl6)
DeosShakaMX8-1* (imx8qm-aarch64)
DeosNAI68INT6-1 (nai68int6)
QEMU-ARM (qemu-arm)
QEMU-AARCH64 (qemu-aarch64)
QEMU-PPC (qemu-ppc)
QEMU-X86 (qemu-x86)
QEMU-X86_64 (qemu-x86_64) 		media: TBD t10xx and come-ctl6 do not have optional mals
ls1043arb, ls10x8ardb, imx8qm-aarch64, imx8qm-a72-aarch64 are not setup for Dvms mal testing, but should be.
LJ:06/27 DvmsMal test has been updated, the test should be re-run for ls1043arb, imx8qm-aarch64, ls10x8ardb and imx8qm-a72-aarch64
7-1-24: nai68int6 is not setup for dvms mal testing
LJ 7/15: QEMU-ARM, QEMU-AARCH64, QEMU-X86, QEMU-X86_64, QEMU-PPC are not setup for dvms mal testing
9.1 CP Linux (qemu-arm)
Windows 		DDCI_PCR:5192 Known Failure deos.DvmsMal DeosLS1043ARDB-1 (ls1043ardb) media:DvmsMal-ls1043ardb-20240627.txt CP:Driver was never tested/integrated on LS1043ARDB board, only DE-LS1043A. PCR 5192 to add resources for MMC to ls1043ardb BSP.

LJ:06/27 Re-ran the updated DvmsMal test for ls1043arb
pi: Error #1: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (Network) owns undefined memory mapped resource (USDHC_RAM) pi: Error #2: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (dvms-demo1) owns undefined memory mapped resource (USDHC_RAM) pi: Error #3: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (Network) owns undefined memory mapped resource (USDHC_CONTROLLER) pi: Error #4: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (dvms-demo1) owns undefined memory mapped resource (USDHC_CONTROLLER)

9.2 CP Linux (qemu-arm)
Windows 		DDCI_PCR:5204 Known Failure deos.DvmsMal DeosLS1043ARDB-1 (ls10x8ardb) media:sales-kismet-24a-windows-ls10x8ardb-dvmsMal-build-errors-6-27-2024.txt KT:06/27 Re-ran the updated DvmsMal test for ls10x8ardb
pi: Error #1: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (Network) owns undefined memory mapped resource (SATA_CSR2)

pi: Error #2: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (dvms-demo1) owns undefined memory mapped resource (SATA_CSR2) pi: Error #3: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (Network) owns undefined memory mapped resource (SATA_RAM2) pi: Error #4: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (dvms-demo1) owns undefined memory mapped resource (SATA_RAM2) pi: Error #5: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (Network) owns undefined memory mapped resource (SATA_CSR1) pi: Error #6: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (dvms-demo1) owns undefined memory mapped resource (SATA_CSR1) pi: Error #7: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (Network) owns undefined memory mapped resource (SATA_RAM1) pi: Error #8: Caused by feature provider content to file (./platreg.pi.xml): Process Instance (dvms-demo1) owns undefined memory mapped resource (SATA_RAM1)

CP:There is no MMC on LS10x8ARDB board, so this is an invalid combination.

10 Linux (qemu-arm) PCR:15231
(see comment #14) 		Known Failure deos.StatusMonitor DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosNAI68PPC2 (nai68ppc2)
DeosZCU102-1 (zcu102)
DeosIMX8QM-3 (imx8qm)
DeosNAI68ARM2-1 (nai-ultrascale)
DeosCOMe-cTL6-1 (come-ctl6)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosShakaMX8-1* (imx8qm-aarch64)
DeosT2080RDB (t2080rdb)
QEMU-ARM (qemu-arm)
QEMU-AARCH64 (qemu-aarch64)
QEMU-PPC (qemu-ppc)
QEMU-X86 (qemu-x86) 		media:StatusMonitor-failures-20240612.txt
media:StatusMonitor-missing-names-20240614.png 		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.
11 CP Linux
Windows 		PCR:15770 Expected Failure Debug.di2c-nxp-read
Debug.di2c-nxp-write
Run.di2c-nxp-read
Run.di2c-nxp-write 		DeosLS1043ARDB-1 (ls1043ardb)
DeosLS1088ARDB-1 (ls10x8ardb) 		media:ls1043ardb-with-di2c-nxp-read-example-output-20240614.txt Error: Process Template (di2c-nxp-read) uses feature set (di2c-nxp), which is not present.

Error: Process Template (di2c-nxp-write) uses feature set (di2c-nxp), which is not present. The example should be integrating i2c-ls not di2c-nxp. PCR will address how to do this.

13 Linux DDCI_PCR:4932 Known Failure MulticoreIntegration DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosNAI68PPC2 (nai68ppc2)
DeosZCU102-1 (zcu102)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosIMX8QM-3 (imx8qm)
DeosCOMe-cTL6-1 (come-ctl6)
DeosCOMe-cTL6-2 (come-ctl6-x86_64)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosShakaMX8-1* (imx8qm-aarch64)
QEMU-X86_64 (qemu-x86_64)
DeosT2080RDB (t2080rdb)
DeosNAI68INT6-1 (nai68int6)
QEMU-ARM (qemu-arm)
QEMU-AARCH64 (qemu-aarch64)
QEMU-PPC (qemu-ppc)
QEMU-X86 (qemu-x86) 		This test requires an update to work properly with BSPs that support pia.
15 CP Windows
Linux 		DDCI_PCR:5204 Known Failure CffsMal DeosIMX8QM-3 (imx8qm)
DeosNAI68PPC2 (nai68ppc2)
DeosT2080RDB (t2080rdb) 		DeosIMX8QM-3 (imx8qm): Mal file: [/desk/etc/cffs-emmc-a.cd.xml] does not exist in the DDS desk\etc folder.
DeosNAI68PPC2 (nai68ppc2): Mal file: [/desk/etc/cffs-sata-atapi.cd.xml] does not exist in the DDS desk\etc folder.
CffsMal cannot run without these files.

Update 6-26-24: Sales DDS does not contain cffs.
17 Windows PCR:15221
PCR:15800 		Known Failure All Build Tests
DeosABCTest.ConfigErrorCheck
DeosABCTest.multi
DeosABCTest.one
DeosOptionTabs.abcToolTabTest
VariantSpecificItFiles.variantItFilesForExeProject
MultipleBuildConfigs 		DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosCOMe-cTL6-2 (come-ctl6-x86_64)
DeosShakaMX8-1* (imx8qm-aarch64)
QEMU-X86_64 (qemu-x86_64)
QEMU-AARCH64 (qemu-aarch64) 		media:hello-world-instrumented-integrated-with-imx8qm-a72-aarch64-20240625.txt /desk/bin/instrument --index=index.txt --format=GNU --arch=AARCH64 --insert ./insert.template --assembly=hello-world.s < hello-world.s_ > inst_hello-world.s_

Can't locate GNUAARCH64Postprocessing.pl in @INC (@INC contains: /desk /desk/bin /desk/lib/abcscat /usr/local/lib/perl5/site_perl/5.36/x86_64-cygwin-threads /usr/local/share/perl5/site_perl/5.36 /usr/lib/perl5/vendor_perl/5.36/x86_64-cygwin-threads /usr/share/perl5/vendor_perl/5.36 /usr/lib/perl5/5.36/x86_64-cygwin-threads /usr/share/perl5/5.36) at /desk/bin/instrument line 163. BEGIN failed--compilation aborted at /desk/bin/instrument line 169 (#1) 

   (F) You said to do (or require, or use) a file that couldn't be found.
   Perl looks for the file in all the locations mentioned in @INC, unless
   the file name included the full path to the file.  Perhaps you need
   to set the PERL5LIB or PERL5OPT environment variable to say where the
   extra library is, or maybe the script needs to add the library name
   to @INC.  Or maybe you just misspelled the name of the file.  See
   "require" in perlfunc and lib.

Uncaught exception from user code: Can't locate GNUAARCH64Postprocessing.pl in @INC (@INC contains: /desk /desk/bin /desk/lib/abcscat /usr/local/lib/perl5/site_perl/5.36/x86_64-cygwin-threads /usr/local/share/perl5/site_perl/5.36 /usr/lib/perl5/vendor_perl/5.36/x86_64-cygwin-threads /usr/share/perl5/vendor_perl/5.36 /usr/lib/perl5/5.36/x86_64-cygwin-threads /usr/share/perl5/5.36) at /desk/bin/instrument line 163. BEGIN failed--compilation aborted at /desk/bin/instrument line 169.
abc not supporting 64-bit

19 Windows
Linux 		PCR:15231 Known Failure Debug.arinc653-partition
Debug.rtems-cpu-usage
Debug.rtems-hm-partition1
Debug.rtems-partition1
Debug.rtems-partition2
Debug.rtems-partition3
Debug.rtems-partition4
Debug.rtems-socket-example
GdbVariables.Rtems
MakeExport.rtems-cpu-usage
MakeExport.rtems-hm-partition1
MakeExport.rtems-partition1
MakeExport.rtems-partition2
MakeExport.rtems-partition3
MakeExport.rtems-partition4
MakeExport.rtems-socket-example

Run.arinc653-partition
Run.rtems-cpu-usage
Run.rtems-hm-partition1
Run.rtems-partition1
Run.rtems-partition2
Run.rtems-partition3
Run.rtems-partition4
Run.rtems-socket-example
StatusMonitor
RtemsLinkOptions.cpp_libraries
RtemsLinkOptions.cpp_objects
RtemsLinkOptions.cpp_additional_options
RtemsCCompileCodeGeneration
RtemsCppCompileCodeGeneration

DeosCOMe-cTL6-2 (come-ctl6-x86_64)
QEMU-X86_64 (qemu-x86_64) 		media:rtems-partition1-80x86_64-build-errors-20240625.txt Support for RTEMS/80x86_64 is not available yet.

LJ 07-23-2024:Debug.sockets653 and Run.sockets653 were mistakenly reported for this failure.
These examples are not RTEMS examples, and fail for a different reason.
Item 19.5 was created below to document the actual failure that was discovered when testing the subsequent Savianos dds for the nai68int6-x86_64 bsp.

19.5 Linux PCR:TBD Fail Debug.sockets653
Run.sockets653 		DeosNAI68INT6-1 (nai68int6-x86_64) media:sockets653-x86_64-build-failure-20240721.txt Link error reported when building the example:
/usr/local/cross-compilers/gcc-11.2.0/bin/x86_64-elf-ld: cannot find -lsocket-adapter
25 Windows DDCI_PCR:5205 Known Failure DeosTargetManager.testF11
DebugOptionsAdditionalOptions
DebugOptionsMessages
DebugOptionsStartup 		DeosLS1088ARDB-1 (ls10x8ardb)
DeosT2080RDB (t2080rdb)
DeosNAI68INT6-1 (nai68int6) 		MLD is not installed in the DDS. Test is set to fail if MLD is not installed.
26 Linux DDCI_PCR:5198 Known Issue CompileError QEMU-X86_64 (qemu-x86_64) OA test update. Test needs update to handle X86_64 targets. Also, the test assumes a folder for x86_64 exists in path /<branch>/TestResources/General/examples/assembly_files, containing file "get5error.s". This folder needs to be created. KT is writing pcr.
27 Linux PCR:15143 Known Failure Debug.mms_partition4 QEMU-X86_64 (qemu-x86_64) 'norm-proc4' thread takes over 15 minutes to spawn in 'mms_partition4'.
29 Linux DDCI_PCR:5198 Known Failure ProjectConverter QEMU-X86_64 (qemu-x86_64) OA test update. Test converts .zip project that exists in /<branch>/TestResources/ProjectConverter. The x86_64 .zip project does not currently exist in this directory. KT writing pcr.
30 Linux PCR:15797 Known Failure CacheTrasher
MakeExport.worker 		QEMU-X86_64 (qemu-x86_64) Cache Trashing is not supported on the qemu-x86_64 platform
31 Linux PCR:15234 Known Failure deos.DeosCrittimeTest QEMU-X86_64 (qemu-x86_64) Timeout after: 5000 ms.: The widget ToolItem with tooltip text {Clear Crittime} was not enabled.
DDS does not contain a crittime kernel
/desk/x86_64/appbin/crittime/libkernel.so does not exist. KT writing a PCR.
32 Linux DDCI_PCR:5115 Known Failure DeosGdbLaunchConfigurations.deosGdbLaunching
GdbVariables.Deos653
GdbVariables.MultipleThreadsRMA 		QEMU-X86_64 (qemu-x86_64) The test implementation for gdb bp setting in linux environments is not currently working.
33 Linux DDCI_PCR:5198 Known Failure NewProjectValidation.createPlatformProjectWithIncludedHypFiles QEMU-X86_64 (qemu-x86_64) OA test update. /TestResources/platform does not currently contain folder test-qemu-x86_64 -- need to add in order to run test.
33.1 Linux DDCI_PCR:5210 Known Failure ManagedBuild.BareX86_64Test
ManagedBuild.testLinkWithCdt
ManagedBuildProperties.BareX86_64PropertiesTest 		QEMU-X86_64 (qemu-x86_64) 64-bit managed builds are not yet supported
LJ: 07/09:OpenArbor should be updated to support this, need a PCR
34 Linux DDCI_PCR:5014 Known Failure other.RenameProjects QEMU-X86_64 (qemu-x86_64) Media:sales-kismet-24a-linux-qemuX86_64-rename-platform-build-error-7-1-2024.txt Build errors occur in the qemu platform project after it is renamed and relaunched. PCR is taken from entry #15 in https://deos.ddci.com/ddciWiki/OpenArbor_12.2.1_Test_Plan_and_Informal_Report.
35 Linux DDCI_PCR:5198 Known Failure GccAssemblerAdditionalOptions
GccAssemblerCodeGeneration
GccAssemblerDirectories
GccAssemblerPreprocessor
RtemsAssemblerAdditionalOptions
RtemsAssemblerCodeGeneration
RtemsAssemblerDirectories
RtemsAssemblerPreprocessor 		QEMU-X86_64 (qemu-x86_64) OA test update. The test tries to import 'get5.sx' file from /.../TestResources/General/examples/assembly_files/<architecture>/. There is no folder for the X86_64 architecture in this folder currently, so it needs to be created.
39 Windows DDCI_PCR:5211 Known Failure GdbVariables.Deos653 QEMU-AARCH64 (qemu-aarch64)
QEMU-X86 (qemu-x86) 		TimeoutException: Timeout after: 5000 ms.: can't find stack frame: Thread #1 131071 (Suspended : Container) -> main
39.1 Windows DDCI_PCR:5211 Known Failure GdbVariables.Deos653 QEMU-ARM (qemu-arm)
QEMU-PPC (qemu-ppc) 		media:qemu-arm-gdbVariables-Deos653-afer-resume-debugger-console-output-20240711.txt Trouble with Resume!
40 Windows DDCI_PCR:5211 Known Failure GdbVariables.MultipleThreadsRMA QEMU-AARCH64 (qemu-aarch64)
QEMU-X86 (qemu-x86)
QEMU-PPC (qemu-ppc) 		media:qemu-aarch64-gdbVariables-MultipleThreadsRMA-afer-resume-debugger-console-output-20240711.txt dbg-multi-thread-process, thread: Thread #2, l_f_var1's value was not modified after the Go or Step Over as expected

dbg-multi-thread-process, thread: Thread #2, g_tl_var1's value was not modified after the Go or Step Over as expected
Expressions item [, , ] appears to be empty
Variables view appears to be empty
Trouble with Resume!

40.1 Windows DDCI_PCR:5211 Known Failure GdbVariables.MultipleThreadsRMA QEMU-ARM (qemu-arm) dbg-multi-thread-process, thread: Thread #2, l_f_var1's value was not modified after the Go or Step Over as expected

dbg-multi-thread-process, thread: Thread #2, g_tl_var1's value was not modified after the Go or Step Over as expected
Expressions item [, , ] appears to be empty
Variables view appears to be empty

41 Windows DDCI_PCR:5211 Known Failure GdbVariables.OneThreadRMA QEMU-AARCH64 (qemu-aarch64) photon, thread: Thread #1, l_tl_var1's value was not modified after the Go as expected
42 Windows PCR:15231 Known Failure GdbVariables.Rtems QEMU-AARCH64 (qemu-aarch64) Error build dbg-rtems.cpp
Error: [output/aarch64-rtems6/diagnostic] Error 2

Error: cast from 'void*' to 'int' loses precision [-fpermissive]
Rtems for 64bit is not yet supported.

42.1 Windows DDCI_PCR:5211 Known Failure GdbVariables.Rtems
GdbVariables.OneThreadRMA 		QEMU-ARM (qemu-arm)
QEMU-X86 (qemu-x86)
QEMU-PPC (qemu-ppc) 		Timeout after: 5000 ms.: can't find stack frame: Thread #1 34144256 (Suspended : Signal : SIGSEGV:Segmentation fault) -> worker
44 Linux PCR:15199 Known Failure RunPalExtension QEMU-X86 (qemu-x86)
QEMU-AARCH64 (qemu-aarch64) 		media:sales-kismet-24a-linux-qemuX86-empty-video-stream-7-15-2024.png The Video Stream is blank after an Update Target Load.

FIXED!! Testing Notes

ID Priority OS PCR Status Affected Tests Target Screenshot Comments
1F Linux PCR:15796 Known Failure Launching qemu emulator QEMU-X86_64 (qemu-x86_64) media:linux-qemu-x86_64-emulator-failure-20240621.txt
media:linux-qemu-x86_64-emulator-failure-20240621.png 		qemu x86_64 emulator fails to launch.
Each of the OA Linux vm's had to be modified by KL to 'enable nested virtualization' which causes kvm to be installed so that the qemu-x86_64 can be launched
2F Linux Known Failure Adding a dependency to the platform DeosNAI68INT6-1 (nai68int6) media:sales-kismet-24a-linux-nai68int6-adding-dependencies-build-error-6-21-2024.txt
media:sales24a-kismet-nai68int-adding-dependencies-20240622.png 		Adding dependencies to the platform results in build errors.
Adding both hello-world and health-monitor-configuration as dependencies resulted in a similar build error.
[lcj] The nai68int6 bsp's target is Intel 80X86

The OA test harness' messages file selected for testing the board/bsp combination is DEOS_PPC_DEOSNAI68PPC2.txt, which defines "target=Power PC".
Selecting the DEOS_80X86_DEOSNAI68INT6-1 config for the test run should fix the problem.

3F Linux Known Failure Run.dvmssimple-raw DeosZCU102-2 (zcu102) media:zcu102-with-dvmssimple-rax-example-failure-20240623.png The dvmssimple-raw example is integrated with zcu102. After an update target load, and waiting about a minute or so, the Error in Video Stream Communication dialog is displayed with the error "No route to host"
This appears to be a problem with the -2 board
Moved the testing to the -1 board
4F Linux DDCI_PCR:5161 Known Failure Debug.dvmsbasher-raw
Run.dvmsbasher-raw 		DeosT1042D4RDB-1 (t10xx) media:dvmsbasher-raw-UTL-t10xx-20240623.png
media:dvmsbasher-raw-connection-error-t10xx-20240623.png 		When the dvmsbasher-raw example is integrated with the t10xx bsp, the Load List Manger fails to connect following an update target load.
Per CP, The basher examples are not ready for prime time and should not be tested.
5F Linux DDCI_PCR:5161 Known Failure Run.dvmsbasher-with-exfat
Run.dvmsbasher-with-journaled-exfat 		DeosZCU102-1 (zcu102) media:zcu102-with-dvmsbasher-with-exfat-failure-20240625.png After copy-for-editing of the ram.dvms.xml and updating it's content, the No Route to host dialog is displayed following an update target load.
Per CP, The basher examples are not ready for prime time and should not be tested.
6F Windows Known Failure 133 tests fail due to communication error DeosNAI68ARM2-1 (nai-ultrascale) media:DeosNAI68ARM2-1-nai-ultrascale-communication-error.png
media:dvmsbasher-raw-utl-data-nai-ultrascale-20240625.png 		Connection refused: connect following update target load
Integrating the dvmsbasher-raw example is one way to reproduce the problem
Unchecking config.vfile.bcfg in the UpdateTargetLoad dialog seems to resolve the problem.
Shouldn't either config.dvms.bcfg OR config.vfile.bcfg be downloaded - not both?
Per CP, The basher examples are not ready for prime time and should not be tested.
7F (was 12) CP Linux
Windows 		DDCI_PCR:5137 Known Failure Debug.espi-nxp-read
Debug.espi-nxp-write
Run.espi-nxp-read
Run.espi-nxp-write 		DeosLS1043ARDB-1 (ls1043ardb)
DeosLS1088ARDB-1 (ls10x8ardb) 		media:ls1043ardb-with-espi-nxp-read-example-output-20240614.txt Error: Process Template (espi-nxp-read) uses feature set (espi-nxp), which is not present.

Error: Process Template (espi-nxp-write) uses feature set (espi-nxp), which is not present.
espi is only applicable to nai68ppc2 and t2080rdb.
LCJ 07/01 updated test whitelist accordingly.

8F (was 16) CP Windows
Linux 		Known Failure deos.DvmsMal DeosZCU102-1 (zcu102)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosNAI68ARM2-1 (nai-ultrascale) 		media:zcu102-DvmsMal-failures-20240625.txt Disk /dev/ram check... ERROR 16 is displayed on the video stream when the dvms basher examples are tested.
Per CP, the dvms basher examples are not ready for prime time and should not be tested.
dvms basher examples were removed from the test workspaces.
9F (was 28) Linux DDCI_PCR:5189 Known Failure GccFileExtensions QEMU-X86_64 (qemu-x86_64) Test uses incorrect option for x86_64 when launching assembler. Needs to be updated to use '-march=x86-64' option instead of '-Wa,-march=x86-64' option. KT writing pcr.

Update 7-2-24: fixed as of most recent commit in listed pcr.
10F (was 36) Linux Known Failure DeosOptionTabs.bootImageTabTest QEMU-X86_64 (qemu-x86_64) media:sales-kismet-24a-linux-qemuX86_64-icount-emulator-fail-7-1-2024.txt The test adds 'startqemu -v -a '-icount align=off,shift=0,sleep=off' as a command in the boot image tab. After applying this change, the emulator fails to launch, and the following message is seen in the console:

qemu-system-x86_64: -icount is not allowed with hardware virtualization.

Update 7-3-24: Changed test to not modify command if testing on QEMU-X86_64. Checked into 12.3.0 release management https://deos.ddci.com/viewsvn/DDCI?view=revision&revision=107069.
4F CP Linux DDCI_PCR:5183 Pass Run.dvmssimple-with-exfat DeosT1042D4RDB-1 (t10xx) media:t10xx -with-dvmssimple-with-exfat-example-output-20240623.txt
media:t10xx-with-dvmssimple-with-exfat-example-output-20240701.txt 		Expected output for the example is not displayed on the video stream. Usage of

std::atomic with bool type appears to be the culprit.
LJ 07/01 retested with DDS built on 07/01, and the test fails due to the expected output not being displayed.
LJ 07/15: Retested with DDS built on 7/11, and the test passed.

5F CP Linux DDCI_PCR:5183 Pass Run.dvmsthroughput-with-exfat DeosT1042D4RDB-1 (t10xx) media:t10xx -with-dvmsthroughput-with-exfat-example-output-20240623.txt
media:t10xx-with-dvmsthroughput-with-exfat-example-output-20240701.txt 		Expected output for the example is not displayed on the video stream. Usage of

std::atomic with bool type appears to be the culprit.
LJ 07/01 retested with DDS built on 07/01, and this test fails due to the expected output not being displayed.
LJ 07/15: Retested with DDS built on 7/11, and the test passed.

20F MS Windows
Linux 		PCR:15573 Pass Debug.ist-partition2 DeosCOMe-cTL6-2 (come-ctl6-x86_64) media:ist-partition2-come-ctl6-x80_64-error-20240625.png
media:ist-partition2-come-ctl6-x80_64-utl-info-20240625.png 		ist-partition2 is not running on the target after an update target load, when ist-simple-configuration is integrated.

26 June 2024 (M. Sygrove) An update to the example is under development
LJ 06/28: created a new image to get updated examples, re-ran the test and it passes now

21F CP Windows
Linux 		DDCI_PCR:4881 Pass Debug.vfile_demo
Debug.vfile_logbook_partition1
Run.vfile_demo
Run.vfile_logbook_partition1 		DeosCOMe-cTL6-2 (come-ctl6-x86_64)
QEMU-X86_64 (qemu-x86_64) 		media:vfile_demo-80x86_64-build-errors-20240625.txt
media:vfile_logbook_partition1-80x86_64-build-errors-20240625.txt 		Link error:cannot find -lvfile-api653p2
Shayne is rebuilding with x86_64 support.
7-9-24: Pass after re-run.
22F LJ Windows
Linux 		PCR:5186 Pass ExternalDebugging DeosCOMe-cTL6-2 (come-ctl6-x86_64) media:ExternalDebugging-80x86_64-setup-error-20240626.txt ScoreCommands.getReadelfTargetString() is returning the incorrect value for 80x86_64.
OA needs an update for the Sales release.
LCJ 06/26: Created a new OA and re-ran the tests. They pass now.
37.1F JK Linux Pass Run.hello-world-ist
Debug.hello-world-ist 		QEMU-X86_64 (qemu-x86_64) media:sales-kismet-24a-qemuX86_64-hello-world-ist-load-list-issue-7-8-2024.png Update 7-8-24: An Update Target Load for this example results in a blank Video Stream. The 'Connect Load List Manager' progress bar does not complete, and eventually the "Error In Load List Manager Communication" Read timed out dialog displays Neither Load List or Status Monitor can be enabled after Update Target Load, they will timeout.
Note: John K. is looking into the ftp connection issues causing the read timed out.
Update 7-10-24: Using latest ist-application unrelease, example runs succesfully.
37.2F JK Linux Pass Run.partition1
Run.partition2
Debug.partition1
Debug.partition2 		QEMU-X86_64 (qemu-x86_64) Update 7-8-24: An Update Target Load for these examples results in the Video Stream outputting the correct content. However, the 'Connect Load List Manager' progress bar does not complete, and eventually the "Error In Load List Manager Communication" Read timed out dialog displays. Neither Load List or Status Monitor can be enabled after Update Target Load, they will timeout.
Note: John K. is looking into the ftp connection issues causing the read timed out.
Update 7-10-24: Using latest ist-application unrelease, example runs succesfully.
37.3F JK Linux Pass Run.partition-1
Debug.partition-1 		QEMU-X86_64 (qemu-x86_64) media:sales-kismet-24a-qemuX86_64-ist-partition-1-load-list-issue-7-8-2024.png Update 7-8-24: An Update Target Load for this example results in the Video Stream outputting an error message (see screenshot).Also, the 'Connect Load List Manager' progress bar does not complete, and eventually the "Error In Load List Manager Communication" Read timed out dialog displays. Neither Load List or Status Monitor can be enabled after Update Target Load, they will timeout.
Note: John K. is looking into the ftp connection issues causing the read timed out.
Update 7-10-24: Using latest ist-application unrelease, example runs succesfully.
18F Adina/Eliecer Windows
Linux 		PCR:15772 Pass Debug.ext-clock-sync
Run.ext-clock-sync 		DeosCOMe-cTL6-1 (come-ctl6) The example does not contain the expected ext-clock-sync-example.fp.xml file (only a pd.xml)
The bsp user guide has a note: If running the example on a 32-bit x86 target, before you load and execute the example, the ext-clock-sync-example.fp.xml must be modified. Open this file for editing under ext-clock-sync -> xml and search for libpal.so. Replace the string libpal.so with pal.dll and save the file.

ALR: The step documented in the BSP UG is no longer necessary. PCR 15772 was created to update the BSP UG.
LCJ(06/26): Updated the oa test harness to no longer do any special configuration for the example when testing on 80x86.
Re ran both tests, and they pass now.

38 KT Windows DDCI_PCR:5137 Pass projectOptions.other.DeosOptionTabs.integrationToolTabTest DeosT1042D4RDB-1 (t10xx)
DeosLS1043ARDB-1 (ls1043ardb)
DeosZCU102-1 (zcu102)
DeosShakaMX8-1* (imx8qm-a72-aarch64)
DeosNAI68ARM2-1 (nai-ultrascale)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosShakaMX8-1* (imx8qm-aarch64)
DeosT2080RDB (t2080rdb)
DeosNAI68INT6-1 (nai68int6) 		media:TBD FAIL Sat Jul 06 15:45:14 EDT 2024: desk basecon.pia.xml version (3.62.1) and workspace qemu-aarch64/xml/basecon.pia.xml version (3.62.1) should have a difference in the major or minor digits.

FAIL Sat Jul 06 15:45:14 EDT 2024: workspace's qemu-aarch64/xml/basecon.pia.xml version (3.62.1) should be equal in the major and minor digits to the version of the installed integration tool (3.63.0)
LJ 07/15: Retested with the 7/11 DDS and the t10xx (t1042d4rdb-1) and it passed.

43F Linux PCR:5137 Pass DeosOptionTabs.bootImageTabTest QEMU-X86 (qemu-x86) media:sales-kismet-24a-qemuX86-bootImage-fail-7-15-2024.png
media:sales-kismet-24a-qemuX86-build-warnings-after-command-change-7-15-2024.txt 		The test adds 'startqemu -v -a '-icount align=off,shift=0,sleep=off' as a command in the boot image tab. After applying this change, the emulator fails to launch, and the following message is seen in the console:
qemu-system-x86_64: -icount is not allowed with hardware virtualization.
This is somewhat strange as the platform is clearly x86 and not x86-64.

Note: The last time OA had run this test for qemu-x86 was in February (https://deos.ddci.com/ddciWiki/OpenArbor_12.0.2_Test_Plan_and_Report_Sales_Kismet_23A-x86), in which the test passed. There has been no change to the boot command used in the test since then. Changing the boot command to 'startqemu' does allow for a successful launch and pinging of the emulator.

RLF: I am ok with this for qemu-x86. Our x86 support will focus on qemu-x86_64 going forward. The 64 in the name of the system executable is fine. ppc is qemu-system-ppc64.exe and we only support 32 bit targets. Is the difference related to host vms: oalinux02 vs testlinux01? If the purpose of the test is to ensure options are passed through, can we find a different option that is always present? If we want to integration test with icount, then we may need to define more configuration aspects to where we can run this test (Cygwin, different linux vm, setup a native Linux workstation, etc).
7-16-24: Test updated to not modify boot command on x86_64 and 80x86 qemu's, when the test environment is Linux, preventing the failure.

Retrieved from "https://ddci.zapto.org/ddciWiki/index.php?title=OpenArbor_12.3.0_Test_Plan_and_Report_Sales_Kismet_24A&oldid=64893"