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

fix partially #13115 (now works for cpp; but still fails for js on openbsd) #16167

Merged
merged 6 commits into from Dec 11, 2020

Conversation

timotheecour
Copy link
Member

@timotheecour timotheecour commented Nov 28, 2020

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

  • doesn't yet work for openbsd + js ; EDIT: ... due to an upstream nodejs bug that has been patched in more recent nodejs version

@timotheecour timotheecour changed the title fix #13115 properly (works for c,js,cpp,vm) finish fix #13115 (now also works for cpp) Nov 28, 2020
@timotheecour timotheecour marked this pull request as draft November 28, 2020 05:14
@timotheecour timotheecour mentioned this pull request Nov 28, 2020
16 tasks
@timotheecour timotheecour changed the title finish fix #13115 (now also works for cpp) fix partially #13115 (now also works for cpp) Nov 28, 2020
@timotheecour timotheecour changed the title fix partially #13115 (now also works for cpp) fix partially #13115 (now also works for cpp) (partial because fails on openbsd) Nov 28, 2020
@timotheecour timotheecour marked this pull request as ready for review November 28, 2020 08:01
@timotheecour timotheecour changed the title fix partially #13115 (now also works for cpp) (partial because fails on openbsd) fix #13115 (now also works for cpp) (but still fails on openbsd) Nov 29, 2020
@euantorano
Copy link
Contributor

This seems to have a conflict with tests/exception/t13115.nim. I assume JS on OpenBSD still exhibits the same behaviour even with this patch? If so, that's quite strange and I'll need to dig a bit to work out why.

@timotheecour
Copy link
Member Author

This seems to have a conflict with tests/exception/t13115.nim.

fixed

I assume JS on OpenBSD still exhibits the same behaviour even with this patch? If so, that's quite strange and I'll need to dig a bit to work out why.

thanks

@timotheecour
Copy link
Member Author

friendly ping @Clyybber

@Clyybber
Copy link
Contributor

Clyybber commented Dec 3, 2020

I think this should work on OpenBSD before we merge this.

@timotheecour timotheecour changed the title fix #13115 (now also works for cpp) (but still fails on openbsd) fix partially #13115 (now also works for cpp) (but still fails on openbsd) Dec 3, 2020
@timotheecour timotheecour changed the title fix partially #13115 (now also works for cpp) (but still fails on openbsd) fix partially #13115 (now works for cpp; but still fails for js on openbsd) Dec 3, 2020
@timotheecour timotheecour force-pushed the pr_fix_13115_cpp branch 2 times, most recently from da0582d to f6893f2 Compare December 3, 2020 19:42
@timotheecour
Copy link
Member Author

timotheecour commented Dec 3, 2020

PTAL

I think this should work on OpenBSD before we merge this.

@euantorano
Copy link
Contributor

euantorano commented Dec 3, 2020 via email

let (outp, exitCode) = execCmdEx(cmd)
doAssert msg in outp, cmd & "\n" & msg
doAssert exitCode == 1
main()
Copy link
Contributor

@Clyybber Clyybber Dec 3, 2020

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.

Copy link
Member Author

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:

@timotheecour
Copy link
Member Author

friendly ping

@Araq Araq merged commit bb1c962 into nim-lang:devel Dec 11, 2020
@timotheecour timotheecour deleted the pr_fix_13115_cpp branch December 11, 2020 09:43
mildred pushed a commit to mildred/Nim that referenced this pull request Jan 11, 2021
…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
ardek66 pushed a commit to ardek66/Nim that referenced this pull request Mar 26, 2021
…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
@VlkrS
Copy link
Contributor

VlkrS commented Mar 5, 2022

Both OpenBSD-current and OpenBSD-stable have a more recent version of nodejs now.
Is it possible to re-evaluate?

@euantorano
Copy link
Contributor

Both OpenBSD-current and OpenBSD-stable have a more recent version of nodejs now. Is it possible to re-evaluate?

Certainly would be a good idea. Looks like the current version is 16.14.0: https://openports.se/lang/node

@VlkrS
Copy link
Contributor

VlkrS commented Mar 5, 2022

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 ;)

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

Successfully merging this pull request may close these issues.

None yet

6 participants