Lines Matching +full:docs +full:- +full:lld +full:- +full:html
28 commits from the llvm-zorg repository.
52 with the "config owner". We do expect "resource owners" - who are generally
53 the contact listed in a workers attributes - to proxy requests to the relevant
74 of parallelism (-j param) would give the fastest build. You can build
77 #. Install buildbot-worker (currently we are using buildbot version 2.8.4).
79 as ``pip3 install buildbot-worker==2.8.4``.
81 #. Create a designated user account, your buildbot-worker will be running under,
84 #. Choose the buildbot-worker root directory (all builds will be placed under
85 it), buildbot-worker access name and password the build master will be using
86 to authenticate your buildbot-worker.
88 #. Create a buildbot-worker in context of that buildbot-worker account. Point it
91 <http://docs.buildbot.net/current/tutorial/firstrun.html#creating-a-worker>`_
94 .. code-block:: bash
96 $ buildbot-worker create-worker <buildbot-worker-root-directory> \
98 <buildbot-worker-access-name> \
99 <buildbot-worker-access-password>
107 .. code-block:: bash
109 $ buildbot-worker start <buildbot-worker-root-directory>
115 ``<buildbot-worker-root-directory>/worker/twistd.log``. If your settings
120 #. Fill the buildbot-worker description and admin name/e-mail. Here is an
121 example of the buildbot-worker description::
126 g++.exe (TDM-1 mingw32) 4.4.0
129 Microsoft(R) 32-bit C/C++ Optimizing Compiler Version 16.00.40219.01 for 80x86
131 See `here <http://docs.buildbot.net/current/manual/installation/worker.html>`_
135 `zorg <https://github.com/llvm/llvm-zorg>`_. Use the typical LLVM
136 `workflow <https://llvm.org/docs/Contributing.html#how-to-submit-a-patch>`_.
158 #. Send the buildbot-worker access name and the access password directly to
163 #. Make sure you can start the buildbot-worker and successfully connect
164 to the silent buildmaster. Then set up your buildbot-worker to start
168 #. Check the status of your buildbot-worker on the `Waterfall Display (Staging)
203 * Within a checkout of `llvm-zorg <https://github.com/llvm/llvm-zorg>`_,
205 <https://docs.python.org/3/library/venv.html>`_ and install the necessary
208 .. code-block:: bash
210 python -m venv bbenv
212 pip install buildbot{,-console-view,-grid-view,-waterfall-view,-worker,-www}==3.11.7 urllib3
215 ``llvm-zorg`` and ask ``buildbot`` to check the configuration. This step can
218 .. code-block:: bash
220 buildbot create-master llvm-testbbmaster
221 cd llvm-testbbmaster
222 ln -s /path/to/checkout/of/llvm-zorg/buildbot/osuosl/master/master.cfg .
223 ln -s /path/to/checkout/of/llvm-zorg/buildbot/osuosl/master/config/ .
224 ln -s /path/to/checkout/of/llvm-zorg/zorg/ .
229 .. code-block:: bash
231 BUILDBOT_TEST=1 buildbot start --nodaemon .
242 .. code-block:: bash
244 buildbot-worker create-worker <buildbot-worker-root-directory> \
246 <buildbot-worker-name> \
248 buildbot-worker start --nodaemon <buildbot-worker-root-directory>
265 .. code-block:: bash
267 ssh -N -L 8011:localhost:8011 -L 9990:localhost:9990 username@buildmaster_server_address
287 complete ~10-15 builds an hour.
290 At 10-15 builds per hour, we need to complete a new build on average every
296 on the order of 5-8 workers. If your build config takes ~2 hours, you'll
297 need something on the order of 20-30 workers. The rest of this section
305 of the configuration. (e.g. For a multi-stage clang builder, you probably
311 compiler, and b) want to do a multi-stage clang build on your target, you
320 `-gmlt`), but in general the balance between debug info quality and build
323 Use Ninja & LLD
325 parallel builds. LLD helps to reduce both link times and memory usage
337 One of the non-obvious benefits of using ccache is that it makes the
345 well, and that having local per-worker caches gets most of the benefit
349 the cache with reasonable access times - i.e. a fast disk, or enough memory