Changeset 403aae58

Timestamp:

08/03/2023 08:22:53 AM (9 months ago)

Author:

Xi Ruoyao <xry111@…>

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:

61f3e811

Parents:

e4c821e2

Message:

llvm: Run tests with core dump disabled, and note failures with Glibc-2.38

File:

• general/prog/llvm.xml (modified) (3 diffs)

general/prog/llvm.xml

@@ -337 +337 @@
 <screen remap="doc"><userinput>ninja docs-clang-html docs-clang-man</userinput></screen>
 
+    <!-- The excessive core dump made my system irresponsive.  -->
+    <para>
+      LLVM test suite can produce many core dump files.  They will occupy
+      a large amount of disk space, and the core dump process can
+      significantly slow down the testing.  To test the results with core
+      dump disabled, <phrase revision='systemd'>ensure
+      <xref linkend='systemd'/> is rebuilt with
+      <xref linkend='linux-pam'/> support and the current login session is
+      started after updating the
+      <filename>/etc/pam.d/system-session</filename> file to include
+      <filename class='libraryfile'>pam_systemd.so</filename>,
+      then </phrase>issue:
+    </para>
+
+    <screen remap="test" revision="sysv"><userinput>sh -c 'ulimit -c 0 &amp;&amp; ninja check-all'</userinput></screen>
+
+    <!-- From core(5): "RLIMIT_CORE will be ignored if the system is
+         configured to pipe core dumps to a program".  Here "the program"
+         is systemd-coredumpd.  So we need some fancy systemd setting.
+         -&ndash;user: Run it under per-user systemd manager, avoiding
+                       the necessity of root priviledge.
+         -&nash;pty: Run it in a pseudo-terminal, so we can monitor the
+                     process or interrupt it with Ctrl-C if we want.
+         -d: Run it with $PWD as the working directory.
+         -G: Delete the transient service unit even if the command fails,
+             to prevent "systemctl -&ndash;user status" from reporting
+             "degraded".
+         -p LimitCORE=0: Disable core dump.
+    -->
+    <screen remap="test" revision="systemd"><userinput>
+systemctl   --user start dbus &amp;&amp;
+systemd-run --user --pty -d -G -p LimitCORE=0 ninja check-all</userinput></screen>
+
     <para>
       <!-- EDITORS - if you have more than 4 cores, take some offline to measure
       the elapsed time for the tests.  Also, libstdc++.a and perhaps libstdc++fs.a
       are used by a couple of the link-static tests. -->
-      To test the results, issue: <command>ninja check-all</command>. Tests are
+      Tests are
       built with all <emphasis>available</emphasis> cores, but run using the number
       of <emphasis>online</emphasis> processors. (The difference is that available
@@ -352 +385 @@
       <option>CONFIG_USER_NS</option> is not enabled in kernel
       configuration.
+      <!-- TODO: make or find a report to upstream -->
+      The tests named <filename>AtoiAndFriendsOOBTest</filename>,
+      <filename>StrtolOOBTest</filename>,
+      <filename>StrtollOOBTest</filename>,
+      <filename>interception_malloc_test.cpp</filename>, and
+      <filename>scanf-allocate.cpp</filename> are known to fail with
+      Glibc-2.38.
       <!-- 16.0.3: 67327 Passed, 23510 Unsupported, 85 Skipped,
                    124 Expectedly Failed 
@@ -370 +410 @@
            124 Expectedly Failed, 1 Failed
            FAIL: ThreadSanitizer-x86_64 :: Linux/clone_setns.cpp - xry111
+
+           16.0.5 with Glibc-2.38:
+           63716 Passed, 23512 Unsupported, 85 Skipped,
+           124 Expectedly Failed, 15 Failed
+
+           - AtoiAndFriendsOOBTest, StrtolOOBTest, StrtollOOBTest
+             (repeated 4 times with different configurations)
+           - interception_malloc_test.cpp (repeated 2 times)
+           - scanf-allocate.cpp
       -->