Re: Running StandaloneTalos test

You aren't going to get any result from the proxy_setup.config - it 
expressly throws away results since it is just trying to build up the 
local cache of web pages that can be served later.  After a successful 
run with proxy_setup.config you need to run with proxy_run.config.  You 
can see this in the final steps on the StandaloneTalos wiki page; it has 
you switch the proxy over to only serve pages from the local cache and 
use the secondary config file.

I can also see how talos is getting confused, it's expectation is that 
the firefox path is that to the directory that contains both the 
executable and the libraries (ie, I grab a copy of firefox from 
http://stage.mozilla.org/pub/mozilla.org/firefox/nightly/ which I then 
untar to a local directory, then I end up with a firefox directory with 
both firefox-bin and all the other firefox related files in it).  Having 
your executable somewhere else from the library files meant that it was 
unable to install the chrome/components directories.

alice.

[email protected] wrote:
> On Feb 6, 12:13 pm, alice nodelman <[email protected]> wrote:
>> [email protected] wrote:
>>> In step 5.2.3, the first time, the browser shutdown script starts by
>>> opening the
>>> pagehttp://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
>> So, this is another indication that the paths aren't working correctly -
>>   firefox should have opened with a pre-loaded profile that would allow
>> the shutdown script to work, as it was you got the unsafe operation
>> popup window.
>>
>> Can you tell me the path where firefox is on your machine?  And how it
>> looks in the config file?  And the same for the profile path?  I'm
>> hoping that I could set up pretty much the same configuration on my test
>> box and see if I can re-create your situation.
>>
>> Thanks for sticking with this!  It is also reminding me that I need to
>> make another revision of the instructions to cover more of the pitfalls.
>>
>> alice.
> 
> firefox is in /usr/bin/firefox
> the firefox lib is in /usr/lib/firefox.2.0.0.10 and /usr/lib64/firefox.
> 2.0.0.10
> 
> In order to get the page load test working, I had to copy the contents
> of talos/page_load_test/chrome and talos/page_load_test/components to /
> usr/lib64/firefox.2.0.0.10. Still my very first run would fail as
> noted above and subsequently it starts running.
> 
> While running the test, some pages stall. As a result, I pruned talos/
> standalone/proxy_manifest.txt appropriately. At the end of running the
> test, I looked for results file in talos/standalone/output but there
> was none.
> 
> I ran the test again, with a shorter file talos/standalone/
> proxy_manifest.txt. Again, the output directory didn't have any
> results. Is there anything else that I should be looking into.
> 
> I will be happy to help iron out and get this up and running.
> 
> thanks
> - mouli
> 
>