You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2017. It is now read-only.
I'm trying to run the annex test under PhantomJS. If we could get this working, we could do things like run web tests in a regression suite or automate generation of certain types of traces. The first issue I ran into is that the current PhantomJS websocket support doesn't seem to be up to snuff. So, I hacked up a quick change to keep the trace in memory during record; see the in-memory-trace branch:
Save the following PhantomJS script into file load.js:
var page = require('webpage').create(),
system = require('system'),
address;
if (system.args.length === 1) {
console.log('Usage: loadspeed.js <some URL>');
phantom.exit();
}
address = system.args[1];
page.onConsoleMessage = function (msg) {
console.log('Got message ' + msg);
};
page.open(address, function (status) {
console.log("loaded");
page.evaluate(function () {
console.log("hello");
console.log(J$.trace_output);
});
});
Check out the in-memory-trace jalangi branch. In analysis.js, line 119, set IN_MEMORY_BROWSER_LOG to inBrowser.
Start the local web server (python scripts/jalangi.py server), and instrument annex as shown in README.md. No need to start the websocket server, though.
Run the following command (assumes phantomjs is in your path):
TypeError: 'undefined' is not an object (evaluating 'screen.orientation.indexOf')
http://127.0.0.1:8000/tests/tizen/annex/index_jalangi_.html:24
Got message TypeError: Attempting to change writable attribute of unconfigurable property.
Got message TypeError: Attempting to change writable attribute of unconfigurable property.
at printableValue (http://127.0.0.1:8000/src/js/analysis.js:1028)
at http://127.0.0.1:8000/src/js/analysis.js:1410
at http://127.0.0.1:8000/src/js/analysis.js:1236
at G (http://127.0.0.1:8000/src/js/analysis.js:541)
at http://127.0.0.1:8000/tests/tizen/annex/lib/jquery-1.6.2.min_jalangi_.js:1222
at invokeFun (http://127.0.0.1:8000/src/js/analysis.js:494)
at http://127.0.0.1:8000/src/js/analysis.js:585
at http://127.0.0.1:8000/tests/tizen/annex/lib/jquery-1.6.2.min_jalangi_.js:13591
Got message TypeError: 'undefined' is not an object (evaluating 'g.apply')
Got message TypeError: 'undefined' is not an object (evaluating 'g.apply')
at invokeFun (http://127.0.0.1:8000/src/js/analysis.js:494)
at http://127.0.0.1:8000/src/js/analysis.js:585
at http://127.0.0.1:8000/tests/tizen/annex/js/annex_jalangi_.js:1462
loaded
Got message hello
Got message [3,"tests/tizen/annex/lib/jquery-1.6.2.min_jalangi_.js",88149,0,6]
,[4,1,88141,1,17]
,[4,3,17473,3,8]
,[4,5,17481,5,8]
,[3,"tests/tizen/annex/js/annex_jalangi_.js",11097,7,6]
,[4,3,9889,10,17]
The trace is printing, which is good, but there are some other JS errors I can't fully grok. @ksen007, any idea what could be going wrong? PhantomJS is based on Webkit, but not the absolute latest version. This is not super urgent, but if we could get this working sometime, that would be great.
The text was updated successfully, but these errors were encountered:
I'm trying to run the annex test under PhantomJS. If we could get this working, we could do things like run web tests in a regression suite or automate generation of certain types of traces. The first issue I ran into is that the current PhantomJS websocket support doesn't seem to be up to snuff. So, I hacked up a quick change to keep the trace in memory during record; see the in-memory-trace branch:
https://github.com/SRA-SiliconValley/jalangi/tree/in-memory-trace
I still get some errors on this branch when loading in PhantomJS, though. Steps to reproduce:
in-memory-trace
jalangi branch. Inanalysis.js
, line 119, setIN_MEMORY_BROWSER_LOG
toinBrowser
.python scripts/jalangi.py server
), and instrument annex as shown in README.md. No need to start the websocket server, though.phantomjs
is in your path):When I run, I get the following output:
The trace is printing, which is good, but there are some other JS errors I can't fully grok. @ksen007, any idea what could be going wrong? PhantomJS is based on Webkit, but not the absolute latest version. This is not super urgent, but if we could get this working sometime, that would be great.
The text was updated successfully, but these errors were encountered: