Changeset f7dd8651 for general/prog
- Timestamp:
- 10/13/2019 01:36:35 AM (5 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 9.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:
- 17d262ca
- Parents:
- d0461a6
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
rd0461a6 rf7dd8651 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 " f43af67a139ce21ff5f530bbd2f486aa">10 <!ENTITY rust-size "14 5MB">9 <!ENTITY rust-md5sum "e67432b37150f13e186ebfb67e5192fb"> 10 <!ENTITY rust-size "147 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 … … 14 14 to measure it. --> 15 15 16 <!ENTITY rust-buildsize "5. 6 GB (423 MB installed) including 407MB of ~/.cargo files for the user building this. Add 1.8GB if running the tests">17 <!ENTITY rust-time "24 SBU (add 1 5SBU for tests, both with 4 processors)">16 <!ENTITY rust-buildsize "5.3GB (375 MB installed) including 429MB of ~/.cargo files for the user building this. Add 1.7 GB if running the tests"> 17 <!ENTITY rust-time "24 SBU (add 13 SBU for tests, both with 4 processors)"> 18 18 ]> 19 19 … … 300 300 <filename>run-make-fulldeps/sysroot-crates-are-unstable</filename> 301 301 fails, presumably because we are using only stable features. 302 <!-- appears to be fixed now 302 303 If gdb has been installed, in some circumstances tests in 303 <filename class="directory">debuginfo</filename> may fail. As with all304 <filename class="directory">debuginfo</filename> may fail.--> As with all 304 305 large testsuites, other tests might 305 306 fail on some machines - if the number of failures is in the single digits, … … 307 308 'stderr:' lines. Any mention of 308 309 SIGSEGV or signal 11 in a failing test is a cause for concern. 310 A fifth test, run-make-fulldeps/linker-output-non-utf8, is known to fail. 309 311 </para> 310 312
Note:
See TracChangeset
for help on using the changeset viewer.