Changeset 4cc77fbd
- Timestamp:
- 01/27/2019 01:49:29 AM (5 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 8.4, 9.0, 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:
- d396c65
- Parents:
- b05ea0b
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
general/prog/rust.xml
rb05ea0b r4cc77fbd 290 290 which need Thumb (ARM) compilers will fail, all in <filename 291 291 class="directory">ui/issues</filename> for issues 37131, 49851 and 50993. 292 Occasionally a fourth test, in run-make, 'sysroot-crates-are-unstable',293 has been known to fail. That is probably harmless. As with all large294 testsuites, other tests might fail on some machines - if the number of295 fail ures is in the single digits, check the log for 'FAILED' and review296 lines above that. Any mention of SIGSEGV or signal 11 in a failing test297 is a cause for concern.292 Occasionally a fourth test, 'run-make-fulldeps/sysroot-crates-are-unstable' 293 fails. If gdb has been installed, in some circumstances three tests in 294 debuginfo-both also fail. As with all large testsuites, other tests might 295 fail on some machines - if the number of failures is in the single digits, 296 check the log for 'FAILED' and review lines above that. Any mention of 297 SIGSEGV or signal 11 in a failing test is a cause for concern. 298 298 </para> 299 299 -
introduction/welcome/changelog.xml
rb05ea0b r4cc77fbd 45 45 <para>January 24th, 2019</para> 46 46 <itemizedlist> 47 <listitem> 48 <para>[ken] - Tweak the details of which rust tests might fail.</para> 49 </listitem> 47 50 <listitem> 48 51 <para>[bdubbs] - Update the rust page providing instructions
Note:
See TracChangeset
for help on using the changeset viewer.