18.09/TestReports/20180711/tiny-containers

From Apertis
< 18.09/TestReports‎ | 20180711
Revision as of 12:27, 16 July 2018 by Em (talk | contribs) (Created page with "{{#vardefine:PASSED|"#68FF68"}}{{#vardefine:PARTIAL|"#FFFF95"}}{{#vardefine:FAILED|"#FF8A75"}}{{#vardefine:NOT_TESTED|"#D1B7FF"}} {{#vardefine:CRITICAL|"#ffa4a4"}}{{#vardefine...")

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Testing results considerations:

  1. These tests use tiny container images.
  2. All automated test cases already integrated into LAVA system were executed on the following images: Arm, Arm64, AMD64.
  3. Failures and partial failures were filed as bugs in Phabricator for further investigation and analysis.

The platform image used for these tests are:

ID Description Type Arm Arm64 AMD64 Tested By Notes
LAVA sanity
check-tiny-system-containers Test privileged tiny container with shared network Integrated
check-tiny-user-containers Test non-privileged tiny container without networking Integrated
PASSED - All tests passed.
PARTIAL - Tests mostly passed, with some minor problems.
FAILED - One or more tests failed.
NOT TESTED - Test not run due to some issue, like WIP, Disabled, lacking proper hardware.
CRITICAL test case - release blocker
HIGH priority test case - must be tested every week
MEDIUM priority test case - must be tested at least every other week
LOW priority test case - test when possible