Re: [MTT users] mtt fails, error: identical key already exists

2014-01-03 Thread Ralph Castain
On Jan 3, 2014, at 8:15 AM, Muhammad Wahaj Sethi wrote: > Thanks for the quick reply. > > Right now I am making use of option no 1. > > As per my understanding, mtt runs tests only if new versions/updates are > available. Info about last run is stored in the scratch dir. No, it is stored in

Re: [MTT users] mtt fails, error: identical key already exists

2014-01-03 Thread Muhammad Wahaj Sethi
Thanks for the quick reply. Right now I am making use of option no 1. As per my understanding, mtt runs tests only if new versions/updates are available. Info about last run is stored in the scratch dir. By removing/changing workspace dir this info will be lost. And next mtt execution may sub

Re: [MTT users] mtt fails, error: identical key already exists

2014-01-03 Thread Ralph Castain
You have two options: 1. After each mtt execution, run a "cleanup" script that simply does "rm -rf " 2. give the mtt scratch location a different name for each execution. However, be careful as you will fill your disk this way - so perhaps run a cleanup script every N times that whacks the old

[MTT users] mtt fails, error: identical key already exists

2014-01-03 Thread Muhammad Wahaj Sethi
Hello! I am running mtt daily using a cron job. After every successful execution, next mtt execution fails with the following error message. *** ERROR: An identical key already exists in memory when MTT tried to read the file /lustre/ws1/ws/hpcmtt-mtt-0/mtt-scratch/sources/mpi_sources-ompi-