test: fix/skip tests for ChakraCore

* Fixed test-async-wrap-pop-id-during-load to run correctly
* Skipped test-assert-builtins-not-read-from-filesystem since it's
  testing the assert message behavior we don't support anyway.

PR-URL: #556
Reviewed-By: Jimmy Thomson <jithomso@microsoft.com>

Author: kfarnung

test/parallel/parallel.status

@@ -25,6 +25,7 @@ test-postmortem-metadata: PASS,FLAKY
 [$jsEngine==chakracore]
 # These tests are failing for Node-Chakracore and should eventually be fixed
 test-assert-checktag : SKIP
+test-assert-builtins-not-read-from-filesystem : SKIP
 test-async-hooks-disable-during-promise : SKIP
 test-async-hooks-enable-during-promise : SKIP
 test-async-hooks-promise : SKIP

test/parallel/test-async-wrap-pop-id-during-load.js

@@ -1,6 +1,6 @@
 'use strict';
 
-require('../common');
+const common = require('../common');
 
 if (process.argv[2] === 'async') {
   async function fn() {
@@ -13,9 +13,14 @@ if (process.argv[2] === 'async') {
 const assert = require('assert');
 const { spawnSync } = require('child_process');
 
+const engineArgs = [];
+if (!common.isChakraEngine) {
+  engineArgs.push('--stack_size=75');
+}
+
 const ret = spawnSync(
   process.execPath,
-  ['--stack_size=75', __filename, 'async']
+  [...engineArgs, __filename, 'async']
 );
 assert.strictEqual(ret.status, 0,
                    `EXIT CODE: ${ret.status}, STDERR:\n${ret.stderr}`);