public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>
Subject: [kirkstone][PATCH 11/18] test-manual: resource updates
Date: Mon, 18 Dec 2023 22:44:35 +0100	[thread overview]
Message-ID: <20231218214442.147385-12-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231218214442.147385-1-michael.opdenacker@bootlin.com>

From: Michael Opdenacker <michael.opdenacker@bootlin.com>

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
 documentation/test-manual/intro.rst | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

diff --git a/documentation/test-manual/intro.rst b/documentation/test-manual/intro.rst
index 3a3fc2270e..51934f4851 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,
 production test environment, building upon the foundations from the
 project core.
 
-Currently, the Yocto Project Test Environment Manual has no projected
-release date. This manual is a work-in-progress and is being initially
-loaded with information from the README files and notes from key
-engineers:
+This manual is a work-in-progress and is being initially loaded with
+information from the README files and notes from key engineers:
 
 -  *yocto-autobuilder2:* This
    :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>`
@@ -39,7 +37,7 @@ engineers:
    As a result, it can be used by any Continuous Improvement (CI) system
    to run builds, support getting the correct code revisions, configure
    builds and layers, run builds, and collect results. The code is
-   independent of any CI system, which means the code can work `Buildbot <https://docs.buildbot.net/0.9.15.post1/>`__,
+   independent of any CI system, which means the code can work `Buildbot <https://docs.buildbot.net/current/>`__,
    Jenkins, or others. This repository has a branch per release of the
    project defining the tests to run on a per release basis.
 
@@ -54,8 +52,8 @@ the Autobuilder tests if things work. The Autobuilder builds all test
 targets and runs all the tests.
 
 The Yocto Project uses now uses standard upstream
-`Buildbot <https://docs.buildbot.net/0.9.15.post1/>`__ (version 9) to
-drive its integration and testing. Buildbot Nine has a plug-in interface
+Buildbot (`version 3.8 <https://docs.buildbot.net/3.8.0/>`__) to
+drive its integration and testing. Buildbot has a plug-in interface
 that the Yocto Project customizes using code from the
 ``yocto-autobuilder2`` repository, adding its own console UI plugin. The
 resulting UI plug-in allows you to visualize builds in a way suited to
@@ -299,11 +297,11 @@ Tests map into the codebase as follows:
       Git repository.
 
       Use the ``oe-build-perf-report`` command to generate text reports
-      and HTML reports with graphs of the performance data. For
-      examples, see
-      :yocto_dl:`/releases/yocto/yocto-2.7/testresults/buildperf-centos7/perf-centos7.yoctoproject.org_warrior_20190414204758_0e39202.html`
+      and HTML reports with graphs of the performance data. See
+      :yocto_dl:`html </releases/yocto/yocto-4.3/testresults/buildperf-debian11/perf-debian11_nanbield_20231019191258_15b576c410.html>`
       and
-      :yocto_dl:`/releases/yocto/yocto-2.7/testresults/buildperf-centos7/perf-centos7.yoctoproject.org_warrior_20190414204758_0e39202.txt`.
+      :yocto_dl:`txt </releases/yocto/yocto-4.3/testresults/buildperf-debian11/perf-debian11_nanbield_20231019191258_15b576c410.txt>`
+      examples.
 
    -  The tests are contained in ``lib/oeqa/buildperf/test_basic.py``.
 
-- 
2.34.1



  parent reply	other threads:[~2023-12-18 21:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-18 21:44 [kirkstone][PATCH 00/18] Documentation backports michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 01/18] ref-manual: Fix reference to MIRRORS/PREMIRRORS defaults michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 02/18] manuals: fix URL michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 03/18] ref-manual: releases.svg: update nanbield release status michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 04/18] dev-manual: layers: update link to YP Compatible form michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 05/18] contributor-guide: add License-Update tag michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 06/18] contributor-guide: fix command option michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 07/18] docs: add CONVERSION_CMD definition michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 08/18] migration-guides: release 3.5 is actually 4.0 michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 09/18] dev-manual: Discourage the use of SRC_URI[md5sum] michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 10/18] test-manual: text and formatting fixes michael.opdenacker
2023-12-18 21:44 ` michael.opdenacker [this message]
2023-12-18 21:44 ` [kirkstone][PATCH 12/18] test-manual: add links to python unittest michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 13/18] test-manual: explicit or fix file paths michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 14/18] test-manual: add or improve hyperlinks michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 15/18] manuals: brief-yoctoprojectqs: align variable order with default local.conf michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 16/18] dev-manual: runtime-testing: fix test module name michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 17/18] migration-guides: add release notes for 4.0.15 michael.opdenacker
2023-12-18 21:44 ` [kirkstone][PATCH 18/18] test-manual: use working example michael.opdenacker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231218214442.147385-12-michael.opdenacker@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox