-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
testament r
doesn't honor --targets:js nor what's in the spec
#14242
Labels
Comments
This was referenced May 6, 2020
I keep hitting this.
this one reflects 2 bugs: this bug, and the fact that unittest works differently for js vs non-js, giving different results because:
instead a EDIT: fixing 1st bug in #16163 EDIT: fixing 2nd bug in #16165 |
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Nov 28, 2020
…w honors --targets
timotheecour
added a commit
to timotheecour/Nim
that referenced
this issue
Nov 28, 2020
…w honors --targets
mildred
pushed a commit
to mildred/Nim
that referenced
this issue
Jan 11, 2021
…w honors --targets (nim-lang#16163) * fix nim-lang#14242 `testament r tests/js/foo` now works; testament now honors --targets * fix shouldfail
ardek66
pushed a commit
to ardek66/Nim
that referenced
this issue
Mar 26, 2021
…w honors --targets (nim-lang#16163) * fix nim-lang#14242 `testament r tests/js/foo` now works; testament now honors --targets * fix shouldfail
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
testament r
doesn't honor --targets:js nor what's in the specExample
Current Output
runs C target
Expected Output
runs js target: both because of
--target:js
and because the test would normally run via jsAdditional Information
D20200505T030352
this makes it inconvenient to run a test locally, maybe I'm missing some option?
The text was updated successfully, but these errors were encountered: