diff options
author | Andrew Geissler <geissonator@yahoo.com> | 2021-04-15 23:55:55 +0300 |
---|---|---|
committer | Brad Bishop <bradleyb@fuzziesquirrel.com> | 2021-04-19 16:32:18 +0300 |
commit | 3b8a17c1d70bac29dd3f1fb727716b7c2151b64a (patch) | |
tree | cc03ed84987f273db964a019f862b08a131d67fa /poky/documentation/test-manual | |
parent | e34f89623c246d261efb7fd0f2ce4a30b10bd59d (diff) | |
download | openbmc-3b8a17c1d70bac29dd3f1fb727716b7c2151b64a.tar.xz |
poky: subtree update:7d0988966c..1203d1f24d
Alexander Kanavin (5):
mesa: update 21.0.0 -> 21.0.1
runqemu: do not stop processing graphical options after nographic
mesa: gallium option requires libdrm
mesa: enable dri in native/nativesdk through gallium drivers
ptest-runner: correct version check
Alistair Francis (2):
conf/machine: Enable bochs-display on RISC-V machines
conf/machine: Enable keyboard and mouse on RISC-V machines
Anibal Limon (1):
ptest-runner: Upgrade to 2.4.1
Awais Belal (2):
perl: allow empty lines and comments in perl-rdepends.txt
perl: fix creation and generate new perl-rdepends.txt
Bruce Ashfield (1):
perf-tests: add bash into RDEPENDS (v5.12-rc5+)
Chen Qi (1):
apt: Fix do_compile error when enable ccache
Denys Dmytriyenko (1):
make-mod-scripts: pass CROSS_COMPILE to configure and build
Guillaume Champagne (1):
image-live.bbclass: optional depends when ROOTFS empty
Janne Kiiskila (1):
poky.yaml: Use git instead of git-core for Ubunti
Joshua Watt (1):
bitbake.conf: Limit the number of OpenMP threads
Khem Raj (3):
mesa-gl: Use swrast gallium driver
binutils: Fix a missing break in case statement
webkitgtk: Drop include_array.patch
Klaus Heinrich Kiwi (6):
uboot: Deploy default symlinks with fitImage
u-boot: Move definitions to common locations
u-boot: Add infrastructure to SPL verified boot
u-boot: Use a different Key for SPL signing
oe-selftest: Add U-Boot fitImage signing testcases
uboot: Fixes SPL verified boot on corner cases
Matt Madison (1):
libxcb: use PN for naming dynamic packages
Michael Halstead (1):
releases: update to include 3.2.3
Michael Opdenacker (7):
manuals: Spellcheck and capitalization fixes
SDK manual: fix reference to appendix
Quick build: checkout a branch instead of a fixed tag
manuals: Fix typos and spacing
overview-manual: style improvements
ref-manual: fix typo
manuals: fix suspicious newlines
Nicolas Dechesne (1):
docs: add a top level page for bitbake documentation
Paul Eggleton (16):
bitbake: bitbake-user-manual: document no support for using passwords in git URLs
bitbake: bitbake-user-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry
ref-manual: add METADATA_REVISION and METADATA_BRANCH
Use variables for minimum host versions and bump Python to 3.6
ref-manual: update/fix text for SDK_VERSION
overview-manual: fix git command line
ref-manual: and SDK_CUSTOM_TEMPLATECONF to glossary
ref-manual: add REQUIRED_VERSION and adjust PREFERRED_VERSION entry
ref-manual: add python3targetconfig class and remove python 2 references
ref-manual: add passwd-expire to EXTRA_USERS_PARAMS
ref-manual: add FIT_KERNEL_COMP_ALG*
ref-manual: fix reference to build-essential
ref-manual: tweak buildtools section
ref-manual: add migration section for 3.3 release
ref-manual: migration guide: add release codenames
ref-manual: add mention of DISTUTILS_SETUP_PATH
Quentin Schulz (1):
docs: replace anchor links
Richard Purdie (9):
oeqa/concurrencytest: Rename variables to improve the code
oeqa/concurrencytest: Fix display of test stdout/stderr
diffoscope: Upgrade 168 -> 172
oeqa/runqemu: Support RUNQEMU_TMPFS_DIR as a location to copy snapshot images to
bitbake: runqueue: Further fixes for confused setscene tasks
documentation/poky.yaml: Fix latest 3.2 series tag reference
poky.conf: Bump version for 3.3 hardknott release
build-appliance-image: Update to master head revision
bitbake: bitbake: Update version to 1.50.0 stable release series
Ross Burton (2):
poky.yaml: change gcc-multilib to gcc
oeqa/selftest: add test case for SRC_URI dependency sniffing
Ulrich Ölmann (1):
sdk-manual: fix typo
Yann Dirson (1):
kernel-yocto: fix do_kernel_configme indentation
Yi Fan Yu (2):
python3: Skip failing ptests due to load variability
valgrind: print failed ptest details
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: Id57d0682ec91b67b90fac931313457f5ed6f3d5c
Diffstat (limited to 'poky/documentation/test-manual')
-rw-r--r-- | poky/documentation/test-manual/intro.rst | 10 | ||||
-rw-r--r-- | poky/documentation/test-manual/test-process.rst | 6 | ||||
-rw-r--r-- | poky/documentation/test-manual/understand-autobuilder.rst | 16 |
3 files changed, 16 insertions, 16 deletions
diff --git a/poky/documentation/test-manual/intro.rst b/poky/documentation/test-manual/intro.rst index 81c24a8c3..101d28366 100644 --- a/poky/documentation/test-manual/intro.rst +++ b/poky/documentation/test-manual/intro.rst @@ -26,7 +26,7 @@ engineers: - *yocto-autobuilder2:* This :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>` - is the main README which detials how to set up the Yocto Project + is the main README which details how to set up the Yocto Project Autobuilder. The ``yocto-autobuilder2`` repository represents the Yocto Project's console UI plugin to Buildbot and the configuration necessary to configure Buildbot to perform the testing the project @@ -88,7 +88,7 @@ Yocto Project Tests - Types of Testing Overview =============================================== The Autobuilder tests different elements of the project by using -thefollowing types of tests: +the following types of tests: - *Build Testing:* Tests whether specific configurations build by varying :term:`MACHINE`, @@ -124,7 +124,7 @@ thefollowing types of tests: The tests utilize the ``testsdkext`` class and the ``do_testsdkext`` task. - *Feature Testing:* Various scenario-based tests are run through the - :ref:`OpenEmbedded Self test (oe-selftest) <ref-manual/release-process:Testing and Quality Assurance>`. We test oe-selftest on each of the main distrubutions + :ref:`OpenEmbedded Self test (oe-selftest) <ref-manual/release-process:Testing and Quality Assurance>`. We test oe-selftest on each of the main distributions we support. - *Image Testing:* Image tests initiated through the following command:: @@ -474,7 +474,7 @@ correctly. The test would only run if python3 is installed in the SDK. ---------------------- The performance tests usually measure how long operations take and the -resource utilisation as that happens. An example from +resource utilization as that happens. An example from ``meta/lib/oeqa/buildperf/test_basic.py`` contains the following:: class Test3(BuildPerfTestCase): @@ -524,5 +524,5 @@ This is particularly true for oe-selftests since these can run in parallel and changing metadata leads to changing checksums, which confuses BitBake while running in parallel. If this is necessary, copy layers to a temporary location and modify them. Some tests need to -change metadata, such as the devtool tests. To prevent the metadate from +change metadata, such as the devtool tests. To protect the metadata from changes, set up temporary copies of that data first. diff --git a/poky/documentation/test-manual/test-process.rst b/poky/documentation/test-manual/test-process.rst index 8a5e29d92..4c3b32bfe 100644 --- a/poky/documentation/test-manual/test-process.rst +++ b/poky/documentation/test-manual/test-process.rst @@ -59,13 +59,13 @@ Release Builds The project typically has two major releases a year with a six month cadence in April and October. Between these there would be a number of -milestone releases (usually four) with the final one being stablization +milestone releases (usually four) with the final one being stabilization only along with point releases of our stable branches. The build and release process for these project releases is similar to -that in `Day to Day Development <#test-daily-devel>`__, in that the +that in :ref:`test-manual/test-process:day to day development`, in that the a-full target of the Autobuilder is used but in addition the form is -configured to generate and publish artefacts and the milestone number, +configured to generate and publish artifacts and the milestone number, version, release candidate number and other information is entered. The box to "generate an email to QA"is also checked. diff --git a/poky/documentation/test-manual/understand-autobuilder.rst b/poky/documentation/test-manual/understand-autobuilder.rst index 199cc97a8..c158d9ce4 100644 --- a/poky/documentation/test-manual/understand-autobuilder.rst +++ b/poky/documentation/test-manual/understand-autobuilder.rst @@ -9,14 +9,14 @@ Execution Flow within the Autobuilder The "a-full" and "a-quick" targets are the usual entry points into the Autobuilder and it makes sense to follow the process through the system -starting there. This is best visualised from the Autobuilder Console +starting there. This is best visualized from the Autobuilder Console view (:yocto_ab:`/typhoon/#/console`). Each item along the top of that view represents some "target build" and these targets are all run in parallel. The 'full' build will trigger the majority of them, the "quick" build will trigger some subset of them. The Autobuilder effectively runs whichever configuration is defined for -each of those targets on a seperate buildbot worker. To understand the +each of those targets on a separate buildbot worker. To understand the configuration, you need to look at the entry on ``config.json`` file within the ``yocto-autobuilder-helper`` repository. The targets are defined in the ‘overrides' section, a quick example could be qemux86-64 @@ -64,10 +64,10 @@ While not every detail of this is covered here, you can see how the template mechanism allows quite complex configurations to be built up yet allows duplication and repetition to be kept to a minimum. -The different build targets are designed to allow for parallelisation, +The different build targets are designed to allow for parallelization, so different machines are usually built in parallel, operations using the same machine and metadata are built sequentially, with the aim of -trying to optimise build efficiency as much as possible. +trying to optimize build efficiency as much as possible. The ``config.json`` file is processed by the scripts in the Helper repository in the ``scripts`` directory. The following section details @@ -111,7 +111,7 @@ roughly consist of: :ref:`test-manual/understand-autobuilder:Autobuilder Clone Cache`. This step has two possible modes of operation. If the build is part - of a parent build, its possible that all the repositories needed may + of a parent build, it's possible that all the repositories needed may already be available, ready in a pre-prepared directory. An "a-quick" or "a-full" build would prepare this before starting the other sub-target builds. This is done for two reasons: @@ -130,7 +130,7 @@ roughly consist of: #. *Call scripts/run-config* - This is another call into the Helper scripts where its expected that + This is another call into the Helper scripts where it's expected that the main functionality of this target will be executed. Autobuilder Technology @@ -164,7 +164,7 @@ Autobuilder Worker Janitor This is a process running on each Worker that performs two basic operations, including background file deletion at IO idle (see :ref:`test-manual/understand-autobuilder:Autobuilder Target Execution Overview`: Run clobberdir) and -maintainenance of a cache of cloned repositories to improve the speed +maintenance of a cache of cloned repositories to improve the speed the system can checkout repositories. Shared DL_DIR @@ -250,7 +250,7 @@ Deploying Yocto Autobuilder =========================== The most up to date information about how to setup and deploy your own -Autbuilder can be found in README.md in the ``yocto-autobuilder2`` +Autobuilder can be found in README.md in the ``yocto-autobuilder2`` repository. We hope that people can use the ``yocto-autobuilder2`` code directly but |