- Timestamp:
- 03/02/2024 09:00:56 AM (7 months ago)
- Branches:
- xry111/loongarch, xry111/loongarch-12.2
- Children:
- 746175a
- Parents:
- 1abe89b (diff), a56a4fc (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the(diff)
links above to see all the changes relative to each parent. - Location:
- chapter08
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter08/coreutils.xml
r1abe89b r0a18eb6 124 124 <screen><userinput remap="test">chown -R tester . </userinput></screen> 125 125 126 <para>Now run the tests:</para> 127 128 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check"</userinput></screen> 129 130 <!-- Sometimes skipped, but if not it may fail. 131 Please DO NOT remove or comment out this unless we can fully 132 understand it! 133 <para>The test-getlogin test may fail in the LFS chroot environment.</para> 134 20240226: Commented out as it seems the upstream has root-caused and 135 fixed the issue. I've checked the fix is in Coreutils 9.4 release 136 tarball: 137 138 https://lists.gnu.org/archive/html/bug-gnulib/2022-06/msg00079.html 139 --> 126 <!-- To editors: in jhalfs the standard input is always piped to "make" 127 so the test failures are not reproducible in jhalfs even if 128 running the build in a PTY. Don't use jhalfs to test if we can 129 remove < /dev/null. --> 130 <para>Now run the tests (using <filename>/dev/null</filename> for the 131 standard input, or two tests may be broken if building LFS in a 132 graphical terminal or a session in SSH or GNU Screen etc. because the 133 standard input is connected to a PTY from host distro, and the device 134 node for such a PTY cannot be accessed from the LFS chroot 135 environment):</para> 136 137 <screen><userinput remap="test">su tester -c "PATH=$PATH make RUN_EXPENSIVE_TESTS=yes check" < /dev/null</userinput></screen> 140 138 141 139 <para>Remove the temporary group:</para> -
chapter08/glibc.xml
r1abe89b r0a18eb6 172 172 parallel make jobs). These tests can be identified with:</para> 173 173 174 <!-- TODO: Using nodump for freeze. Change it to role="test" after 175 12.1 release so jhalfs can list these in the log. --> 176 <screen role="nodump"><userinput>grep "Timed out" -l $(find -name \*.out)</userinput></screen> 174 <screen><userinput remap="test">grep "Timed out" $(find -name \*.out)</userinput></screen> 177 175 178 176 <para>It's possible to re-run a single test with enlarged timeout -
chapter08/procps.xml
r1abe89b r0a18eb6 71 71 <screen revision='systemd'><userinput remap="make">make src_w_LDADD='$(LDADD) -lsystemd'</userinput></screen> 72 72 73 <para> To run the test suite, run:</para> 74 75 <screen><userinput remap="test">make -k check</userinput></screen> 73 <!-- To editors: "pmap {X,XX} with unreachable process" tests don't work 74 as root. They may seem to pass due to some Tcl/Expect/DejaGNU 75 internal hazards with some "luck" though. --> 76 <para>To run the test suite, run:</para> 77 78 <screen><userinput remap="test">chown -R tester . 79 su tester -c "PATH=$PATH make check"</userinput></screen> 76 80 77 81 <para>One test named 78 82 <literal>ps with output flag bsdtime,cputime,etime,etimes</literal> 79 83 is known to fail if the host kernel is not built with 80 <literal>CONFIG_BSD_PROCESS_ACCT</literal> enabled. 81 <!-- These two tests just do not work as root but they seem to pass 82 in most time due to some internal hazards of Tcl/Expect/DejaGNU 83 framework. However the failures have been really observed. 84 TODO: run the test suite as tester after the freeze ends. --> 85 Two tests named 86 <literal>pmap X with unreachable process</literal> and 87 <literal>pmap XX with unreachable process</literal> are known to 88 fail occasionally.</para> 84 <literal>CONFIG_BSD_PROCESS_ACCT</literal> enabled.</para> 89 85 90 86 <para>Install the package:</para>
Note:
See TracChangeset
for help on using the changeset viewer.