Changeset aa36625

Timestamp:

03/13/2022 02:14:38 PM (2 years ago)

Author:

Pierre Labastie <pierre.labastie@…>

Branches:

11.2, 11.3, 12.0, 12.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, xry111/llvm18, xry111/soup3, xry111/xf86-video-removal

Children:

cac5f30

Parents:

674cb17

Message:

tracker-miners: move libseccomp to recommended

Also add some nitpick about timeouts in tests.

File:

• gnome/platform/tracker3-miners.xml (modified) (4 diffs)

gnome/platform/tracker3-miners.xml

@@ -87 +87 @@
       <xref linkend="libexif"/>,
       <xref linkend="libgrss"/>,
-      <xref linkend="libgxps"/>, and
+      <xref linkend="libgxps"/>,
+      <xref linkend="libseccomp"/>, and
       <xref linkend="poppler"/>
     </para>
@@ -97 +98 @@
       <xref linkend="dconf"/>,
       <xref linkend="libgsf"/>,
-      <xref linkend="libseccomp"/>,
       <xref linkend="taglib"/>,
       <xref linkend="totem-pl-parser"/>,
@@ -127 +127 @@
 -->
 
-    <para>
-      If you plan to run the tests, you may want to increase the global timeout
-      for them. The default value, 120 s, is not adapted to spinning disks
-      (replace 200 with a value suitable for your machine):
-    </para>
+    <note>
+      <para>
+        If you plan to run the tests, some timeouts are too short when
+        using spinning disks. There are two places where timeouts are
+        used: first, individual tests inside a group of tests have a
+        default timeout of 10s. This can be changed by setting the environment
+        variable <envar>TRACKER_TESTS_AWAIT_TIMEOUT</envar> to the desired
+        value when running the tests (see below). Second, a global timeout
+        for a group of tests is fixed at configuration time. The default value
+        in the <filename class="directory">functional-tests</filename>
+        directory (other directories have only short lived tests) may be
+        increased with the following command (replace 200 with a value
+        suitable for your machine):
+      </para>
 
 <screen remap="test"><userinput>sed -i s/120/<replaceable>200</replaceable>/ tests/functional-tests/meson.build</userinput></screen>
+    </note>
 
     <para>
@@ -158 +168 @@
     <para>
       To test the results, issue (adjust the individual test timeout to a
-      value suitable for your machine. The default value of 10s is too
-      short for spinning disks):
+      value suitable for your machine, see the note above):
     </para>