-
Notifications
You must be signed in to change notification settings - Fork 376
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
Bump lit/luvi versions to latest for testing #1063
Conversation
Looks like lit may need a lua-openssl tweak. |
Yep, needs luvit/lit#257 |
Published a fixed lit (3.7.3) and rebased to include #1065 |
please rebase on #1078 and relaunch CI. |
Rebased on latest master and merged #1078 for testing |
The fail narrow
|
curl/curl#3271 says TLS1.3 session reuse don't same with old version. I wll do some work on it. |
ok 190 tls-connect-session-reuse - tls connect session reuse test on linux/mac |
Nice work, rebased on latest master. EDIT: Failing |
And need to add uv.spawn for windows in luv |
luvit/luv@27a5b5f shows uv.spawn works well on windows. https://ci.appveyor.com/project/racker-buildbot/luv/branch/master/job/65mp6f76a96jhf80#L1281 |
Looks like the test machines may not have enough RAM or swap to run the test: |
I can do some test on real windows box, in this weekend. |
libuv/libuv#2133 That explain why luv direct uv.spawn success but luvi/luvit fails. |
Bumping luv to latest might get all tests to pass now, see luvit/luv#386 for the likely cause of the |
I think we've got everything working again 🎉. Not sure why the https-client test failed here, but it seems random and I can't reproduce it, so I guess we'll just need to look into it if it becomes a problem. I'm going to rebase this branch onto latest master for one last test and then we can move forward with a new Luvit release with the latest Luvi. |
This is only for CI purposes. I'll rebase this branch as we fix things, so our goal is to make the CI pass on this branch. See luvit#1058 & luvit#1060
96b4218
to
80318d3
Compare
Closing in favor of #1098 |
This is only for CI purposes. I'll rebase this branch as we fix things, so our goal is to make the CI pass on this branch.
See #1058 & #1060