I have defined a test-suite "suite-definition.xml"
one test is hanging and i have to kill the process or it just runs forever...Code:<Execute> <Test>pts/cpu</Test> </Execute> <Execute> <Test>pts/disk</Test> </Execute> <Execute> <Test>pts/memory</Test> </Execute>
the test name is tscp-1.0.0
how do i exclude it in my "suite-definition.xml" file?
the problem is that "pts/tscp" is part of the "pts/cpu"
Code:./phoronix-test-suite info pts/cpu Phoronix Test Suite v4.0.1 CPU / Processor Suite Run Identifier: pts/cpu-1.2.0 Suite Version: 1.2.0 Maintainer: Michael Larabel Suite Type: Processor Unique Tests: 25 Suite Description: This test suite contains tests designed to test the system's CPU / processor. pts/cpu-1.2.0 * pts/padman * pts/etqw-demo * pts/graphics-magick * pts/john-the-ripper * pts/ttsiod-renderer * pts/compress-pbzip2 * pts/compress-7zip * pts/encode-mp3 * pts/encode-flac * pts/x264 * pts/ffmpeg * pts/openssl * pts/gcrypt * pts/himeno * pts/pgbench * pts/apache * pts/c-ray * pts/povray * pts/smallpt * pts/tachyon * pts/crafty * pts/tscp * pts/mafft * pts/npb * pts/stream
this feature is very good and saves time... just define
and cpu tests are running...Code:<Execute> <Test>pts/cpu</Test> </Execute>
because i have in my xml file "pts/cpu" i can not remove "pts/tscp"....
is there some workaround?
Last edited by Yaniv; 12-05-2012 at 11:05 AM.
You could set environment variable: SKIP_TESTS=tscp
It should work like that otherwise SKIP_TESTS=pts/tscp
will try that tomorrow and report back.
tested both variables. and confirmed they are exported...
both result in the following PTS error. and the tests did not run at all.
SolutionCode:[NOTICE] Undefined: run_object in pts_test_run_manager.php:1450 PHP Fatal error: Call to a member function get_identifier_base_name() on a non-object in /root/phoronix-test-suite/pts-core/objects/client/pts_test_run_manager.php on line 1450
remove the pts/tscp definition from this file...
in this file are all pts/cpu tests defined.Code:../test-suites/pts/cpu-1.2.0/suite-definition.xml
Thanks for the report about the error, it's been fixed in Git.