Sorry, forgot to reply all...
> I'll take a look at it. I think the easiest thing may be to have the 
> files generated by the test suite during setup so that the add file 
> <x> lines in the manifest have a fixed place to look for the files. 
> Unless there's something important I'm missing about having things in 
> that particular directory. Unless there objections, I'll make the 
> changes and post a webrev here in a little bit.
>
> Brock
>
> Bart Smaalders wrote:
>> Shawn Walker wrote:
>>  
>>> I noticed that cli-complete.py doesn't run
>>> cli.t_actions.TestPkgActions even though it imports cli.t_actions.
>>>
>>> When I changed my local copy to do so, it failed complaining about
>>> "IOError: [Errno 2] No such file or directory: './testdata/passwd'"
>>>
>>> Anyone else familiar with this particular testsuite?
>>>
>>> Cheers,
>>>     
>>
>> This one needs to be run from the src/tests/cli directory...
>> I usually do so as:
>>
>> pfexec python t_actions.py
>>
>> : [EMAIL PROTECTED]; pfexec python t_actions.py
>> NOTE: Adding 
>> /home/barts/ws/pkg/proto/root_i386/usr/lib/python2.4/vendor-packages 
>> to PYTHONPATH
>> NOTE: Adding '/home/barts/ws/pkg/proto/root_i386/usr/bin' to head of 
>> PATH
>> ...
>> ----------------------------------------------------------------------
>> Ran 3 tests in 19.619s
>>
>> OK
>> : [EMAIL PROTECTED]; pwd
>> /home/barts/ws/pkg/src/tests/cli
>> : [EMAIL PROTECTED];
>>
>> Seems like we need a change or two to handle this case....
>>
>> - Bart
>>
>>
>>   
>
>



_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to