- Timestamp:
- 06/14/2024 10:48:38 AM (4 months ago)
- Branches:
- 12.2, gimp3, lazarus, trunk, xry111/for-12.3, xry111/spidermonkey128
- Children:
- d09f8bcc
- Parents:
- 68df8455
- git-author:
- Xi Ruoyao <xry111@…> (06/14/2024 06:15:35 AM)
- git-committer:
- Xi Ruoyao <xry111@…> (06/14/2024 10:48:38 AM)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
r68df8455 rebffd4b 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 " ce1c084daec811aac07951cc954e7809">10 <!ENTITY rust-size "15 2MB">9 <!ENTITY rust-md5sum "1a00ff85d5fdb48ddbe534dcf1f6183f"> 10 <!ENTITY rust-size "155 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)"> … … 239 239 # and updated it to follow the major changes of the building system, 240 240 # so x.py will not warn us to do such a review. 241 change-id = 12 1754241 change-id = 123711 242 242 243 243 [llvm] … … 351 351 https://github.com/rust-lang/rust/pull/115869, see my comment 352 352 353 regression-bad-location-list-67992.rs: rust bug or gdb bug ???? --> 353 regression-bad-location-list-67992.rs: rust bug or gdb bug ???? 354 355 2024-06-14: Test result is clean with 1.79.0 354 356 <para> 355 357 Three tests, <filename>tests/ui/error-emitter/highlighting.rs</filename>, … … 357 359 <filename>tests/debuginfo/regression-bad-location-list-67992.rs</filename>, 358 360 are known to fail. 359 </para> 361 </para> --> 362 360 363 <!-- Let's just comment this out. Nobody has tested on a system w/o 361 364 FileCheck for a long time. … … 367 370 --> 368 371 <para> 369 As with all large test suites, othertests might fail on some machines -372 As with all large test suites, some tests might fail on some machines - 370 373 if the number of additional failures is low, 371 374 check the log for 'failures:' and review lines above that, particularly the … … 386 389 <para> 387 390 Therefore, you should determine the number of failures. 388 </para>389 390 <para>391 391 The number of tests which passed and failed can be found by running: 392 392 </para>
Note:
See TracChangeset
for help on using the changeset viewer.