-
Notifications
You must be signed in to change notification settings - Fork 46
Open
Description
Currently when running test262-harness test/**/*.js on the command line or Powershell it gives a totally different result than running it on Git Bash.
Step to reproduce:
- run
test262-harness test/**/*.json either command line or powershell.
Results:
Git Bash: 205 tests run
Powershell/Command Line: 58797 tests run
Here is an example of the output:
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/bigint-errors.js (default)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/bigint-errors.js (strict mode)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/bigint-toprimitive.js (default)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/bigint-toprimitive.js (strict mode)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/bigint-wrapped-values.js (default)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/bigint-wrapped-values.js (strict mode)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/coerce-bigint-to-string.js (default)
Expected no error, got SyntaxError: Invalid or unexpected token
FAIL test/language/expressions/addition/coerce-bigint-to-string.js (strict mode)
Expected no error, got SyntaxError: Invalid or unexpected token
Expected Result:
The tests should be consistent.
Version: 3.5
OS: Windows: 10
Metadata
Metadata
Assignees
Labels
No labels