Broken TLS tests in master branch
See original GitHub issuethe TLS tests in PostgreSQL do not pass due to the breaking changes of upgradeToSsl
in Vert.x core 4.0. We need a rework implementation for TLS in PostgreSQL and that also makes sense for MySQL TLS support in #299.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
Random test failures on some tests on master #1256 - GitHub
I've been working on a patch and was trying to get a baseline for the test suites using tox on the master branch....
Read more >Flaky tests - GitLab Docs
When a test frequently fails in master , create a ~"failure::flaky-test" issue. ... in maintenance scheduled pipelines on the master branch, and saves...
Read more >Is there a way to avoid broken or untested code from going ...
Even if these tests pass the master branch may fail them or be plain broken after merge. See an example of how just...
Read more >Quick fix to Git's fatal 'unable to access SSL certificate' error
That will turn off SSL during the git clone operation and allow you to push and pull back and forth to your server....
Read more >Understanding Continuous Integration and ... - Geekflare
We have adopted the practice of writing tests as a means of ensuring that the new ... There is also the possibility of...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I patched 3.8 and master with work around that will make TLS work in both cases
see https://github.com/eclipse-vertx/vert.x/commit/6a255436777a77640b8f31da35ef96876d773578