Changeset 5c01736c for general/prog


Ignore:
Timestamp:
09/19/2023 05:39:33 PM (8 months ago)
Author:
Xi Ruoyao <xry111@…>
Branches:
12.1, ken/TL2024, ken/tuningfonts, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18
Children:
7bfadab
Parents:
d6b169d
git-author:
Xi Ruoyao <xry111@…> (09/19/2023 05:35:54 PM)
git-committer:
Xi Ruoyao <xry111@…> (09/19/2023 05:39:33 PM)
Message:

llvm: Align test instruction with build-in-cgroup

File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/prog/llvm.xml

    rd6b169d r5c01736c  
    349349      significantly slow down the testing.  To test the results with core
    350350      dump disabled, <phrase revision='systemd'>ensure
    351       <xref linkend='systemd'/> is rebuilt with
    352       <xref linkend='linux-pam'/> support and the current login session is
    353       started after updating the
     351      <xref linkend='systemd'/> and <xref linkend='shadow'/> have
     352      been rebuilt with <xref linkend='linux-pam'/> support (if you are
     353      interacting via a SSH or graphical session, also ensure the
     354      <xref linkend='openssh'/> server or the desktop manager has been
     355      built with <xref linkend='linux-pam'/>) and the current login session
     356      is started after updating the
    354357      <filename>/etc/pam.d/system-session</filename> file to include
    355358      <filename class='libraryfile'>pam_systemd.so</filename>,
     
    377380
    378381    <para>
    379       <!-- EDITORS - if you have more than 4 cores, take some offline to measure
     382      <!-- EDITORS - if you have more than 4 cores, use a cgroup to measure
    380383      the elapsed time for the tests.  Also, libstdc++.a and perhaps libstdc++fs.a
    381384      are used by a couple of the link-static tests. -->
    382       Tests are
    383       built with all <emphasis>available</emphasis> cores, but run using the number
    384       of <emphasis>online</emphasis> processors. (The difference is that available
    385       cores can be limited using <command>taskset</command>, but taking them offline
    386       requires echoing 0 to <filename
    387       class="directory">/sys/devices/system/cpu/cpu&lt;N&gt;/online</filename>
    388       by the <systemitem class="username">root</systemitem> user and makes them
    389       temporarily unusable by all jobs on the machine.)  One test named
    390       <filename>Linux/clone_setns.cpp</filename> will fail if
    391       <option>CONFIG_USER_NS</option> is not enabled in kernel
     385      If <option>-jN</option> (N replaced with a number) is passed to
     386      <command>ninja</command>, the tests will be built with N logical
     387      cores, but run using all available logical cores.
     388      Run the test command in a cgroup (<phrase revision='systemd'>pass
     389        the <option>-p AllowedCPUs=...</option> option to the
     390        <command>systemd-run</command> command,
     391      </phrase>
     392      read <xref linkend='build-in-cgroup'/> for details) to limit the
     393      number of logical cores for running the tests.
     394      One test named <filename>Linux/clone_setns.cpp</filename> will fail
     395      if <option>CONFIG_USER_NS</option> is not enabled in kernel
    392396      configuration.
    393397      <!-- 17.0.1: 69321 Passed, 25066 Unsupported, 337 Skipped,
Note: See TracChangeset for help on using the changeset viewer.