Changeset 32a3136 for general/prog/rust.xml
- Timestamp:
- 05/05/2024 07:38:44 PM (5 months ago)
- Branches:
- 12.2, gimp3, lazarus, trunk, xry111/for-12.3, xry111/spidermonkey128
- Children:
- 99d85abd
- Parents:
- cbfd207
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
rcbfd207 r32a3136 7 7 <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.xz"> 8 8 <!ENTITY rust-download-ftp " "> 9 <!ENTITY rust-md5sum " 7df442945fb2e32cbccd45a7faa3a5e1">10 <!ENTITY rust-size "15 6MB">9 <!ENTITY rust-md5sum "ce1c084daec811aac07951cc954e7809"> 10 <!ENTITY rust-size "152 MB"> 11 11 <!ENTITY rust-buildsize "8.9 GB (298 MB installed); add 6.4 GB if running the tests"> 12 12 <!ENTITY rust-time "6.7 SBU (including download time; add 6.2 SBU for tests, both using parallelism=8)"> … … 264 264 # and updated it to follow the major changes of the building system, 265 265 # so x.py will not warn us to do such a review. 266 change-id = 1 02579266 change-id = 121754 267 267 268 268 [llvm] … … 368 368 python3 x.py test --verbose --no-fail-fast | tee rustc-testlog</userinput></screen> 369 369 370 <!-- https://github.com/rust-lang/rust/pull/115869 --> 371 <para> 372 Two tests, <filename>tests/ui/issues/issue-21763.rs</filename> and 370 <!-- highlighting.rs: 371 may be fixed by 372 https://github.com/rust-lang/rust/pull/124398 ? 373 it seems harmless anyway 374 375 issue-21763.rs: 376 https://github.com/rust-lang/rust/pull/115869, see my comment 377 378 regression-bad-location-list-67992.rs: rust bug or gdb bug ???? --> 379 <para> 380 Three tests, <filename>tests/ui/error-emitter/highlighting.rs</filename>, 381 <filename>tests/ui/issues/issue-21763.rs</filename>, and 373 382 <filename>tests/debuginfo/regression-bad-location-list-67992.rs</filename>, 374 383 are known to fail. 375 384 </para> 376 377 <!-- https://github.com/rust-lang/rust/pull/120529 --> 378 <para> 379 With LLVM-18, two <literal>[run-make]</literal> tests named 380 <filename>rustdoc-target-spec-json-path</filename> and 381 <filename>target-specs</filename> are known to fail. 382 </para> 383 385 <!-- Let's just comment this out. Nobody has tested on a system w/o 386 FileCheck for a long time. 384 387 <para> 385 388 If <command>FileCheck</command> from <application>LLVM</application> has … … 387 390 will fail. 388 391 </para> 389 392 --> 390 393 <para> 391 394 As with all large test suites, other tests might fail on some machines -
Note:
See TracChangeset
for help on using the changeset viewer.