Ignore:
Timestamp:
05/21/2016 04:48:00 PM (8 years ago)
Author:
DJ Lucas <dj@…>
Branches:
systemd-13485
Children:
d017cd4
Parents:
98c91f4c
Message:

Update to trunk r17385.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/branches/systemd@17386 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • general/prog/mercurial.xml

    r98c91f4c ra0fa5dd  
    77  <!ENTITY mercurial-download-http "https://www.mercurial-scm.org/release/mercurial-&mercurial-version;.tar.gz">
    88  <!ENTITY mercurial-download-ftp  " ">
    9   <!ENTITY mercurial-md5sum        "172a8c588adca12308c2aca16608d7f4">
    10   <!ENTITY mercurial-size          "4.5 MB">
     9  <!ENTITY mercurial-md5sum        "c38daa0cbe264fc621dc3bb05933b0b3">
     10  <!ENTITY mercurial-size          "4.6 MB">
    1111  <!ENTITY mercurial-buildsize     "52 MB (385 MB with docs and tests)">
    1212  <!ENTITY mercurial-time          "less than 0.1 SBU (15 SBU with docs and tests)">
     
    9999<screen><userinput>make doc</userinput></screen>
    100100
     101<!-- All tests pass (or are skipped) at version 3.8.2
    101102    <para>Running the test suite is optional. Tests which fail may be disabled,
    102103    adding each one to <filename>tests/blacklists/failed-tests</filename>. In
     
    109110  test-gpg.t</literal>
    110111EOF
    111 
    112 rm -rf tests/tmp &amp;&amp;
     112-->
     113    <para>
     114      To run the test suite, issue:
     115    </para>
     116<screen><userinput>rm -rf tests/tmp &amp;&amp;
    113117
    114118TESTFLAGS="-j<replaceable>&lt;N&gt;</replaceable> --tmpdir tmp --blacklist blacklists/failed-tests" \
     
    116120
    117121    <para>where <replaceable>&lt;N&gt;</replaceable> is an integer between one
    118     and the number of ( processor X threads ), inclusive. In order to
     122    and the number of ( processor X threads ), inclusive. <!--In order to
    119123    investigate the apparently failing tests, you may use the
    120124    <command>run-tests.py</command> script. To see the almost forty switches,
    121     some of them very useful, issue <command>tests/run-tests.py --help</command>.
     125    some of them very useful, issue <command>tests/run-tests.py - -help</command>.
    122126    Running the following commands, you will execute only the tests that failed
    123     before:</para>
    124 
     127    before:--></para>
     128
     129<!--
    125130<screen><userinput>pushd tests  &amp;&amp;
    126131  rm -rf tmp &amp;&amp;
    127132
    128   ./run-tests.py --tmpdir tmp test-gpg.t &amp;&amp;
     133  ./run-tests.py - -tmpdir tmp test-gpg.t &amp;&amp;
    129134popd</userinput></screen>
    130135
    131136    <para>Normally, the previous failures will be confirmed. However, if you add    the switch
    132     "--debug" before "--tmpdir", and run again, some failures are gone, which
     137    "- -debug" before "- -tmpdir", and run again, some failures are gone, which
    133138    seems to be a problem with the test suite. If this happens, normally, from
    134139    now on, there will be no more such failures whether you use the debug switch
    135140    or not.</para>
    136141
    137     <para>An interesting switch is "--time", which will generate at the end of
     142    <para>An interesting switch is "- -time", which will generate at the end of
    138143    the test suite execution, a table with all executed tests and respective
    139144    start, end, user, system and real times. Notice that the switches may be
    140145    used with <command>make check</command>, including them in the
    141146    <envar>TESTFLAGS</envar> environment variable.</para>
    142 
     147-->
    143148    <para>Install <application>Mercurial</application> by running the following
    144149    command (as <systemitem class="username">root</systemitem>):</para>
Note: See TracChangeset for help on using the changeset viewer.