-
-
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
fix partially #13115 (now works for cpp; but still fails for js on openbsd) #16167
Conversation
This seems to have a conflict with |
3ec9b19
to
2d28392
Compare
fixed
thanks |
2d28392
to
aafbc7c
Compare
friendly ping @Clyybber |
I think this should work on OpenBSD before we merge this. |
aafbc7c
to
76e258b
Compare
da0582d
to
f6893f2
Compare
PTAL
|
It looks like there was a node patch to support the null character, I need to work out which versions that patch landed in as it’s possible that version isn’t packaged for OpenBSD yet.
EDIT: looks like 12.16.1: https://openports.se/lang/node
It looks like the node change was released in 12.16.2: nodejs/node#32313
It’s probably best to leave the test disabled for JS on OpenBSD for now if that’s the case, or else we may need to build our own copy of node as part of the build (or install a binary that’s not in ports...).
…On Thu, 3 Dec 2020, at 19:50, Timothee Cour wrote:
PTAL
> I think this should work on OpenBSD before we merge this.
* openbsd on js was already failing prior to this PR and fixing it can
be done later. I believe this is an upstream nodejs bug similar to the
one I had submitted last year (nodejs/node#28761
<nodejs/node#28761>); we should report this
upstream after confirming (/cc @euantorano
<https://github.com/euantorano> since you have access to openbsd).
* I've amended PR msg and commit msg with `s/fix/fix partially/` so
#13115 <#13115> won't auto-close
when this PR is merged
* I've improved test coverage for this bug by calling `execCmdEx`
directly instead of relying on testament spec DSL; the test is stronger
now:
* it now tests openbsd (except for js)
* it now checks the msg is exactly what we expect (including the
`\0`)
* it now checks VM too
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#16167 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFW24J6ZRBD6GH5SG2GPXTSS7TXRANCNFSM4UFRMSPA>.
|
let (outp, exitCode) = execCmdEx(cmd) | ||
doAssert msg in outp, cmd & "\n" & msg | ||
doAssert exitCode == 1 | ||
main() |
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.
Please get rid of this abomination and use testament to accomplish what you want.
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.
testament spec DSL isn't flexible enough for this test, sorry. If you disagree, please show a complete example that tests VM, openbsd (for non-js case), the '\0' being part of the output message, allows avoiding combinatorial explosion (as i do in this PR) etc, while also avoiding generating N different test files (not DRY nor desirable).
testament spec may be good for the general case, but you'll always have special cases, which need things like:
- trunner.nim
- trunner_thirdparty.nim (remove .github/workflows/ci_ssl.yml; instead run via trunner_thirdparty #16221)
- tosproc.nim
- this test, etc
f6893f2
to
41f552c
Compare
d5ea1cd
to
d394231
Compare
friendly ping |
…js on openbsd) (nim-lang#16167) * fix partially nim-lang#13115 properly (works for c,js,cpp,vm; still fails for js on openbsd) * address comment: also test with -d:danger, -d:debug
…js on openbsd) (nim-lang#16167) * fix partially nim-lang#13115 properly (works for c,js,cpp,vm; still fails for js on openbsd) * address comment: also test with -d:danger, -d:debug
Both OpenBSD-current and OpenBSD-stable have a more recent version of nodejs now. |
Certainly would be a good idea. Looks like the current version is 16.14.0: https://openports.se/lang/node |
It's 12.22.9 for -stable, but in any case the fix from 12.16.2 should be in ;) |
fix partially #13115 (js on openbsd still broken for some reason)
/cc @xflywind
before PR: works for js,cpp,vm
after PR: also cpp
future work
openbsd + js
; EDIT: ... due to an upstream nodejs bug that has been patched in more recent nodejs version