Changeset 37dfd42 for general/prog/mercurial.xml
- Timestamp:
- 10/06/2014 01:57:30 AM (10 years ago)
- Branches:
- kde5-14686, systemd-13485
- Children:
- f101b9f2
- Parents:
- 333e8400
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/mercurial.xml
r333e8400 r37dfd42 7 7 <!ENTITY mercurial-download-http "http://mercurial.selenic.com/release/mercurial-&mercurial-version;.tar.gz"> 8 8 <!ENTITY mercurial-download-ftp " "> 9 <!ENTITY mercurial-md5sum " 5a530bb472b3cb306b757c8f5df91358">10 <!ENTITY mercurial-size "3. 8MB">11 <!ENTITY mercurial-buildsize " 31MB (additional 250 MB for the tests and 2 MB for docs generation)">12 <!ENTITY mercurial-time "0.1 SBU (additional 8.8SBU for tests)">9 <!ENTITY mercurial-md5sum "72a79798de828d6d6fb055273f91201a"> 10 <!ENTITY mercurial-size "3.9 MB"> 11 <!ENTITY mercurial-buildsize "44 MB (additional 250 MB for the tests and 2 MB for docs generation)"> 12 <!ENTITY mercurial-time "0.1 SBU (additional 9 SBU for tests)"> 13 13 ]> 14 14 … … 113 113 make check</userinput></screen> 114 114 115 <para>Tests may be run in parallel, just add 116 <quote>-j$(getconf _NPROCESSORS_ONLN)</quote> to TESTFLAGS.</para> 115 <para>More failing tests might be added to that file, if necessary. Tests 116 may be run in parallel, just add <quote>-j$(getconf 117 _NPROCESSORS_ONLN)</quote> to TESTFLAGS. In order to investigate a 118 particular apparently failing test, e.g <quote>test-parse-date.t</quote>, 119 issue the following commands (notice that omitting <option>--debug</option> 120 sometimes modifies the result):</para> 121 122 <screen><userinput>pushd tests && 123 rm -rf tmp && 124 ./run-tests.py --debug --tmpdir tmp test-parse-date.t && 125 popd</userinput></screen> 117 126 118 127 <para>Install <application>Mercurial</application> by running
Note:
See TracChangeset
for help on using the changeset viewer.