@@ -223,37 +223,5 @@ and unpredictable, the issue should be reported on the bug tracker; even
223
223
better if it can be diagnosed and suppressed by fixing the test's
224
224
implementation, or by making its parameters - such as a timeout - more robust.
225
225
226
-
227
- Custom builders
228
- ===============
229
-
230
- .. highlight :: console
231
-
232
- When working on a platform-specific issue, you may want to test your changes on
233
- the buildbot fleet rather than just on GitHub Actions and Azure Pipelines. To do so, you can
234
- make use of the `custom builders
235
- <https://buildbot.python.org/all/#/builders?tags=%2Bcustom> `_.
236
- These builders track the ``buildbot-custom `` short-lived branch of the
237
- ``python/cpython `` repository, which is only accessible to core developers.
238
-
239
- To start a build on the custom builders, push the commit you want to test to
240
- the ``buildbot-custom `` branch::
241
-
242
- $ git push upstream <local_branch_name>:buildbot-custom
243
-
244
- You may run into conflicts if another developer is currently using the custom
245
- builders or forgot to delete the branch when they finished. In that case, make
246
- sure the other developer is finished and either delete the branch or force-push
247
- (add the ``-f `` option) over it.
248
-
249
- When you have gotten the results of your tests, delete the branch::
250
-
251
- $ git push upstream :buildbot-custom # or use the GitHub UI
252
-
253
- If you are interested in the results of a specific test file only, we
254
- recommend you change (temporarily, of course) the contents of the
255
- ``buildbottest `` clause in ``Makefile.pre.in ``; or, for Windows builders,
256
- the ``Tools/buildbot/test.bat `` script.
257
-
258
226
.. seealso ::
259
227
:ref: `buildworker `
0 commit comments