Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent results between Git Bash and Command Line/Powershell #99

Open
irrationalRock opened this issue Mar 12, 2018 · 1 comment
Open

Comments

@irrationalRock
Copy link

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:

  1. run test262-harness test/**/*.js on 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

@astlaurent1
Copy link

In case anyone still experiences issues here:

In git bash, test/**/*.js seems to only match one level deep by default. You have to enable globstar first via shopt -s globstar. If you do so, the glob pattern will match all the js files in test. powershell seems to have this kind of matching by default

More info here: https://www.linuxjournal.com/content/globstar-new-bash-globbing-option

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants