[Bioperl-pipeline] tests

[shawnh@worf.fugu-sg.org]

haha,
kiran and I digged deeper and it the error was quite funny.
bascially, what we are doing (something remnant from ensembl)
was to cat the NSFTMPDIR to a NSFTMPDIR/$num
basically some random number.
so if the number doesn't exist, it creates one.
problem was with the permissions of THAT dir.
eg. NSFTMPDIR/4

even if we create with all write permissions, that would 
be a problem if there are already directories that exist of that
number and we can't simply delete them.
so simply, just use NSFTMPDIR that people specify. Fair?
or does splitting into /tmp/1 /tmp/2 serve a purpose?



shawn

accessibleOn Thu, 15 Aug 2002, Elia Stupka wrote:

> I just noticed that the last two tests in Job.t is failing, don't want to
> step on your active work toes, so this is the message:
> 
> not ok 11
> # Test 11 got: '
> ------------- EXCEPTION  -------------
> MSG: Cannot pipe STDOUT to stdout_file.
> STACK Bio::Pipeline::Job::run
> /usr/users/elia/src/bioperl-pipeline//Bio/Pipeline/Job.pm:352
> STACK (eval) t/Job.t:56
> STACK toplevel t/Job.t:54
> 
> --------------------------------------
> ' (t/Job.t at line 60)
> #    Expected: ''
> not ok 12
> # Failed test 12 in t/Job.t at line 68
> 
> Elia
> 
> ********************************
> * http://www.fugu-sg.org/~elia *
> * tel:    +65 6874 1467        *
> * mobile: +65 9030 7613        *
> * fax:    +65 6777 0402        *
> ********************************
> 
> 
> _______________________________________________
> bioperl-pipeline mailing list
> bioperl-pipeline@bioperl.org
> http://bioperl.org/mailman/listinfo/bioperl-pipeline
> 

-- 
'Torture the data long enough and they will reveal anything'
********************************
* Shawn Hoon
* http://www.fugu-sg.org/~shawnh
********************************