[developers] Trouble Seeing Test Suite Instances

[Joshua Crowgey]

Hey Alec,

I meant the '$' just to represent the prompt that you type at, not to
actually type the '$' in this case.  If `which tsdb' does nothing, then
there's no tsdb on your $PATH.  You might still have the tsdb file
though.  Try using find to see if it's somewhere in your delphin directory:

$ find /opt/delphin/ -name "tsdb"

(replace /opt/delphin/ with whatever your path to the delphin stuff is).

--Joshua

On 09/08/2014 05:00 PM, Alexander Sugar wrote:
> If I just type 'which tsdb' at the command line, I see nothing. If I
> type '$which tsdb', I get a
> 
> No command 'tsdb' found, did you mean:
>  Command 'tdb' from package 'tads2-dev' (multiverse)
> tsdb: command not found
> 
>  message.
> 
> On 9/8/14, Emily M. Bender <ebender at uw.edu> wrote:
>> The flags in that command suggest it belongs on the linux command line.  If
>> you do 'which tsdb' at the linux prompt, what do you see?
>>
>> Emily
>>
>> On Mon, Sep 8, 2014 at 4:35 PM, Alexander Sugar <sugara at uw.edu> wrote:
>>
>>> Mr. Oepen,
>>>
>>>       Please excuse my computer illiteracy. From where should I be
>>> introducing the
>>>
>>> tsdb -home <path> -verify
>>>
>>> command?
>>>
>>> Thank you,
>>> Alec
>>>
>>> On 9/8/14, Stephan Oepen <oe at ifi.uio.no> wrote:
>>>> colleagues,
>>>>
>>>>> The problem seems to be with [incr tsdb()]'s ability to "see" certain
>>>>> directories on the UbuntuLKB distro.
>>>>
>>>> i only have partial context here, but it sounds as if (a) there is a
>>>> valid skeleton, and (b) running ‘File|Create’ on it shows the
>>>> ‘creating empty data file’ messages as it should.
>>>>
>>>> the ‘no history file’ message should not be a problem.
>>>>
>>>> i would recommend inspecting the directory corresponding to the [incr
>>>> tsdb()] Database Root, where there should be a new sub-directory after
>>>> the ‘File|Create’ action.
>>>>
>>>> [incr tsdb()] will try validating that directory (i.e. the one
>>>> containing the ‘relations’ and ‘item’ files, together will all those
>>>> empty ones) using a command like the following:
>>>>
>>>>   tsdb -home <path> -verify
>>>>
>>>> here, <path> should correspond to the above sub-directory, and the
>>>> ‘-verify’ should either return with a zero exit(3) code (see ‘man
>>>> true’), or it should print diagnostic messages that i hope will help
>>>> resolve the problem.
>>>>
>>>> this all is relatively standard [incr tsdb()] territory that has been
>>>> unchanged for a decade or more.  thus, i am inclined to suspect that
>>>> some idiosyncrasy of the local setup is at the root of this problem.
>>>>
>>>> best, oe
>>>>
>>>
>>
>>
>>
>> --
>> Emily M. Bender
>> Associate Professor
>> Department of Linguistics
>> Check out CLMS on facebook! http://www.facebook.com/uwclma
>>
>