Changeset a0fa5dd for general/prog
- Timestamp:
- 05/21/2016 04:48:00 PM (8 years ago)
- Branches:
- systemd-13485
- Children:
- d017cd4
- Parents:
- 98c91f4c
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/mercurial.xml
r98c91f4c ra0fa5dd 7 7 <!ENTITY mercurial-download-http "https://www.mercurial-scm.org/release/mercurial-&mercurial-version;.tar.gz"> 8 8 <!ENTITY mercurial-download-ftp " "> 9 <!ENTITY mercurial-md5sum " 172a8c588adca12308c2aca16608d7f4">10 <!ENTITY mercurial-size "4. 5MB">9 <!ENTITY mercurial-md5sum "c38daa0cbe264fc621dc3bb05933b0b3"> 10 <!ENTITY mercurial-size "4.6 MB"> 11 11 <!ENTITY mercurial-buildsize "52 MB (385 MB with docs and tests)"> 12 12 <!ENTITY mercurial-time "less than 0.1 SBU (15 SBU with docs and tests)"> … … 99 99 <screen><userinput>make doc</userinput></screen> 100 100 101 <!-- All tests pass (or are skipped) at version 3.8.2 101 102 <para>Running the test suite is optional. Tests which fail may be disabled, 102 103 adding each one to <filename>tests/blacklists/failed-tests</filename>. In … … 109 110 test-gpg.t</literal> 110 111 EOF 111 112 rm -rf tests/tmp && 112 --> 113 <para> 114 To run the test suite, issue: 115 </para> 116 <screen><userinput>rm -rf tests/tmp && 113 117 114 118 TESTFLAGS="-j<replaceable><N></replaceable> --tmpdir tmp --blacklist blacklists/failed-tests" \ … … 116 120 117 121 <para>where <replaceable><N></replaceable> is an integer between one 118 and the number of ( processor X threads ), inclusive. In order to122 and the number of ( processor X threads ), inclusive. <!--In order to 119 123 investigate the apparently failing tests, you may use the 120 124 <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>. 122 126 Running the following commands, you will execute only the tests that failed 123 before:</para> 124 127 before:--></para> 128 129 <!-- 125 130 <screen><userinput>pushd tests && 126 131 rm -rf tmp && 127 132 128 ./run-tests.py - -tmpdir tmp test-gpg.t &&133 ./run-tests.py - -tmpdir tmp test-gpg.t && 129 134 popd</userinput></screen> 130 135 131 136 <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, which137 "- -debug" before "- -tmpdir", and run again, some failures are gone, which 133 138 seems to be a problem with the test suite. If this happens, normally, from 134 139 now on, there will be no more such failures whether you use the debug switch 135 140 or not.</para> 136 141 137 <para>An interesting switch is "- -time", which will generate at the end of142 <para>An interesting switch is "- -time", which will generate at the end of 138 143 the test suite execution, a table with all executed tests and respective 139 144 start, end, user, system and real times. Notice that the switches may be 140 145 used with <command>make check</command>, including them in the 141 146 <envar>TESTFLAGS</envar> environment variable.</para> 142 147 --> 143 148 <para>Install <application>Mercurial</application> by running the following 144 149 command (as <systemitem class="username">root</systemitem>):</para>
Note:
See TracChangeset
for help on using the changeset viewer.