| Server IP : 176.32.38.42 / Your IP : 216.73.216.67 Web Server : LiteSpeed System : Linux ha006.mymail.zone 4.18.0-553.51.1.lve.1.el8.x86_64 #1 SMP Wed May 14 14:34:57 UTC 2025 x86_64 User : s1225329 ( 1835) PHP Version : 7.4.33 Disable Function : exec,system,passthru,shell_exec,proc_close,proc_open,dl,popen,show_source,posix_kill,posix_mkfifo,posix_getpwuid,posix_setpgid,posix_setsid,posix_setuid,posix_setgid,posix_seteuid,posix_setegid,posix_uname MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : ON | Sudo : OFF | Pkexec : OFF Directory : /usr/share/cmake/Help/prop_test/ |
Upload File : |
RESOURCE_LOCK ------------- Specify a list of resources that are locked by this test. If multiple tests specify the same resource lock, they are guaranteed not to run concurrently. See also :prop_test:`FIXTURES_REQUIRED` if the resource requires any setup or cleanup steps. Both the :prop_test:`RESOURCE_GROUPS` and ``RESOURCE_LOCK`` properties serve similar purposes, but they are distinct and orthogonal. Resources specified by :prop_test:`RESOURCE_GROUPS` do not affect ``RESOURCE_LOCK``, and vice versa. Whereas ``RESOURCE_LOCK`` is a simpler property that is used for locking one global resource, :prop_test:`RESOURCE_GROUPS` is a more advanced property that allows multiple tests to simultaneously use multiple resources of the same type, specifying their requirements in a fine-grained manner.