From e40058f3c50277b2502db99a2c3f604128931bca Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Tue, 15 Jul 2025 16:40:36 +0200 Subject: [PATCH 1/7] Add explanation to buildbots.rst about triggering buildbot on a PR --- testing/buildbots.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/testing/buildbots.rst b/testing/buildbots.rst index 97856f713..b595047e3 100644 --- a/testing/buildbots.rst +++ b/testing/buildbots.rst @@ -48,6 +48,26 @@ after each commit. In particular, reference leaks builds take several hours to complete so they are done periodically. This is why it's important for you to be able to check the results yourself, too. +Triggering a buildbot on a pull request +======================================= + +If you want a pull request tested against a given platform, you can trigger one +or more build bots by posting a comment that begins with: + +.. code-block:: none + + !buildbot regex-matching-target + + +For example to run both the iOS and Android build bot, you can use: + +.. code-block:: none + + !buildbot ios|android + +If this worked, bedevere-bot will post a comment indicating which build bots, if +any, were matched. If none were matched, it will tell you that too. + Checking results of automatic builds ==================================== From f01363f473892ec3ff567b5cb1f17f6a853aed9c Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Tue, 15 Jul 2025 16:45:19 +0200 Subject: [PATCH 2/7] Get rid of extra new line --- testing/buildbots.rst | 1 - 1 file changed, 1 deletion(-) diff --git a/testing/buildbots.rst b/testing/buildbots.rst index b595047e3..d98e94533 100644 --- a/testing/buildbots.rst +++ b/testing/buildbots.rst @@ -58,7 +58,6 @@ or more build bots by posting a comment that begins with: !buildbot regex-matching-target - For example to run both the iOS and Android build bot, you can use: .. code-block:: none From 096d17c881bf7932c90681bc7d05c8116ae54716 Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Tue, 15 Jul 2025 18:55:06 +0200 Subject: [PATCH 3/7] Update testing/buildbots.rst Co-authored-by: Stan Ulbrych <89152624+StanFromIreland@users.noreply.github.com> --- testing/buildbots.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/testing/buildbots.rst b/testing/buildbots.rst index d98e94533..148851346 100644 --- a/testing/buildbots.rst +++ b/testing/buildbots.rst @@ -64,8 +64,9 @@ For example to run both the iOS and Android build bot, you can use: !buildbot ios|android -If this worked, bedevere-bot will post a comment indicating which build bots, if -any, were matched. If none were matched, it will tell you that too. +bedevere-bot will post a comment indicating which build bots, if +any, were matched. If none were matched, or you do not have the +necessary permissions to trigger a request, it will tell you that too. Checking results of automatic builds ==================================== From efb5296fefebcefc4352c1772b5fd785138fec04 Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Wed, 23 Jul 2025 10:19:43 +0200 Subject: [PATCH 4/7] Mention labels, explain about retriggering --- testing/buildbots.rst | 23 +++++++++++++++++++---- triage/labels.rst | 5 +++-- 2 files changed, 22 insertions(+), 6 deletions(-) diff --git a/testing/buildbots.rst b/testing/buildbots.rst index 148851346..81302fd81 100644 --- a/testing/buildbots.rst +++ b/testing/buildbots.rst @@ -48,11 +48,22 @@ after each commit. In particular, reference leaks builds take several hours to complete so they are done periodically. This is why it's important for you to be able to check the results yourself, too. -Triggering a buildbot on a pull request -======================================= +Triggering buildbots on a pull request +====================================== -If you want a pull request tested against a given platform, you can trigger one -or more build bots by posting a comment that begins with: +To trigger buildbots on a pull request you need to be a CPython triager or a +core developer. If you are not, ask someone to trigger them on your behalf. + +The simplest way to trigger most buildbots on your PR is with the +:gh-label:`🔨 test-with-buildbots` and :gh-label:`🔨 test-with-refleak-buildbots` +labels. (See :ref:`github-pr-labels`.) + +These will run buildbots on the most recent commit. If you want to trigger the +buildbots again on a later commit, you'll have to remove the label and add it +again. + +If you want to test a pull request against specific platforms, you can trigger +one or more build bots by posting a comment that begins with: .. code-block:: none @@ -68,6 +79,10 @@ bedevere-bot will post a comment indicating which build bots, if any, were matched. If none were matched, or you do not have the necessary permissions to trigger a request, it will tell you that too. +The ``!buildbot`` comment will also only run buildbots on the most recent +commit. To trigger the buildbots again on a later commit, you will have to +repeat the comment. + Checking results of automatic builds ==================================== diff --git a/triage/labels.rst b/triage/labels.rst index d78f6b472..d7703dc7f 100644 --- a/triage/labels.rst +++ b/triage/labels.rst @@ -135,7 +135,6 @@ Other labels .. _GitHub Labels for PRs: .. _github-pr-labels: - Labels specific to PRs ====================== @@ -158,9 +157,11 @@ to trigger specific bot behaviors. * :gh-label:`skip news `: for PRs that don't need a NEWS entry. The :ref:`news-entry` section covers in details in which cases the NEWS entry can be skipped. -* :gh-label:`test-with-buildbots`: used to test the latest commit with +* :gh-label:`🔨 test-with-buildbots`: used to test the latest commit with the :ref:`buildbot fleet ` whenever more testing is required before merging. This may take multiple hours to complete. +* :gh-label:`🔨 test-with-refleak-buildbots`: Run the reference leak buildbots + on the latest commit. Useful for when the code might be leaky. * :samp:`awaiting {action}`: these labels are applied and used by `bedevere`_ to indicate the stage of a PR and should not be applied manually. From bcf103e6458bec1ca0afcc961b47a0a2dbc9b79b Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Wed, 23 Jul 2025 10:20:38 +0200 Subject: [PATCH 5/7] Fix --- triage/labels.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/triage/labels.rst b/triage/labels.rst index d7703dc7f..6b317ab17 100644 --- a/triage/labels.rst +++ b/triage/labels.rst @@ -135,6 +135,7 @@ Other labels .. _GitHub Labels for PRs: .. _github-pr-labels: + Labels specific to PRs ====================== From 74bef72c51b79ac9ffd80359c5e148e6500a63f6 Mon Sep 17 00:00:00 2001 From: Hood Chatham Date: Wed, 23 Jul 2025 10:21:39 +0200 Subject: [PATCH 6/7] Try again: --- triage/labels.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/triage/labels.rst b/triage/labels.rst index 6b317ab17..4dd895630 100644 --- a/triage/labels.rst +++ b/triage/labels.rst @@ -158,10 +158,10 @@ to trigger specific bot behaviors. * :gh-label:`skip news `: for PRs that don't need a NEWS entry. The :ref:`news-entry` section covers in details in which cases the NEWS entry can be skipped. -* :gh-label:`🔨 test-with-buildbots`: used to test the latest commit with +* :gh-label:`:hammer: test-with-buildbots`: used to test the latest commit with the :ref:`buildbot fleet ` whenever more testing is required before merging. This may take multiple hours to complete. -* :gh-label:`🔨 test-with-refleak-buildbots`: Run the reference leak buildbots +* :gh-label:`:hammer: test-with-refleak-buildbots`: Run the reference leak buildbots on the latest commit. Useful for when the code might be leaky. * :samp:`awaiting {action}`: these labels are applied and used by `bedevere`_ to indicate the stage of a PR and should not be applied manually. From f5558dd1cd406e86e4c8f349abe9a14f8c6fa16f Mon Sep 17 00:00:00 2001 From: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com> Date: Wed, 23 Jul 2025 12:08:52 +0300 Subject: [PATCH 7/7] core team member --- testing/buildbots.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/testing/buildbots.rst b/testing/buildbots.rst index 81302fd81..c25de5012 100644 --- a/testing/buildbots.rst +++ b/testing/buildbots.rst @@ -52,7 +52,7 @@ Triggering buildbots on a pull request ====================================== To trigger buildbots on a pull request you need to be a CPython triager or a -core developer. If you are not, ask someone to trigger them on your behalf. +core team member. If you are not, ask someone to trigger them on your behalf. The simplest way to trigger most buildbots on your PR is with the :gh-label:`🔨 test-with-buildbots` and :gh-label:`🔨 test-with-refleak-buildbots` pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy