Deos Crucible 21B

From DDCIDeos
Jump to navigationJump to search


This release provides Crucible_Program with an aperiodic DDS release.

This page was constructed following the Create Release Wiki instructions.

Description

The previous distribution is at:

\\nx3000\ship\dds\windows\approved\DDS-crucible-deos-jupiter-20210421

The candidate distribution is at:

 \\ddsbuild.ddci.com\DDCI_integration\DDS-crucible-deos-jupiter-20210902
   ftp://redhat5.ddci.com//Workstation/cygwin-20180401-ddci-dist-jupiter/x86_64/archive/1630610911

Note: The candidate distribution was created as a new DDS using all latest stable components via the DDS Build Process.

Components to Work

Below are the Deos components that have been identified to work for this release. See also the list of FTP server symbolic links.

Components Version Phase CCB Who Remarks

Legend

CCB: A Release CCB has been held
Phases:

  • Dev - In Development
  • Test - Component unreleased and ready to test
  • Delta - A Delta baseline must be established
  • Audit - One (or more) SQA Audits must be performed (e.g., a Verification and/or Software Conformity Audit)
  • Stable - You are done! All steps (including test report) in the Deos Software Release HowTo or OpenArbor Development HowTo have been followed.

Who: The person responsible for doing the work associated with the component.

Remarks: Free form text. It must contain the test report when done.

Differences from Prior Release

Added/Modified Packages

New Packages

  • kfs-cvt - 1.0.0-2
  • socket-adapter-library - 1.0.0-1
  • vfileconfig - 1.0.1-1

Updated Packages

  • ansi - 4.8.4-2
  • bsp-examples - 1.3.0-3
  • crittime-tool - 4.0.0-3
  • deos-time - 3.0.0-5
  • deos653-config-win32 - 1.24.5-3
  • deos653-cvt - 2.0.0-3
  • deos653p1 - 5-1
  • deos653p1-runtime - 5.4.0-4
  • desk-python-tools - 4.18.1-1
  • ftpserver - 11.0.0-8
  • hyperstart - 9.5.0-2
  • imx8qm - 4.2.1-1
  • integ-tool-command-line - 3.57.0-9
  • ist-application - 2.1.0-1
  • ist-config-win32 - 1.1.0-1
  • kernel - 10.5.0-8
  • kernel-examples - 4.3.0-1
  • network-standard-apps - 1.5.4-1
  • pal-ext-stub - 2.1.0-3
  • qemu-vm - 3.0.0.2-1
  • registry-cvt-win32 - 2.0.0-8
  • socket-examples - 3.3.0-1
  • time-prl - 2.0.0-2
  • vfile - 4.0.1-1
  • vfile-examples - 2.0.0-4
  • zcu102 - 4.3.0-1

Removed Components

  • N/A

Unreleased Components

  • ist-arinc653-examples - 1.4.0-2
  • ist-ioi-examples - 1.4.0-2
  • mailbox-transport-library - 2.6.0-1
  • status-monitor - 11.2.0-1

DDS Test Summary

  • No OA testing required. Will leverage off testing for DDS-sales-deos-jupiter-20210902

Trac ARM Version 278 Test Report Trac 80x86 Version 278 Test Report Trac PPC Version 278 Test Report

Additional Testing

diff -rq DDS-sales-deos-jupiter-20210902 DDS-crucible-deos-jupiter-20210902
diff result


Known Problems

  • NOTE: OA Test Update items are not listed as known problems against the deos components.
ID Priority OS PCR Status Affected Tests Target Screenshot Comments
2 Windows n/a Expected Failure BuildAll.tx-duart-nxp
Debug.tx-duart-nxp
Run.tx-duart.nxp
QEMU-ARM (qemu-arm)
QEMU-X86 (qemu-x86)
DeosIMX8QM (imx8qm)
Error: Process Template (tx-duart-nxp) uses feature set (duart-nxp), which is not present. This example is only expected to work for ls1043A, ls1048a, t10xx and de-gpu.
3 Windows n/a Expected Failure BuildAll.trasher
BuildAll.worker
Debug.trasher
Debug.worker
Run.trasher
Run.worker
MakeExport.trasher
MakeExport.worker
All Targets Media:TrasherWorkerBuildFailure2.png Platform project fails to build when the Multicore-memory-pools example projects trasher and worker are integrated into the out of the box single core and/or single pool platform. The MulticoreIntegration test performs the BuildAll, Run and Debug tests for the multicore memory pools examples in a multicore/multi memory pool environment.
4 Windows PCR:13647 Known Issue Run.hello-world-ist
Debug.hello-world-ist
Debug.ist-ioi-to-host
All Targets Media:ist-ioi-to-host-failure.png
Media: hello-world-ist-failure.png
VideoStream output contains: Hello World 1 ioi_init failed, return status == 9
This example is hard-coded to expect ioiConfig.cfg to be on the loadlist, but shouldn't be anymore.
5 Windows Expected Failure Run.hello-world-timer
Debug.hello-world-timer
All Targets pi: Error #1: Caused by feature provider content to file (/desk/platform/qemu-arm/etc/platreg.pi.xml): Process Instance (hello-world-timer-process) owns undefined memory mapped resource (TIME_CONTROL)
Per MV, this is expected for these bsps. Each bsp must now add a memory mapped resource for TIME_CONTROL in their platreg.pi.xml file
7 Windows PCR:12286 Known Issue Debug.rtems-partition2
Debug.rtems-partition3
Debug.rtems-partition4
QEMU-ARM (qemu-arm)
QEMU-PPC (qemu-ppc)
QEMU-X86 (qemu-x86)
Media:rtems-partition3-debug-fail-arm.png qemu performance issues.
10 Windows DDCI_PCR:4197 Known Issue other.PerformanceTest QEMU-X86 (qemu-x86)
QEMU-PPC (qemu-ppc)
QEMU-ARM (qemu-arm)
The 'Toggle Command Display' button is missing from the DDC-I Debugger Console view after the test runs.
11 Windows
Linux
PCR:11440 Known Issue DeosOptionTabs.integrationToolTabTest All Targets WAT png file is not being generated. The -w option is ignored.
12 Windows
Linux
DDCI_PCR:4041 Known Issue DeosOptionTabs.integrationToolTabTest All Targets binder.xml files are not currently being validated in OpenArbor.
15 Windows DDCI_PCR:4200 Known Issue MulticoreIntegration DeosIMX8QM (imx8qm)
DeosLS1088ARDB-1 (ls10x8ardb)
DeosT2080RDB (t2080rdb)
Media:mulitcore-integration-imx8qm-failure.png
Media:ls10x8ardb-mulitcore-integration-settings.png
Media:t2080rdb-multicore-integration-settings.png
Trasher example does not display output even after the environment has been configured for multicore. The multi-threading example produces output and passes. Test sets up the memory pools incorrectly.
16 Windows PCR:13688 Known Issue Debug.CffsMal DeosImx8qm (imx8qm) After integrating the cffs-emmc-a mal, the expected output from the cffsthroughput example was not displayed on the video stream.
CP investigated and found error reported during init 'data error in status'
During manual testing, the integration of the mal failed and passed.

QA Report

QA Report