-
Notifications
You must be signed in to change notification settings - Fork 339
test: skip tests that are marked flaky for node-chakracore #436
test: skip tests that are marked flaky for node-chakracore #436
Conversation
Remove mentions to tests that no longer exist from .status files.
Tests were marked as FLAKY in the .status files for ChakraCore because they were failing. This commit changes the .status files to skip those tests instead. Fixes: nodejs#426
Some tests check for the ChakraCore engine at runtime to skip, since these tests depend on V8 features. This commit adds those tests to the .status files, so they aren't started at all.
Move all tests that are fully skipped at runtime for the ChakraCore engine to the .status files as a SKIP entry, so they aren't started at all.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, cc @nodejs/node-chakracore
With this we lose the ability to quickly run these tests, but we reduce the delta to the upstream tests and almost everything is organized in the status files. Almost, because tests that are only partially skipped must still be skipped in the test file with common.skip
. I think this is a good solution.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, pending CI: https://ci.nodejs.org/job/chakracore-test-pull-request/161/
@MSLaguana you had seen that lint error before, no? |
Yeah, we haven't spent the time to make our readme files lint-clean since that's a relatively new addition. |
Remove mentions to tests that no longer exist from .status files. PR-URL: #436 Reviewed-By: João Reis <[email protected]> Reviewed-By: Jack Horton <[email protected]>
Tests were marked as FLAKY in the .status files for ChakraCore because they were failing. This commit changes the .status files to skip those tests instead. PR-URL: #436 Fixes: #426 Reviewed-By: João Reis <[email protected]> Reviewed-By: Jack Horton <[email protected]>
Some tests check for the ChakraCore engine at runtime to skip, since these tests depend on V8 features. This commit adds those tests to the .status files, so they aren't started at all. PR-URL: #436 Refs: #426 Reviewed-By: João Reis <[email protected]> Reviewed-By: Jack Horton <[email protected]>
Move all tests that are fully skipped at runtime for the ChakraCore engine to the .status files as a SKIP entry, so they aren't started at all. PR-URL: #436 Refs: #426 Reviewed-By: João Reis <[email protected]> Reviewed-By: Jack Horton <[email protected]>
Landed in a7d03f2...a008278. Thanks! |
Tests were marked as FLAKY in the .status files for ChakraCore because they were failing. This commit changes the .status files to skip those tests instead. PR-URL: nodejs#436 Fixes: nodejs#426 Reviewed-By: João Reis <[email protected]> Reviewed-By: Jack Horton <[email protected]>
Currently, most tests that are marked as
FLAKY
for theChakraCore
engine in the tests'.status
files are actually failing everytime they are run.This PR marks those tests as
SKIP
, instead.FLAKY
should be used for tests that fail only sometimes due to timing or racing conditions issues but pass most of the time.This PR contains four different changes, divided by commit:
.status
files, mentions to tests that no longer exist.FLAKY
for Node-Chakracore in the.status
files..status
files, tests that are being skipped at runtime for depending on V8 features..status
files.Fixes: #426
Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passesAffected core subsystem(s)
test