Skip to content

Conversation

@mback2k
Copy link
Member

@mback2k mback2k commented Nov 5, 2021

Adds Schannel variants of SSLpinning tests that include the option
--ssl-revoke-best-effort to ignore certificate revocation check
failures which is required due to our custom test CA certificate.

Disable the original variants if the Schannel backend is enabled.

Also skip all IDN tests which are broken while using an msys shell.

This is a step to simplify test exclusions for Windows and MinGW.

@mback2k mback2k added tests Windows Windows-specific CI Continuous Integration labels Nov 5, 2021
@mback2k mback2k self-assigned this Nov 5, 2021
@mback2k mback2k force-pushed the fix-schannel-tests branch 2 times, most recently from 3543fc6 to 157cc37 Compare November 6, 2021 14:39
Adds Schannel variants of SSLpinning tests that include the option
--ssl-revoke-best-effort to ignore certificate revocation check
failures which is required due to our custom test CA certificate.

Disable the original variants if the Schannel backend is enabled.

Also skip all IDN tests which are broken while using an msys shell.

This is a step to simplify test exclusions for Windows and MinGW.
@mback2k mback2k force-pushed the fix-schannel-tests branch from 157cc37 to 6aeae37 Compare November 6, 2021 15:14
@mback2k mback2k changed the title tests: add Schannel-specific tests or disabled unsupported ones tests: add Schannel-specific tests or disable unsupported ones Nov 7, 2021
@mback2k mback2k marked this pull request as ready for review November 7, 2021 12:42
@mback2k mback2k requested review from MarcelRaad, bagder and jay November 7, 2021 12:42
@jay
Copy link
Member

jay commented Nov 7, 2021

Works for me. Why did you add quotes to the tests field?

@mback2k
Copy link
Member Author

mback2k commented Nov 8, 2021

Because a leading ! without " has special meaning in YAML.

@mback2k
Copy link
Member Author

mback2k commented Nov 8, 2021

Thanks guys. @bagder Do you think this can go in before the release or should I rather wait with this?

@bagder
Copy link
Member

bagder commented Nov 8, 2021

I think they can go in before the release.

@mback2k
Copy link
Member Author

mback2k commented Nov 8, 2021

@bagder unfortunately it seems like I am no longer allowed to push to master, not sure what changed though:
image

remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: You're not authorized to push to this branch. Visit https://docs.github.com/articles/about-protected-branches/ for more information.
To git@github.com:curl/curl.git
 ! [remote rejected] master -> master (protected branch hook declined)

@bagder
Copy link
Member

bagder commented Nov 8, 2021

Sorry, that was me experimenting with a feature that I shouldn't have. Hopefully fixed now.

@mback2k mback2k closed this in b3e1ed3 Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Continuous Integration tests Windows Windows-specific

Development

Successfully merging this pull request may close these issues.

4 participants