diff options
Diffstat (limited to 'documentation/test-manual')
-rw-r--r-- | documentation/test-manual/test-manual-intro.rst | 4 | ||||
-rw-r--r-- | documentation/test-manual/test-manual-test-process.rst | 6 |
2 files changed, 5 insertions, 5 deletions
diff --git a/documentation/test-manual/test-manual-intro.rst b/documentation/test-manual/test-manual-intro.rst index cf511e9256..b41972084b 100644 --- a/documentation/test-manual/test-manual-intro.rst +++ b/documentation/test-manual/test-manual-intro.rst | |||
@@ -25,14 +25,14 @@ loaded with information from the README files and notes from key | |||
25 | engineers: | 25 | engineers: |
26 | 26 | ||
27 | - *yocto-autobuilder2:* This | 27 | - *yocto-autobuilder2:* This |
28 | :yocto_git:`README.md </cgit.cgi/yocto-autobuilder2/tree/README.md>` | 28 | :yocto_git:`README.md </yocto-autobuilder2/tree/README.md>` |
29 | is the main README which detials how to set up the Yocto Project | 29 | is the main README which detials how to set up the Yocto Project |
30 | Autobuilder. The ``yocto-autobuilder2`` repository represents the | 30 | Autobuilder. The ``yocto-autobuilder2`` repository represents the |
31 | Yocto Project's console UI plugin to Buildbot and the configuration | 31 | Yocto Project's console UI plugin to Buildbot and the configuration |
32 | necessary to configure Buildbot to perform the testing the project | 32 | necessary to configure Buildbot to perform the testing the project |
33 | requires. | 33 | requires. |
34 | 34 | ||
35 | - *yocto-autobuilder-helper:* This :yocto_git:`README </cgit.cgi/yocto-autobuilder-helper/tree/README/>` | 35 | - *yocto-autobuilder-helper:* This :yocto_git:`README </yocto-autobuilder-helper/tree/README/>` |
36 | and repository contains Yocto Project Autobuilder Helper scripts and | 36 | and repository contains Yocto Project Autobuilder Helper scripts and |
37 | configuration. The ``yocto-autobuilder-helper`` repository contains | 37 | configuration. The ``yocto-autobuilder-helper`` repository contains |
38 | the "glue" logic that defines which tests to run and how to run them. | 38 | the "glue" logic that defines which tests to run and how to run them. |
diff --git a/documentation/test-manual/test-manual-test-process.rst b/documentation/test-manual/test-manual-test-process.rst index bbf0103803..8a5e29d922 100644 --- a/documentation/test-manual/test-manual-test-process.rst +++ b/documentation/test-manual/test-manual-test-process.rst | |||
@@ -35,9 +35,9 @@ which the result was required. | |||
35 | The Autobuilder does build the ``master`` branch once daily for several | 35 | The Autobuilder does build the ``master`` branch once daily for several |
36 | reasons, in particular, to ensure the current ``master`` branch does | 36 | reasons, in particular, to ensure the current ``master`` branch does |
37 | build, but also to keep ``yocto-testresults`` | 37 | build, but also to keep ``yocto-testresults`` |
38 | (:yocto_git:`/cgit.cgi/yocto-testresults/`), | 38 | (:yocto_git:`/yocto-testresults/`), |
39 | buildhistory | 39 | buildhistory |
40 | (:yocto_git:`/cgit.cgi/poky-buildhistory/`), and | 40 | (:yocto_git:`/poky-buildhistory/`), and |
41 | our sstate up to date. On the weekend, there is a master-next build | 41 | our sstate up to date. On the weekend, there is a master-next build |
42 | instead to ensure the test results are updated for the less frequently | 42 | instead to ensure the test results are updated for the less frequently |
43 | run targets. | 43 | run targets. |
@@ -45,7 +45,7 @@ run targets. | |||
45 | Performance builds (buildperf-\* targets in the console) are triggered | 45 | Performance builds (buildperf-\* targets in the console) are triggered |
46 | separately every six hours and automatically push their results to the | 46 | separately every six hours and automatically push their results to the |
47 | buildstats repository at: | 47 | buildstats repository at: |
48 | :yocto_git:`/cgit.cgi/yocto-buildstats/`. | 48 | :yocto_git:`/yocto-buildstats/`. |
49 | 49 | ||
50 | The 'quick' targets have been selected to be the ones which catch the | 50 | The 'quick' targets have been selected to be the ones which catch the |
51 | most failures or give the most valuable data. We run 'fast' ptests in | 51 | most failures or give the most valuable data. We run 'fast' ptests in |