Results 1 to 10 of 19

Thread: Missing Variables on three tests (PTS 4.8.3)

Hybrid View

  1. #1
    Join Date
    Oct 2013
    Posts
    14

    Default Missing Variables on three tests (PTS 4.8.3)

    Hi all,

    this is my first post at the forum and I checked it for my existing case. I did not find anything,so I post that Thread.
    I am testing PTS 4.8.3 with Rhel6U4. Following tests within the suite linux-system did not run because of missing variables:

    c-ray benchmark test
    tachyon benchmark test
    compress-pbzip2 benchmark test

    All of them expect a variable which is not set: $NUM_CPU_CORES

    So I 've set it manually into the dedicated binaries.
    socket=$(lscpu | grep Socket | cut -d ":" -f 2)
    core=$(lscpu | grep Core | cut -d ":" -f 2)
    NUM_CPU_CORES=`expr $core \* $socket`

    Regards

    Dirk Hartel

  2. #2

    Default

    Quote Originally Posted by harteld View Post
    Hi all,

    this is my first post at the forum and I checked it for my existing case. I did not find anything,so I post that Thread.
    I am testing PTS 4.8.3 with Rhel6U4. Following tests within the suite linux-system did not run because of missing variables:

    c-ray benchmark test
    tachyon benchmark test
    compress-pbzip2 benchmark test

    All of them expect a variable which is not set: $NUM_CPU_CORES

    So I 've set it manually into the dedicated binaries.
    socket=$(lscpu | grep Socket | cut -d ":" -f 2)
    core=$(lscpu | grep Core | cut -d ":" -f 2)
    NUM_CPU_CORES=`expr $core \* $socket`

    Regards

    Dirk Hartel
    NUM_CPU_CORES is always set by the Phoronix Test Suite automatically. Can you please run: phoronix-test-suite diagnostics and check for the "NUM_CPU_CORES" line value? The only thing I can think of is that maybe for your system there was trouble parsing that info. If you can let me know what the value is that would be great.

    Thanks,
    Michael

  3. #3
    Join Date
    Oct 2013
    Posts
    14

    Exclamation

    -bash-4.1$ phoronix-test-suite diagnostics | grep NUM
    NUM_CPU_CORES = 64
    NUM_CPU_JOBS = 128

    Interesting that the mentioned tests did not run up to the time if I set NUM_CPU_CORES manually....

    hmmmm
    Last edited by harteld; 10-10-2013 at 06:08 AM.

  4. #4

    Default

    Quote Originally Posted by harteld View Post
    -bash-4.1$ phoronix-test-suite diagnostics | grep NUM
    NUM_CPU_CORES = 64
    NUM_CPU_JOBS = 128

    Interesting that the mentioned tests did not run up to the time if I set NUM_CPU_CORES manually....

    hmmmm
    Is there anything else unique about your installation with its settings or anything along those lines? I can try on Scientific/CentOS 6.4 and see if I can reproduce but last time I tried (EL ~6.3) I didn't run into such issue and I don't believe with any platform I've ever run into NUM_CPU_CORES not being exposed right.

  5. #5
    Join Date
    Oct 2013
    Posts
    14

    Unhappy

    Same issue with pgbench, which did not get the variable $NUM_CPU_JOBS....

    Other issue, the necessary dirs were not copied:

    -bash-4.1$ cd /opt/phoronix/installed-tests/pts/pgbench-1.4.0/
    -bash-4.1$ ./pgbench
    server starting
    postgres cannot access the server configuration file "/var/home/unix/pg_/data/db/postgresql.conf": No such file or directory


    I think we have a problem with the standard configuration of some phoronix-4.8.3 tests and Rhel6.3/Rhel6.4
    Last edited by harteld; 10-28-2013 at 05:47 AM.

  6. #6

    Default

    Quote Originally Posted by harteld View Post
    Same issue with pgbench, which did not get the variable $NUM_CPU_JOBS....

    Other issue, the necessary dirs were not copied:

    -bash-4.1$ cd /opt/phoronix/installed-tests/pts/pgbench-1.4.0/
    -bash-4.1$ ./pgbench
    server starting
    postgres cannot access the server configuration file "/var/home/unix/pg_/data/db/postgresql.conf": No such file or directory


    I think we have a problem with the standard configuration of some phoronix-4.8.3 tests and Rhel6.3/Rhel6.4
    I've tried PTS on EL 6.4 and it's working fine for me without env var problems so it's likely something to do with your specific system configuration.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •