Changeset d401fde for general/prog
- Timestamp:
- 08/19/2023 02:22:47 AM (9 months ago)
- Branches:
- 12.0, 12.1, ken/TL2024, ken/tuningfonts, lazarus, plabs/newcss, python3.11, rahul/power-profiles-daemon, renodr/vulkan-addition, trunk, xry111/llvm18
- Children:
- 6156212c
- Parents:
- 32bcdbf0
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
r32bcdbf0 rd401fde 355 355 python3 ./x.py test --verbose --no-fail-fast | tee rustc-testlog</userinput></screen> 356 356 357 <!-- https://github.com/rust-lang/rust/issues/112209 --> 358 <para> 359 Two <literal>ui</literal> tests may fail (depending on the length 360 of absolute path of the 357 <!-- https://github.com/rust-lang/rust/issues/112209 358 I only saw 2 failures with 1.71.1, but Rainer saw 6 ones. 359 I don't want to find out the maximum number (by building rustc 360 in somewhere like /a/very/long/long/long/.../long/path) so I'd 361 just omit the exact number of failures here. --> 362 <para> 363 Some <literal>ui</literal> tests may fail (the number of failures 364 depends on the length of the absolute path to the 361 365 <filename class='directory'>rustc-&rust-version;-src</filename> 362 directory). 366 directory). These failures can be identified by viewing the 367 <filename>rustc-testlog</filename> file and search for the 368 <computeroutput>note: the full type name has been written 369 to</computeroutput>... messages and they can be safely ignored. 363 370 </para> 364 371
Note:
See TracChangeset
for help on using the changeset viewer.