headers
Spear, Raymond (Mission Critical Linux | 1 May 2012 17:29
Picon
Favicon

Re: multiple user documentation

A lot of the Web pages out there talk about doing things on the server using "atest".  I found a file in
/usr/local/autotest/cli called "atest.py" which I assume is this command.  However, that file is not executable.

I have no /usr/local/autotest/bin.

I haven't found anything on the WEB about this.  I setup my server using the contrib script contrib/install-autotest-server.sh.

What did I miss?

Thanks, ray spear
Permalink | Reply |
headers
Nishanth Aravamudan | 1 May 2012 22:24
Picon

Re: multiple user documentation

On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> A lot of the Web pages out there talk about doing things on the server
> using "atest".  I found a file in /usr/local/autotest/cli called
> "atest.py" which I assume is this command.  However, that file is not
> executable.
> 
> I have no /usr/local/autotest/bin.
> 
> I haven't found anything on the WEB about this.  I setup my server
> using the contrib script contrib/install-autotest-server.sh.
> 
> What did I miss?

I'm not positive, but maybe you're mixing up client and server directory
structures?

/usr/local/autotest/cli are the files used to build/support the CLI (as
opposed to the web interface).

/usr/local/autotest/bin I think only exists on clients running autotest
jobs.

I'm not sure what atest is, but I've not yet needed to look for it :)

-Nish

--

-- 
Nishanth Aravamudan <nacc <at> us.ibm.com>
IBM Linux Technology Center
(Continue reading)

Permalink | Reply |
headers
Spear, Raymond (Mission Critical Linux | 1 May 2012 22:55
Picon
Favicon

Re: multiple user documentation

the github autotest pages says:

*Autotest command line interface: Alternatively, users also can use the autotest CLI, written in python

we ran into issues and when we looked on the web the "fixes" all said to run atest with specific options.
there is no atest executable created when the contrib install script is used.

I tried to do "python /usr/local/autotest/cli/atest.py --help" but it did nothing

ray spear

-----Original Message-----
From: Nishanth Aravamudan [mailto:nacc <at> linux.vnet.ibm.com] 
Sent: Tuesday, May 01, 2012 1:25 PM
To: Spear, Raymond (Mission Critical Linux)
Cc: Autotest <at> test.kernel.org
Subject: Re: [Autotest] multiple user documentation

On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> A lot of the Web pages out there talk about doing things on the server 
> using "atest".  I found a file in /usr/local/autotest/cli called 
> "atest.py" which I assume is this command.  However, that file is not 
> executable.
> 
> I have no /usr/local/autotest/bin.
> 
> I haven't found anything on the WEB about this.  I setup my server 
> using the contrib script contrib/install-autotest-server.sh.
> 
> What did I miss?
(Continue reading)

Permalink | Reply |
headers
Nishanth Aravamudan | 1 May 2012 23:20
Picon

Re: multiple user documentation

On 01.05.2012 [20:55:38 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> the github autotest pages says:
> 
> *Autotest command line interface: Alternatively, users also can use the autotest CLI, written in python
> 
> we ran into issues and when we looked on the web the "fixes" all said to run atest with specific options.
> there is no atest executable created when the contrib install script is used.

Let's ignore the web (unless you mean the wiki :) -- what issues did you
hit with the CLI?

Thanks,
Nish

> 
> I tried to do "python /usr/local/autotest/cli/atest.py --help" but it did nothing
> 
> ray spear
> 
> -----Original Message-----
> From: Nishanth Aravamudan [mailto:nacc <at> linux.vnet.ibm.com] 
> Sent: Tuesday, May 01, 2012 1:25 PM
> To: Spear, Raymond (Mission Critical Linux)
> Cc: Autotest <at> test.kernel.org
> Subject: Re: [Autotest] multiple user documentation
> 
> On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> > A lot of the Web pages out there talk about doing things on the server 
> > using "atest".  I found a file in /usr/local/autotest/cli called 
> > "atest.py" which I assume is this command.  However, that file is not
(Continue reading)

Permalink | Reply |
headers
Lucas Meneghel Rodrigues | 2 May 2012 03:13
Picon
Favicon
Gravatar

Re: multiple user documentation

On Tue, 2012-05-01 at 13:24 -0700, Nishanth Aravamudan wrote:
> On 01.05.2012 [15:29:02 +0000], Spear, Raymond (Mission Critical Linux) wrote:
> > A lot of the Web pages out there talk about doing things on the server
> > using "atest".  I found a file in /usr/local/autotest/cli called
> > "atest.py" which I assume is this command.  However, that file is not
> > executable.
> > 
> > I have no /usr/local/autotest/bin.
> > 
> > I haven't found anything on the WEB about this.  I setup my server
> > using the contrib script contrib/install-autotest-server.sh.
> > 
> > What did I miss?
> 
> I'm not positive, but maybe you're mixing up client and server directory
> structures?
> 
> /usr/local/autotest/cli are the files used to build/support the CLI (as
> opposed to the web interface).
> 
> /usr/local/autotest/bin I think only exists on clients running autotest
> jobs.
> 
> I'm not sure what atest is, but I've not yet needed to look for it :)

It's the old name of what it's called today 'autotest-rpc-client'.

> -Nish
>
(Continue reading)

Permalink | Reply |
headers
Lucas Meneghel Rodrigues | 2 May 2012 03:12
Picon
Favicon
Gravatar

Re: multiple user documentation

On Tue, 2012-05-01 at 15:29 +0000, Spear, Raymond (Mission Critical
Linux) wrote:
> A lot of the Web pages out there talk about doing things on the server using "atest".  I found a file in
/usr/local/autotest/cli called "atest.py" which I assume is this command.  However, that file is not executable.
> 
> I have no /usr/local/autotest/bin.
> 
> I haven't found anything on the WEB about this.  I setup my server using the contrib script contrib/install-autotest-server.sh.
> 
> What did I miss?

I was on holiday today, getting back to read email, just saw your
inquiry.

Actually, I missed updating the docs. atest was renamed to
autotest-rpc-client, and atest.py became just a library that contains
the application core functionality. The reason why a longer name was
chosen was discoverability on a system wide install.

I've just pushed an update to the wiki that replaces all uses of atest
with autotest-rpc-client.

Cheers,

Lucas
Permalink | Reply |

Gmane