madhuneal / ppss

Automatically exported from code.google.com/p/ppss
0 stars 0 forks source link

Intermittent ppss.sh failures #20

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
[psarkar@teentaal ppssTrial]$ cat largeLoop.sh 
#!/bin/bash

N=0
PN=$BASHPID
while (( $N < 1000 )); do
   N=$(( $N + 1 ));
   echo ${PN}_${N};
   sleep 1;
done

[psarkar@teentaal ppssTrial]$ head -5 joblistNumbered.txt 
/tmp/ppssTrial/largeLoop.sh 1
/tmp/ppssTrial/largeLoop.sh 2
/tmp/ppssTrial/largeLoop.sh 3
/tmp/ppssTrial/largeLoop.sh 4
/tmp/ppssTrial/largeLoop.sh 5
[psarkar@teentaal ppssTrial]$ wc -l joblistNumbered.txt 
170 joblistNumbered.txt
[psarkar@teentaal ppssTrial]$ 
What is the expected output? What do you see instead?

[psarkar@teentaal ppssTrial]$ ppss.sh -f joblistNumbered.txt -c 'sh '
Dec 09 10:11:40:  =========================================================
Dec 09 10:11:40:                         |P|P|S|S|                         
Dec 09 10:11:40:  Distributed Parallel Processing Shell Script version 2.41
Dec 09 10:11:40:  =========================================================
Dec 09 10:11:40:  Hostname:     teentaal
Dec 09 10:11:40:  ---------------------------------------------------------
Dec 09 10:11:40:  CPU: Intel(R) Xeon(TM) CPU 3.20GHz
Dec 09 10:11:40:  Found 8 logic processors.
Dec 09 10:11:40:  Starting 8 parallel workers.
Dec 09 10:11:40:  ---------------------------------------------------------
/tilde/psarkar/UTILS/bin/ppss.sh: line 1514: 100 *  / 170 : syntax error:
operand expected (error token is "/ 170 ")

^^^^^^ I have seen this failure a few times, but it happens intermittently
I have not figured out how to reproduce it.

What version of the product are you using? On what operating system?

  ppss 2.4.1 on Fedora 11, Intel Xeon Quad w/hyperthreading.

Please provide any additional information below.

Original issue reported on code.google.com by sarkarpr...@gmail.com on 9 Dec 2009 at 6:26

GoogleCodeExporter commented 9 years ago
Thanx for the report, this should be fixed.

Original comment by Louwrentius on 13 Dec 2009 at 8:46

GoogleCodeExporter commented 9 years ago
It has been fixed in version 2.45 which will be released shortly.

Original comment by Louwrentius on 16 Dec 2009 at 12:36