Re: Running StandaloneTalos test

On Feb 6, 9:17 am, alice nodelman <[email protected]> wrote:
> Hmmm, the contents of those directories needs to make it into the
> matching chrome/components directories of your firefox install.  I would
>   think that that means that the path in the config files isn't
> appropriate for your browser, but then it doesn't make sense that it is
> opening the browser at all.
>
> For now, why not try copying the contents of those directories into the
> appropriate locations in your firefox directory.  That will at least let
> you move forward.  I have some theory about relative paths not working
> quite right for you...
>
> alice.
>
> [email protected] wrote:
> > On Feb 5, 2:23 pm, [email protected] wrote:
> >> On Feb 5, 1:51 pm, alice nodelman <[email protected]> wrote:> If it is attempting to openhttp://tinderboxthatmeansthat the
> >>> pageloader (step 3 in First Steps) isn't in the right location.  The
> >>> chrome and components directories created by generate-tpcomponent.py
> >>> need to end up in the talos/page_load_test directory.
> >>> alice.
> >> The 3rd step (i.e running generate-tpcomponent.py) indeed created
> >> chrome and components directories underneath talos/page_load_test.
>
> >> So chrome and components are in the right place.
>
> >> talos/page_load_test/chrome/ has two files pageloader.jar and
> >> pageloader.manifest.
> >> talos/page_load_test/components has one file tp-cmdline.js
>
> >> I run the proxy server from talos: python standalone/proxyserver.py -p
> >> 9001
> >> The test is run from talos: python run_tests.py standalone/
> >> proxy_setup.config
>
> >> thanks again,
> >> - mouli
>
> > Just to clarify my own post, page_load_test has both chrome and
> > components subdirectories as created by Step 3.
>
> > But still, running the test fails and it is attempting to open up
> >http://tinderbox
>
> > - mouli

I will try your suggestion. Meanwhile, here is the exact sequence of
steps for any possible gotchas.

Exact sequence of steps:

1. Setup the prerequisites (I have python 2.5.1 on the system, just
got the pyyaml using the link)
2. Get talos: cvs -d:pserver:[email protected]:/cvsroot
co -d talos mozilla/testing/performance/talos
3. Install the new page loader:
3.1 cvs -d:pserver:[email protected]:/cvsroot co -d
scripts mozilla/tools/buildbot-configs/testing/talos/perfmaster/
scripts/generate-tpcomponent.py

I invoke cvs from a directory above talos. As a result of the cvs
command, a script directory is created which contains generate-
tpcomponent.py

3.2 Edit generate-tpcomponent.py to use '[email protected]'
instead of 'cvs.mozilla.org'
The checked out version has the following lines, I don't think I need
to change it and so I leave it as it is.
# where the pageloader will be checked out from
cvsroot = ":pserver:[email protected]:/cvsroot"

3.3 Run in talos/page_load_test directory with the command:
python ../../script generate-tpcomponent.py

Per StandaloneTalos instruction, the command to use is python generate-
tpcomponent.py for this step. In my case, note that the script
directory is two levels above page_load_test. I also tried this step
by creating a symlink to generate-tpcomonent.py in page_load_test
directory itself so that I can run the command as in the
StandaloneTalos instruction, but still the test would finally fail in
the same way.

When the script is executed, I see the following cvs messages.
Interestingly,there is no directory by name pageloader once the script
completes. Perhaps, the script cleans up after creating chrome and
components.

cvs checkout: Updating pageloader
U pageloader/Makefile.in
U pageloader/README
U pageloader/jar.mn
U pageloader/pageloader.js
U pageloader/pageloader.xul
U pageloader/quit.js
U pageloader/report.js
U pageloader/tp-cmdline.js


3.4 Directories chrome and components are created in talos/
page_load_test.

4. unzip standalone.zip in talos.

5. Set up local web page set using the proxy server method.

5.1 prereqs step
5.1.1 Copy of talos. I already have it as above [ I assume that I
don't need to make another copy the directory ]
5.1.2 Copy of the standalone directory. This is already set up aboe
[ I assume that I don't need to make another copy of the dir]
5.1.3 Copy of the proxyserver.
cvs -d:pserver:[email protected]:/cvsroot co -d
proxyserver mozilla/testing/tools/proxyserver
Copy proxyserver/proxyserver.py into the standalone directory

5.2.1 from talos directory, set up the proxy server using python
standalone/proxyserver.py -p 9001
The proxy server runs and awaits connection
5.2.2 In standalone/proxy_setup.config change the firefox: firefox/
firefox.exe to /usr/bin/firefox as appropriate for Linux
5.2.3 Run the tests once from the talos directory using the command
python run_tests.py standalone/proxy_setup.config

First time (after installing and setting up) test behavior
----------------------------------------------------------
In step 5.2.3, the first time, the browser shutdown script starts by
opening the
page http://mozilla/testing/performance/talos/getinfo.html
At this point, a pop up window says file:// is requesting an UNSAFE
operation
which could compromise the machine and then it closes.

In the shell window that runs the test, the test fails with the
following
message:

 python run_tests.py standalone/proxy_setup.config
standalone_setup_proxy:
                Started Wed, 06 Feb 2008 10:03:32
Running test tp:
                Started Wed, 06 Feb 2008 10:03:32
WARNING: failed to terminate: 4562
ERROR: no metrics
FAIL: couldn't initialize firefox
Failed tp:
                Stopped Wed, 06 Feb 2008 10:04:27
FAIL: failure to complete test: tp

Subsequent failures:
-------------------
As explained in the details of my previous post.