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 Mar 10, 2022. It is now read-only.
There are instances of js-test.js functions used in stringified parameters. These parameters are parsed and then passed to testharness.js directly, which would cause problems since they use the old functions. Example:
This would be transformed as: assert_true(areArraysEqual(index.keyPath, ['c', 'd']);.
Running this test in the testharness.js framework would fail, since areArraysEqual is a js-test.js function.
This is likely very hard to do correctly and not common the chromium source so this is low priority.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There are instances of
js-test.js
functions used in stringified parameters. These parameters are parsed and then passed totestharness.js
directly, which would cause problems since they use the old functions. Example:shouldBeTrue("areArraysEqual(index.keyPath, ['c', 'd'])");
This would be transformed as:
assert_true(areArraysEqual(index.keyPath, ['c', 'd']);
.Running this test in the
testharness.js
framework would fail, sinceareArraysEqual
is ajs-test.js
function.This is likely very hard to do correctly and not common the chromium source so this is low priority.
The text was updated successfully, but these errors were encountered: