OpenArbor 12.1.0 Test Plan and Informal Report
From DDCIDeos
Jump to navigationJump to search
About
OpenArbor Windows/Linux 12.1.0
SVN Revision: r105942
SVN Branch Name: mainline
Test Schedule
| Scheduled Test Runs | Start Date | Due Date | Delivered | Percentage Complete |
|---|---|---|---|---|
| Formal | 02-16-2024 | tbd | tbd | 0% |
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.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\Release12.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. |
| 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 | Docker image customer-shaka unreleased components | n/a | ARM | QEMU-ARM (qemu-arm) | Launcher | OALinux01 | LJ | X | See testing notes |
| Deos | Docker image customer-shaka unreleased components | n/a | AARCH64 | QEMU-AARCH64 (qemu-aarch64) | Launcher | OALinux02 | NH | X | See testing notes |
| Deos | DDS-shaka-deos-kismet-20240216 + unreleased OA + needed unreleased Deos components | n/a | AARCH64 | QEMU-AARCH64 (qemu-aarch64) | Launcher | testw10e2 | NH | X | Windows Cygwin 2022 See testing notes |
| Deos | DDS-tostones3-deos-jupiter-20240118+new stable + unreleased OA + needed unreleased Deos compoents | n/a | ARM | QEMU-ARM (qemu-arm) | Launcher | testw10e1 | NH | X | Windows Cygwin 2018 See testing notes |
| Deos | DDS-loewen-deos-europa-20230117+new stable + unreleased OA | n/a | ARM | QEMU-ARM (qemu-arm) | PlatformIntegration | oatestlap | LJ | X | Windows Cygwin 2018 See testing notes |
Unreleased Packages
The environment for testing is encoded in the bdu64-shaka script:
https://deos.ddci.com/scm/Deos/maintainer-tools/docker/branches/mainline/bdu64-shaka
I.e.,:
svn up ~/scm/Deos/maintainer-tools/docker/branches/mainline ~/scm/Deos/maintainer-tools/docker/branches/mainline/bdu64-shaka kismet customer-shaka
Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | Linux (Kismet) | DDCI_PCR:5050 | Known Failure | Run.health_monitor |
QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:health-monitor-arm-run-errors-03052024.txt | The output on the video stream does not match the expected output | |
| 3 | Linux (Kismet) | PCR:15247 | Known Failure | BuildAll.kernelModeCalculatorPRL | QEMU-ARM (qemu-arm) | media:kernelModeCalculatorPRL-arm-build-errors-02192024.txt | Instrumented builds fail for this example make[1]: *** [/OpenArbor/openarbor-common/compiler-rules.mk:235: inst_kernelModeCalculatorPRL.s_] Error 1 | |
| 7 | 01:CF/JD | Linux (Kismet) | PCR:tbd | Fail | Debug.rtems-partition1 | QEMU-ARM (qemu-arm) | media:rtems-partition1-debug-arm-errors-03062024.png | 03-06[lcj]created a new image to rerun this test gdbserver exception Failed to execute MI command: -break-insert -t -f " " Can reproduce for partition 1, but for all other partitions can spawn debug sessions without problem - JD |
| 8 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:4932 | Known Failure | MulticoreIntegration | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
This test requires an update to work properly with BSPs that support pia. | ||
| 10 | Linux (Kismet) | DDCI_PCR:5050 | Known Failure | Run.demo653 | QEMU-ARM (qemu-arm) | This test requires an update for this example, the output of the example has changed. New line 'Periodic Loop Count: nnn' | ||
| 11 | Linux (Kismet) Windows (Kismet) |
PCR:15344 | Known Failure | Run.zlib-compress | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
Media:sales-kismet-23a-zlib-compress-video-stream-output-12-21-2023.png | No Pattern Defined for zlib-compress. Output appears to be overlapping: zlib-compress example: finished!ceLen=4A52E/desk/help/deos-zlib-examples-user-guide.htm does not include the zlib-compress example. | |
| 12 | Linux (Kismet) Windows (Kismet) |
PCR:15160 | Known Failure | deos.CacheTrasher MakeExport.worker |
QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:cacheTrasher-qemu-arm-fail-12-18-2023.txt media:worker-qemu-arm-fail-12-18-2023.txt |
The kernel example cache-trasher's ipal and hpal projects have build errors | |
| 13 | crittime not installed | Linux (Kismet) Windows (Kismet) |
Known Failure | deos.DeosCrittimeTest | QEMU-ARM (qemu-arm) | Timeout after: 5000 ms.: The widget ToolItem with tooltip text {Clear Crittime} was not enabled. DDS does not contain a crittime kernel /desk/ppc/appbin/crittime/libkernel.so does not exist | ||
| 13.5 | Linux (Kismet) Windows (Kismet) |
PCR:15234 | Known Failure | deos.DeosCrittimeTest | QEMU-AARCH64 (qemu-aarch64) | Timeout after: 5000 ms.: The widget ToolItem with tooltip text {Clear Crittime} was not enabled. DDS does not contain a crittime kernel /desk/ppc/appbin/crittime/libkernel.so does not exist | ||
| 14 | Linux (Kismet) Windows (Kismet) |
PCR:15221 | Known Failure | All BuildAll tests DeosABCTest.ConfigErrorCheck DeosABCTest.multi DeosABCTest.one VariantSpecificItFiles.variantItFilesForExeProject MultipleBuildConfigs DeosOptionTabs.abcToolTabTest |
QEMU-AARCH64 (qemu-aarch64) | media:a-deos-process-linux-kismet-2-22-2024.txt | /desk/bin/instrument --index=index.txt --format=GNU --arch=AARCH64 --assembly=aDeosProcess.s < aDeosProcess.s_ > inst_aDeosProcess.s_ Can't locate GNUAARCH64Postprocessing.pl in @INC (@INC contains: /desk /desk/bin /desk/lib/abcscat /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.34.0 /usr/local/share/perl/5.34.0 /usr/lib/x86_64-linux-gnu/perl5/5.34 /usr/share/perl5 /usr/lib abc not supporting 64-bit | |
| 15 | Linux (Kismet) | DDCI_PCR:tbd | Known Failure | DeosGdbLaunchConfigurations.deosGdbMultipleRemoteTargets | QEMU-ARM (qemu-arm) | media:deosGdbMultipleRemoteTargets-arm-errors-02202024.txt media:deosGdbMultipleRemoteTargets-arm-errors-02202024.png |
Error: tap-host-ip-mask "192.168.19.109/31" must be of the form N.N.N.N with an optional "/M"where N is between 0 and 255 and M is between 1 and 31 (all inclusive). mask "31" is not in 1..31 Update 1/31/2024: AL mentions desk-python-tools:4.24.0 should have the fix to this error. The test needs an update to create the second emulator correctly on linux | |
| 17 | Windows | DDCI_PCR:4572 | Known Failure | deos.timemap.TimeMapUI mld.stopPoints.GutterClicking |
QEMU-ARM (qemu-arm) | Test update is needed to more accurately use the mouseMove() function to retrieve time map information and to click Toggle Breakpoint. | ||
| 18 | 01:SD | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:tbd | Known Failure | GdbVariables.Deos653 | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:gdbVariables-deos653-arm-failure-02262024.txt media:gdbVariables-deos653-arm-resume-failure-02262024.png |
Resume after setting bp results in internal-error SD: 653 Runtime Issue: Uncertainty surrounding the task being stepped and the task halted. Client gets lost. Workaround: Once debugger attaches, show breakpoints in Debugger Console and delete the last breakpoint placed in trap.h. |
| 18.5 | 02:SD | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:tbd | Fail | GdbVariables.MultipleThreadsRMA | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:gdbVariables-MultipleThreadsRMA-arm-bp-failure-02262024.png | Function local variables are not reported as modified after a Resume as expected. A bp appears to be set at line 64, but after a Resume, the program stops at line 59. This is where the previously set (and removed bp) was located for testing global vars. SD: Unable to replicate behavior. Successsfully halts at correct location of the next breakpoint. |
| 19 | 02:SD | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:tbd | Fail | GdbVariables.OneThreadRMA | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:gdbVariables-oneThreadRMA-arm-bp-failure-02262024.png media:gdbVariables-oneThreadRMA-threadlocal-arm-bp-failure-02262024.png |
Testing function local variables fails A bp appears to be set at line 65, but after a Resume, the program stops at line 60. This is where the previously set (and removed bp) was located for testing global vars. Doing a second Resume gets to the bp at line 65. But, the function local variable is not modifed after a Step/Over is done. When tread local variables are included in building the example project, a similar problem occurs. A bp appears to be set at line 62, but after a Resume, the program is not stopped at the bp, but some other location. A second Resume is needed to get to the bp The global thread local variable's value is not properly modified. SD: Unable to replicate behavior. Successfully halts at the valid location of next breakpoint. Variables are updated with correct values. |
| 20 | 02:CF | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:tbd | Fail | GdbVariables.Rtems | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:gdbVariables-rtems-arm-failure-03062024.png | The debugging session for the test project cannot be started. 03-06[lcj]created a new image to rerun this test gdbserver exception, see screenshot emulator display Update: When trying to debug the application, OA shows the following error: |
| 21 | 02:SD | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:tbd | Fail | LaunchGdbTest | QEMU-ARM (qemu-arm) | media:LaunchGdbTest-arm-debugger-console-output-02212024.txt media:LaunchGdbTest-arm-02212024.png |
A breakpoint is set, but not encountered after a Resume. SD: Unable to replicate behavior. Successfully resumes and halts and breakpoint. |
| 22 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:4930 | Known Failure | MinimalFileSystem.hello-world-mfs MinimalFileSystem.mms-configuration |
QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
This test requires an update to work properly with BSPs that support pia. | ||
| 23 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:5014 | Known Failure | other.RenameProjects | QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
Media:renameprojects-qemu-arm-12-19-2023.txt | When the qemu platform project is renamed, the launching of the emulator displays an error. | |
| 24 | Windows | PCR:15143 | Known Failure | Debug.mms_partition4 | QEMU-ARM (qemu-arm) | QEMU-ARM's performance has dropped significantly. 'norm-proc4' thread takes over 15 minutes to spawn in 'mms_partition4'. | ||
| 25 | Windows | PCR:15143 | Known Failure | Run.except | QEMU-ARM (qemu-arm) | Media:loewen-d2-except-output.txt | The media link displays the output captured from running the except example. The example doesn't display all necessary output. Work around to increase budget: <threadTemplate name = "mainThreadTemplate" budget = "670"
| |
| 28 | Linux (Kismet) Windows (Kismet) |
PCR:15192 | Known Failure | Compile.psio-print Run.psio-print Debug.psio-print MakeExport.psio-print |
QEMU-AARCH64 (qemu-aarch64) | Media:psio-print_errors_2-22-24.txt | ../../../code/psio-print.cpp:29:53: error: cast from 'const PlatformSpecificInfoTYP*' {aka 'const PlatformSpecificInfo*'} to 'uint32_t' {aka 'unsigned int'} loses precision | |
| 29 | 01:JD | Linux (Kismet) Windows (Kismet) |
PCR:15231 | Known Failure | Compile.rtems-cpu-usage Compile.rtems-hm-partition1 Compile.rtems-partition1 Compile.rtems-partition2 Compile.rtems-partition3 Compile.rtems-partition4 Compile.rtems-socket-example Debug.rtems-cpu-usage Debug.rtems-hm-partition1 Debug.rtems-partition1 Debug.rtems-partition2 Debug.rtems-partition3 Debug.rtems-partition4 Debug.rtems-socket-example Run.rtems-cpu-usage Run.rtems-hm-partition1 Run.rtems-partition1 Run.rtems-partition2 Run.rtems-partition3 Run.rtems-partition4 Run.rtems-socket-example MakeExport.rtems-cpu-usage MakeExport.rtems-hm-partition1 MakeExport.rtems-partition1 MakeExport.rtems-partition2 MakeExport.rtems-partition3 MakeExport.rtems-partition4 MakeExport.rtems-socket-example Clean.rtems-cpu-usage Clean.rtems-hm-partition1 Clean.rtems-partition1 Clean.rtems-partition2 Clean.rtems-partition3 Clean.rtems-partition4 Clean.rtems-socket-example Debug.arinc653-partition Run.arinc653-partition RtemsLinkOptions.cpp_additional_options RtemsLinkOptions.cpp_libraries RtemsLinkOptions.cpp_objects RtemsLinkOptions.cpp_outputs rtemsAsm.RtemsAssemblerAdditionalOptions rtemsAsm.RtemsAssemblerCodeGeneration rtemsAsm.RtemsAssemblerDirectories rtemsAsm.RtemsAssemblerPreprocessor rtemsCompile.RtemsCCompileAdditionalOptions rtemsCompile.RtemsCCompileCodeGeneration rtemsCompile.RtemsCCompileDirectories rtemsCompile.RtemsCPreprocessor rtemsCompile.RtemsCppCompileAdditionalOptions rtemsCompile.RtemsCppCompileCodeGeneration rtemsCompile.RtemsCppCompileDirectories rtemsCompile.RtemsCppCompilePreprocessor StatusMonitor SuperMakefile |
QEMU-AARCH64 (qemu-aarch64) | Media:rtems_errors_2-22-24.txt | rtems projects do not build. Aarch64 does not support rtems yet. JD - RTEMS projects do build, but currently Socket encounters processor violations that must be avoided by explicitly defining alignment for socket address and socket length variables. IPC also has violations, and can be avoided by removing a zero-initialization of a pthread attribute declaration. |
| 31 | Linux (Kismet) Windows (Kismet) |
PCR:15358 | Known Failure | Debug.mms_partition1 Debug.mms_partition2 Debug.mms_partition3 Debug.mms_partition4 Run.mms_partition1 Run.mms_partition2 Run.mms_partition3 Run.mms_partition4 |
QEMU-AARCH64 (qemu-aarch64) | This example requires a .pia.xml file to be created to configure WAT, windows and schedulers.
Need to fix 653 examples | ||
| 34 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:4051 | Known Failure | ProjectConverter | QEMU-AARCH64 (qemu-aarch64) | This test needs to be updated. | ||
| 35 | Linux (Kismet) Windows (Kismet) |
PCR:15160 | Known Failure | Run.auto-tune ExternalDebugging.noLoadList ExternalDebugging.partialLoadList |
QEMU-AARCH64 (qemu-aarch64) | 'Unable to allocate 0x20 bytes of TLS. Allocate at least this much...' Seen in Video Stream. Status Monitor shows 'Insufficient tls quota' ProcessEvent. | ||
| 36 | 01:PZ | Linux (Kismet) Windows (Kismet) |
PCR:14055 | Known Failure | RunPalExtension | QEMU-AARCH64 (qemu-aarch64) | media:aarch64-pal-extension-video-stream-3-6-24.png | Empty videos stream when running pal-extension on aarch64. Confirmed correct output populates video stream on qemu-arm. PZ: The pal-extension is not supported in qemu-aarch64 yet. The blank screen is expected behavior. See PCR 14055. |
| 37 | Linux (Kismet) | PCR:14080 | Known Failure | CacheTrasher | QEMU-AARCH64 (qemu-aarch64) | Cache Trashing is not supported on the qemu-aarch64 platform. | ||
| 38 | Linux (Kismet) | DDCI_PCR:5077 | Known Failure | DeosGdbLaunchConfigurations.deosGdbMultipleRemoteTargets | QEMU-AARCH64 (qemu-aarch64) | media:deosGdbMultipleRemoteTargets-failure-2-23-24.png | Launching debug session on hello-world_debug_configuration gets stuck at 46%. Works fine with 1 target. After adding second remote target 192.168.19.110, updating platform's lwip.config to reference second target's IP, adding '-tap-host-ip-mask=192.168.19.109/31' to boot image command, the debug session fails to launch (Error in Load List Manager Communication). AL: The instructions you presented are a mix of Cygwin and Linux. Cygwin uses IP addresses with /24 netmask, Linux uses /31. If there were instructions before for how to run this test on Cygwin, you should follow those. On linux the procedure you describe is close, but the IP addresses are different and the netmask is /31. | |
| 39 | 01:AL | Linux (Kismet) | Fail | ExternalDebugging.noLoadListMfs | QEMU-AARCH64 (qemu-aarch64) | media:noLoadListMfs-failure-2-23-24.png | Launching debug session on hello-world-mfs causes an error. Replicate by checking out https://deos.ddci.com/svn/DDCI/products/openarbor/openarbor/branches/mainline/TestResources/MinimalFileSystems/hello-world-mfs/, then using OA's File Import, General, Existing project into workspace. AL: SCATHitmap is not owned by LwIP. Adding SCATHitmap as an owned resource causes the network process to get a process event "File system auto mount error", which is log message ID file_system_auto_mount_error, which is mentioned in the kernel UG, but the description is not helpful in diagnosing the issue. I added mountQuota to network's pd.xml, no help. I'm not sure why LwIP would be automounting SCATHitmap. I have to quit for the night. Hopefully someone else can pick this up. | |
| 40 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:4926 | Known Failure | NewProjectValidation.createPlatformProjectWithIncludedHypFiles | QEMU-AARCH64 (qemu-aarch64) | Error when creating platorm project `test-qemu-aarch64' was not reported as expected. | ||
| 41 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:4938 | Known Failure | ShowVasLayout | QEMU-AARCH64 (qemu-aarch64) | media:ShowVasLayout-aarch64-linux-kismet-10-17-2023-2.png | gap in VAS coverage. Expected: 0x100000000, got: 0x0 This is an OA issue not a SM issue. Wireshark shows SM sent 0x100000000 but OA only displayed the least significant 32-bits. Also the command line SM reports the correct value. | |
| 42 | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:4922 | Known Failure | ManagedBuild.BareAarch64Test ManagedBuild.testLinkWithCdt ManagedBuildProperties.BareAarch64Test |
QEMU-AARCH64 (qemu-aarch64) | The ManagedBuild OA plugin does not yet support 64-bit architectures. | ||
| 43 | Linux (Kismet) | Expected Deviation | AboutDDCITools GeneralTest |
QEMU-AARCH64 (qemu-aarch64) | Media:shaka-d2-10-13-23-dds-name-error.png | DDS Name was not properly displayed. when testing with an image created with the bdu64 script, the DDS label.txt is not is not installed formal testing with an official docker image should be ok. | ||
| 44 | Linux (Kismet) Windows (Kismet) |
Expected Deviation | DebugOptionsAdditionalOptions DebugOptionsMessages DebugOptionsStartup DeosLaunchConfigurations.commonTabs DeosLaunchConfigurations.deosMldLaunching DeosTargetManager.testF11 DwarfDump.auto-tune DwarfDump.auto-tune-library |
QEMU-AARCH64 (qemu-aarch64) | MLD is not installed on Linux MLD does not support 64bit archs | |||
| 45 | Linux (Kismet) | DDCI_PCR:5070 | Known Failure | DeosOptionTabs.integrationToolTabTest | QEMU-AARCH64 (qemu-aarch64) | media:sockets653-qemu-aarch64-xml-integrationToolTabTest-validation-error.txt | This test failed due to 2 separate problems.
(1) The IT tool, as all xml tools, will up-convert xml files based only on a difference in the major.minor digits. The debug digit is ignored. The XMLValidation() function of DeosOptionTabs has already been updated to reflect this during pia updates for the integrationToolTabTest. The testXmlToolVersion() function will need similar updates. This caused the following failures, as the test expected the debug digit to cause a conversion, which is not expected behavior: | |
| 46 | 01:CF | Linux (Kismet) | Fail | Deos653GdbTest | QEMU-AARCH64 (qemu-aarch64) | media:Deos653GdbTest-failure-3-11-24.png media:Deos653GdbTest-failure-3-14-24.png |
The test is failing saying that some threads never suspended. Screenshot shows all 3 threads in debug view are suspended. Test update needed? Update: | |
| 47 | Windows (Kismet) | Fail | MLD tests mld.Suspend mld.TerminateWhileRunning mld.EnableDisableTrace mld.EnableDisableLogFile Debug.hello-world |
QEMU-ARM (qemu-arm) | media:MldTests-failure-03-21-24.png | MLD reports "DF-227-ERROR: Communication with cross target has not been established" when launching an MLD debugging session. mld-arm exe is left running in Task Manager |
Fixed! Testing Notes
| ID | Priority | OS | PCR | Status | Affected Tests | Target | Screenshot | Comments |
|---|---|---|---|---|---|---|---|---|
| 1 | Linux (Kismet) | DDCI_PCR:tbd | Fail | BuildAll.health_monitor | QEMU-ARM (qemu-arm) | media:health-monitor-arm-build-errors-02172024.txt | link error:cannot open linker script file ../../../code/health_monitor_example.dynamic-list: No such file or directory The health_monitor example was removed from the test workspace 03-05[lcj]created a new image and reran these tests and BuildAll.health_monitor passed today. | |
| 2 | Linux (Kismet) Windows (Kismet) |
PCR:15358 | Known Failure | BuildAll.interrupt Compile.interrupt Debug.interrupt Run.interrupt MakeExport.interrupt |
QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
media:interrupt-arm-build-errors-02172024.txt | interrupt.cpp fails to compile due to missing types (e.g. INTERRUPT_ID_TYPE, CREATE_INTERRUPT, etc) 03-11[lcj]MS has removed the interrupt example from the desk in the kismet baseline | |
| 4 | 01:CF | Linux (Kismet) | PCR:15521 | Known Failure | Debug.vfile_demo | QEMU-ARM (qemu-arm) | media:vfile-demo-arm-debug-errors-03052024.png | 03-05[lcj]created a new image to rerun this tests The debug session failed to display the confirm perspective switch dialog. After an Update Target Load, vfile_demo is not available in the Status Monitor to be selected to launch a debugging session
|
| 5 | 01:CF | Linux (Kismet) | PCR:15521 | Known Failure | Debug.vfile_logbook_partition1 Run.vfile_logbook_partition1 |
QEMU-ARM (qemu-arm) | media:vfile-logbook-partition1-arm-run-errors-03052024.txt | 03-05[lcj]created a new image to rerun these tests video stream does not contain the expected output
|
| 6 | Linux (Kismet) | PCR:tbd | Known Failure | 653 examples | QEMU-ARM (qemu-arm) | MS fixed the 653 examples to have version 28! | ||
| 7.25 | 03:SD | Linux (Kismet) | PCR:tbd | Fail | Debug.sockets653 | QEMU-ARM (qemu-arm) | media:sockets653-debug-arm-errors-03062024.png | 03-06[lcj]created a new image to rerun this test gdbserver exception, see screenshot emulator display SD: Successfully replicated error. Common issue with not being able to attach to a 653 project that has breakAtStartup enabled. 03-11[lcj]created a new image w/ unreleased gdbserver to rerun this test, and it passed. |
| 7.5 | Linux (Kismet) | PCR:tbd | Fail | Debug.rtems-hm-partition1 | QEMU-ARM (qemu-arm) | media:tbd | 03-06[lcj]created a new image to rerun this test Passed when rerun on 0306 | |
| 9 | 01:MS | Linux (Kismet) Windows (Kismet) |
DDCI_PCR:tbd | Fail | Run.custom-io-partition1 Run.custom-io-partition2 Sybil |
QEMU-ARM (qemu-arm) QEMU-AARCH64 (qemu-aarch64) |
On Linux, the first line of output 'Custom IO example' is displayed once, then disappears. | |
| 16 | Linux (Kismet) | DDCI_PCR:tbd | Fail | NewProjectValidation.checkNonProjectFolderInWorkspace | QEMU-ARM (qemu-arm) | media:checkNonProjectFolderInWorkspace-arm-errors-02202024.txt | The cd.xml file is not found in the workspace folder shared-library as specified in the DDC-I Peferences Search Path Error: No rule to make target '/cygdrive/c/oaTestHarness/workspace/ddses/DDS-shaka-deos-kismet-20240206/deos_arm_qemu/workspace/startup-loaded-library/output/desk/etc/startup-loaded-library.cd.xml', needed by '../mfs-config.mk'.>03-05[lcj]created a new image and reran these tests passed today. | |
| 26 | o2:MS | Linux (Kismet) Windows (Kismet) |
PCR:15198 | Known Failure | Compile.demo653 Run.demo653 Debug.demo653 MakeExport.demo653 Compile.health_monitor Debug.health_monitor MakeExport.health_monitor |
QEMU-AARCH64 (qemu-aarch64) | Media:demo653_errors_2-22-24.txt | ../../../code/demo653.cpp:44:48: error: cannot convert 'uint32_t*' {aka 'unsigned int*'} to 'processRestartCount_t*' {aka 'long unsigned int*'} |
| 27 | Linux (Kismet) Windows (Kismet) |
PCR:15192 | Known Failure | Compile.ext-clock-sync Run.ext-clock-sync Debug.ext-clock-sync MakeExport.ext-clock-sync |
QEMU-AARCH64 (qemu-aarch64) | Media:ext-clock-sync_errors_2-22-24.txt | ../../../code/ext-clock-sync-example.cpp:128:34: error: cannot convert 'const volatile systemTickCount_t*' {aka 'const volatile long unsigned int*'} to 'const volatile uint32_t*' {aka 'const volatile unsigned int*'} in assignment | |
| 30 | 04:SD | Linux (Kismet) Windows (Kismet) |
Fail | Debug.buffer_semaphore | QEMU-AARCH64 (qemu-aarch64) | media:buffer_semaphore-arm-debug-linux-kismet-10-05-2023.png | Debugging session failed to Suspend. | |
| 32 | 04:SD | Linux (Kismet) Windows (Kismet) |
Fail | Debug.sockets653 | QEMU-AARCH64 (qemu-aarch64) | media:sockets653-qemu-aarch64-gdb-back-end-error.txt | Debug session never starts. Error message recieved from debugger back end. | |
| 33 | 01:CF | Linux (Kismet) Windows (Kismet) |
PCR:15521 | Known Failure | Debug.vfile_demo Debug.vfile_logbook_partition1 Run.vfile_logbook_partition1 |
QEMU-AARCH64 (qemu-aarch64) | media:vfile-demo-qemu-2-22-24.png media:vfile-logbook-partition1-qemu-2-22-24.png |
Error from the console when attempting to debug: Error: Bad process under test status from Deos Remote Debugger. status = 0x0The screenshot link shows what is in the qemu window.
|
