+- WebPagetest Forums (http://www.webpagetest.org/forums)
+-- Forum: WPT Monitor (/forumdisplay.php?fid=22)
+--- Forum: Bugs/Issues (/forumdisplay.php?fid=24)
+--- Thread: Everything is 0 on Chrome and Firefox :( (/showthread.php?tid=11384)
Everything is 0 on Chrome and Firefox :( - slarisch - 07-03-2012 11:38 PM
Hi,
I am using WPT Monitor 0.3.0 (from 2011/03/18) and I have 3 WPT (Windows XP) Server working as agents, one for each browser (Chrome, IE8, FF12). My agents are setup on a VMware Server, so it's 100% same configuration (besides my location.ini and settings.ini).
When I start a test from WPT-Monitor, everything is fine. The agents starts their work correctly (with urlBlast or wptdriver). I can see all results for IE8 in WPTMonitor, but not fpr Chrome and Firefox. Everything in the "Results"-Tab is "0", but the test are done correctly and I can see the results on my Webpagetest-Server, even the waterfall-IMGs.
What I figured out:
In wpt_functions.inc ~row 690 it says:
PHP Code:
$pageDataLocation = $xml->data->run[0]->firstView->rawData->pageData;
The pageDataLocation is the 1_IEWPG.txt file from the result-folder located on the WPT Agent, which in this case has no!! header, just the data. When I look into all the other IEWPG files from my IE-Agents, there is a header.
Therefor the
PHP Code:
$headers = explode("\t",$lines[0]);
What could be the reason for this?? Any ideas?
Kind Regards,
Sebastian
EDIT:
It's very likely a Webpagetest problem and not a WPT Monitor problem. When I do a test from my Firefox-Agent itself (localy, not via WPT Monitor) I have no headers in the IEWPG files as well.
Anyway, does anybody has any ideas?
RE: Everything is 0 on Chrome and Firefox :( - pmeenan - 07-10-2012 03:25 AM
Accessing the IEWPG files on disk directly will certainly have this problem - the headers were removed from the raw files for the Chrome and Firefox agents and they are appended dynamically when requested through the UI (through csv.php).
RE: Everything is 0 on Chrome and Firefox :( - braincracking - 07-31-2012 06:15 PM
Hi
I'm having the "0 everywhere problem" too, but for all the browsers
the jobs are correctly created, the tests piloted by the monitor and are running correctly, and I can see the results on the WPT installation. However, looking wptMonitor still see 0 for all metrics. Looking at the logs :
Job Processor Log File
Result ID: 120731_F3_4ddd2af046fef0479caffe119680256e
Result ID: 07/31/2012 09:58
[ 07/31/2012 08:08:09 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_F3_4ddd2af046fef0479caffe119680256e Id: 24
[ 07/31/2012 08:08:09 ] [INFO] [ProcessResults] 120731_F3_4ddd2af046fef0479caffe119680256e Completed
[ 07/31/2012 08:08:09 ] [INFO] [wptCallBack] WPT Callback called for result id 120731_F3_4ddd2af046fef0479caffe119680256e
[ 07/31/2012 08:07:39 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_K5_0c7e5878612296b2a55161364fc22424 Id: 23
[ 07/31/2012 08:07:39 ] [INFO] [ProcessResults] 120731_K5_0c7e5878612296b2a55161364fc22424 Completed
[ 07/31/2012 08:07:39 ] [INFO] [wptCallBack] WPT Callback called for result id 120731_K5_0c7e5878612296b2a55161364fc22424
[ 07/31/2012 08:04:05 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_BJ_401d7d52484b598023908c99329ceed5 Id: 19
[ 07/31/2012 08:04:05 ] [INFO] [ProcessResults] 120731_BJ_401d7d52484b598023908c99329ceed5 Completed
[ 07/31/2012 08:04:05 ] [INFO] [wptCallBack] WPT Callback called for result id 120731_BJ_401d7d52484b598023908c99329ceed5
[ 07/31/2012 08:03:07 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_K5_0c7e5878612296b2a55161364fc22424 Id: 23
[ 07/31/2012 08:03:07 ] [INFO] [ProcessResults] 120731_K5_0c7e5878612296b2a55161364fc22424 Completed
[ 07/31/2012 08:03:01 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_F3_4ddd2af046fef0479caffe119680256e Id: 24
[ 07/31/2012 08:03:01 ] [INFO] [ProcessResults] 120731_F3_4ddd2af046fef0479caffe119680256e Completed
[ 07/31/2012 08:02:48 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_FZ_9b3189812e1bc6ec29ef44c791cc1ba6 Id: 21
[ 07/31/2012 08:02:48 ] [INFO] [ProcessResults] 120731_FZ_9b3189812e1bc6ec29ef44c791cc1ba6 Completed
[ 07/31/2012 08:02:48 ] [INFO] [wptCallBack] WPT Callback called for result id 120731_FZ_9b3189812e1bc6ec29ef44c791cc1ba6
[ 07/31/2012 07:58:54 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_KS_4b6add2230afb11cb2b9a6bfd6ccd2a6 Id: 20
[ 07/31/2012 07:58:54 ] [INFO] [ProcessResults] 120731_KS_4b6add2230afb11cb2b9a6bfd6ccd2a6 Completed
[ 07/31/2012 07:58:54 ] [INFO] [wptCallBack] WPT Callback called for result id 120731_KS_4b6add2230afb11cb2b9a6bfd6ccd2a6
[ 07/31/2012 07:58:53 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_W8_bea6d6dd897e2b62dc3b7c3163826c0e Id: 22
[ 07/31/2012 07:58:53 ] [INFO] [ProcessResults] 120731_W8_bea6d6dd897e2b62dc3b7c3163826c0e Completed
[ 07/31/2012 07:58:53 ] [INFO] [wptCallBack] WPT Callback called for result id 120731_W8_bea6d6dd897e2b62dc3b7c3163826c0e
url: http://pluzz.francetv.fr/
[ 07/31/2012 07:58:27 ] [INFO] [ProcessJob] Id:4 Label:Pluzz HP Prod IE 7 - 8 Sumitted job for processing
url: http://pluzz.francetv.fr/
I always have the "0 runs", and for now I cant spot where the problem is.
Any idea on how to debug that ?
RE: Everything is 0 on Chrome and Firefox :( - braincracking - 08-01-2012 09:57 PM
UPDATE :
I had this warning appearing in the jobProcessorLog :
Code:
[ 07/31/2012 08:08:09 ] [WARN] [ProcessResults] Result set with 0 runs for WPTResultdId: 120731_F3_4ddd2af046fef0479caffe119680256e Id: 24Actually my WPT instance is in non-friendly urls mode, so I had to fix some URLs
In monitor.inc, after lines 26 :
PHP Code:
$wptRuntest="/runtest.php";
$wptResult="/results.php?test=";
$wptXmlResult="/xmlResult.php?test=";
PHP Code:
$resultXml = file_get_contents($result['WPTHost'] . $wptXmlResult . $wptResultId );
So far the warning I saw in the logs disappeared, but I'm still investigating on why I have 0 everywhere
RE: Everything is 0 on Chrome and Firefox :( - braincracking - 08-08-2012 01:27 AM
All seems to work fine now. I think that what fixed it at the end was that I gave the write permission on the db folder. My fault, but a warning would have been a good idea
