Changeset bf5fb94 for general/prog/rust.xml
- Timestamp:
- 10/26/2020 09:44:17 PM (3 years ago)
- Branches:
- 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, lazarus, lxqt, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 6fe9b0bd
- Parents:
- a2e21ee
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
ra2e21ee rbf5fb94 7 7 <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.gz"> 8 8 <!ENTITY rust-download-ftp " "> 9 <!ENTITY rust-md5sum " ff5731326898a7010403e1b148375de4">10 <!ENTITY rust-size "1 30MB">9 <!ENTITY rust-md5sum "a460bed79b92f6a7833ba6e6390ee6ae"> 10 <!ENTITY rust-size "145 MB"> 11 11 <!-- Gentle Reminder: buildsize is how much the user requires for the real 12 12 install, i.e. the source with its DESTDIR *plus* the DESTDIR. You … … 15 15 after the tests. --> 16 16 17 <!ENTITY rust-buildsize " 5.7 GB (250 MB installed) including 344 MB of ~/.cargo files for the user building this. Add 2.5GB if running the tests">18 <!ENTITY rust-time "3 3 SBU (add 17SBU for tests, both on a 4-core machine)">17 <!ENTITY rust-buildsize "7.6 GB (369 MB installed) including 294 MB of ~/.cargo files for the user building this. Add 3.3 GB if running the tests"> 18 <!ENTITY rust-time "39 SBU (add 31 SBU for tests, both on a 4-core machine)"> 19 19 ]> 20 20 … … 100 100 <para> 101 101 The current <application>rustbuild</application> build-system will use 102 all availableprocessors, although it does not scale well and often falls102 all processors, although it does not scale well and often falls 103 103 back to just using one core while waiting for a library to compile. 104 104 However it can be mostly limited to a specified number of processors by … … 108 108 environment variable <envar>CARGO_BUILD_JOBS=<N></envar>. At the 109 109 moment this is not effective when some of the rustc tests are run. 110 </para> 111 112 <para> 113 The current version of rust's num_cpus crate now recognizes that cgroups 114 can be used to restrict which processors it is allowed to use. So if your 115 machine lacks DRAM (typically, less than 2GB DRAM per core) that might be 116 an alternative to taking CPUs offline. 117 <phrase revision="sysv">In sysv systems cgroups requires <ulink 118 url="https://sourceforge.net/projects/libcg/">libcgroup</ulink>.</phrase> 119 <phrase revision="systemd">That can apparently be achievedd by writing 120 custom unit files.</phrase> 110 121 </para> 111 122 … … 205 216 <bridgehead renderas="sect4">Optional</bridgehead> 206 217 <para role="optional"> 207 <xref linkend="gdb"/> (used by the testsuite if it is present) and 208 <xref linkend="python2"/> (used by the testsuite) 218 <xref linkend="gdb"/> (used by the testsuite if it is present) 209 219 </para> 210 220 … … 293 303 294 304 <para> 305 Two of the tests reliably fail. To cause them to be ignored run the 306 following sed command: 307 </para> 308 309 <screen><userinput>sed -i '1i # ignore-test' \ 310 src/test/run-make-fulldeps/sysroot-crates-are-unstable/Makefile \ 311 src/test/run-make-fulldeps/long-linker-command-lines/Makefile</userinput></screen> 312 313 <para> 295 314 Compile <application>Rust</application> by running the following 296 315 commands: … … 318 337 319 338 <para> 320 The instructions above do not build ARM compilers, so the testsuite 321 <emphasis>will</emphasis> fail and the tests will be reported to end in 322 error, with a backtrace of the last failing test. On a good run, 3 tests 323 which need Thumb (ARM) compilers will fail, all in <filename 324 class="directory">ui/issues</filename> for issues 37131, 49851 and 50993. 325 A fourth test, 326 <filename>run-make-fulldeps/sysroot-crates-are-unstable</filename> 327 fails, presumably because we are using only stable features. 328 <!-- gdb appears to be fixed now 329 If gdb has been installed, in some circumstances tests in 330 <filename class="directory">debuginfo</filename> may fail.--> As with all 331 large testsuites, other tests might 339 Although no tests are now expected to fail, the testsuite reports that 340 1 commands did not execute successfully. As with all large testsuites, 341 some tests might 332 342 fail on some machines - if the number of failures is in the single digits, 333 343 check the log for 'FAILED' and review lines above that, particularly the … … 339 349 If you get any <emphasis>other</emphasis> failing test which reports an 340 350 issue number then you should search for that issue. For example, when 341 rustc >= 1.41.1 is built with a version of sysllvm before 10.0 the test351 rustc >= 1.41.1 was built with a version of sysllvm before 10.0 the test 342 352 for issue 69225 fails <ulink 343 353 url="https://github.com/rust-lang/rust/issues/69225"/> and that should be … … 347 357 348 358 <para> 349 Therefore, you should determine the number of failures. The total number 359 Therefore, you should determine the number of failures. 360 </para> 361 362 <!-- 363 The total number 350 364 of tests varies depending on which dependencies are present, e.g. more 351 365 will be run if <command>gdb</command> is available. If you wish, the … … 353 367 </para> 354 368 355 <screen remap="test"><userinput>egrep 'running [[:digit:]]+ test' rustc-testlog | awk '{ sum += $2 } END { print sum }'</userinput></screen> 356 357 <para> 358 More importantly, the totalof tests which failed can be found by running:369 <screen remap="test"><userinput>egrep 'running [[:digit:]]+ test' rustc-testlog | awk '{ sum += $2 } END { print sum }'</userinput></screen>--> 370 371 <para> 372 The number of tests which failed can be found by running: 359 373 </para> 360 374
Note:
See TracChangeset
for help on using the changeset viewer.