Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code

Unified Diff: test/runners/chromium_remote_process.js

Issue 29891680: Issue 6986 - Don't use chromium remote interface on Windows (Closed) Base URL: https://hg.adblockplus.org/adblockpluscore/
Patch Set: Created Sept. 25, 2018, 9:59 p.m.
Use n/p to move between diff chunks; N/P to move between comments.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: test/runners/chromium_remote_process.js
===================================================================
--- a/test/runners/chromium_remote_process.js
+++ b/test/runners/chromium_remote_process.js
@@ -54,17 +54,17 @@
catch (error)
{
console.error(error);
}
}
function startChromium(chromiumPath)
{
- fs.chmodSync(chromiumPath, fs.constants.S_IRWXU);
+ fs.chmodSync(chromiumPath, 0o700);
Sebastian Noack 2018/09/25 22:12:46 fs.constants.S_IRWXU is 0o700. This change has no
hub 2018/09/26 01:03:25 on Windows? I expect it to be undefined there.
Sebastian Noack 2018/09/26 01:10:51 Geo, can you confirm?
geo 2018/09/26 13:34:09 Well, it get's rid of the `fs.chmodSync` error. Ho
let dataDir = fs.mkdtempSync(path.join(os.tmpdir(), "chromium-data"));
let child = null;
return {
kill: () => child && child.kill(),
done: new Promise((resolve, reject) =>
{
child = childProcess.execFile(chromiumPath, [
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld