diff options
author | Michael Opdenacker <michael.opdenacker@bootlin.com> | 2023-12-06 16:39:45 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2023-12-18 13:18:55 +0000 |
commit | 3090312661ebf7d1b3481a580ed53aaab90022ab (patch) | |
tree | 37c831571d95570ae6a52fd2e0d7216bd7e7e0ef | |
parent | 84b242ef8bc103e49d83dcc25d968ab59524e1f3 (diff) | |
download | poky-3090312661ebf7d1b3481a580ed53aaab90022ab.tar.gz |
test-manual: resource updates
(From yocto-docs rev: 230523f2b834d3fdb2114956678e3003a486cebc)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r-- | documentation/test-manual/intro.rst | 20 |
1 files changed, 9 insertions, 11 deletions
diff --git a/documentation/test-manual/intro.rst b/documentation/test-manual/intro.rst index f27210642c..d14aa20f76 100644 --- a/documentation/test-manual/intro.rst +++ b/documentation/test-manual/intro.rst | |||
@@ -19,10 +19,8 @@ environment used by the Yocto Project to create their own automated, | |||
19 | production test environment, building upon the foundations from the | 19 | production test environment, building upon the foundations from the |
20 | project core. | 20 | project core. |
21 | 21 | ||
22 | Currently, the Yocto Project Test Environment Manual has no projected | 22 | This manual is a work-in-progress and is being initially loaded with |
23 | release date. This manual is a work-in-progress and is being initially | 23 | information from the README files and notes from key engineers: |
24 | loaded with information from the README files and notes from key | ||
25 | engineers: | ||
26 | 24 | ||
27 | - *yocto-autobuilder2:* This | 25 | - *yocto-autobuilder2:* This |
28 | :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>` | 26 | :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>` |
@@ -39,7 +37,7 @@ engineers: | |||
39 | As a result, it can be used by any Continuous Improvement (CI) system | 37 | As a result, it can be used by any Continuous Improvement (CI) system |
40 | to run builds, support getting the correct code revisions, configure | 38 | to run builds, support getting the correct code revisions, configure |
41 | builds and layers, run builds, and collect results. The code is | 39 | builds and layers, run builds, and collect results. The code is |
42 | independent of any CI system, which means the code can work `Buildbot <https://docs.buildbot.net/0.9.15.post1/>`__, | 40 | independent of any CI system, which means the code can work `Buildbot <https://docs.buildbot.net/current/>`__, |
43 | Jenkins, or others. This repository has a branch per release of the | 41 | Jenkins, or others. This repository has a branch per release of the |
44 | project defining the tests to run on a per release basis. | 42 | project defining the tests to run on a per release basis. |
45 | 43 | ||
@@ -54,8 +52,8 @@ the Autobuilder tests if things work. The Autobuilder builds all test | |||
54 | targets and runs all the tests. | 52 | targets and runs all the tests. |
55 | 53 | ||
56 | The Yocto Project uses now uses standard upstream | 54 | The Yocto Project uses now uses standard upstream |
57 | `Buildbot <https://docs.buildbot.net/0.9.15.post1/>`__ (version 9) to | 55 | Buildbot (`version 3.8 <https://docs.buildbot.net/3.8.0/>`__) to |
58 | drive its integration and testing. Buildbot Nine has a plug-in interface | 56 | drive its integration and testing. Buildbot has a plug-in interface |
59 | that the Yocto Project customizes using code from the | 57 | that the Yocto Project customizes using code from the |
60 | ``yocto-autobuilder2`` repository, adding its own console UI plugin. The | 58 | ``yocto-autobuilder2`` repository, adding its own console UI plugin. The |
61 | resulting UI plug-in allows you to visualize builds in a way suited to | 59 | resulting UI plug-in allows you to visualize builds in a way suited to |
@@ -304,11 +302,11 @@ Tests map into the codebase as follows: | |||
304 | Git repository. | 302 | Git repository. |
305 | 303 | ||
306 | Use the ``oe-build-perf-report`` command to generate text reports | 304 | Use the ``oe-build-perf-report`` command to generate text reports |
307 | and HTML reports with graphs of the performance data. For | 305 | and HTML reports with graphs of the performance data. See |
308 | examples, see | 306 | :yocto_dl:`html </releases/yocto/yocto-4.3/testresults/buildperf-debian11/perf-debian11_nanbield_20231019191258_15b576c410.html>` |
309 | :yocto_dl:`/releases/yocto/yocto-2.7/testresults/buildperf-centos7/perf-centos7.yoctoproject.org_warrior_20190414204758_0e39202.html` | ||
310 | and | 307 | and |
311 | :yocto_dl:`/releases/yocto/yocto-2.7/testresults/buildperf-centos7/perf-centos7.yoctoproject.org_warrior_20190414204758_0e39202.txt`. | 308 | :yocto_dl:`txt </releases/yocto/yocto-4.3/testresults/buildperf-debian11/perf-debian11_nanbield_20231019191258_15b576c410.txt>` |
309 | examples. | ||
312 | 310 | ||
313 | - The tests are contained in ``lib/oeqa/buildperf/test_basic.py``. | 311 | - The tests are contained in ``lib/oeqa/buildperf/test_basic.py``. |
314 | 312 | ||