Identify Windows CI failures: test code bugs, not real network issues#305
Closed
Identify Windows CI failures: test code bugs, not real network issues#305
Conversation
Copilot
AI
changed the title
[WIP] Improve compatibility with other operating systems
Identify Windows CI failures: test code bugs, not real network issues
Mar 3, 2026
Member
|
@copilot so no actual network issues? why are tests failing at wp-cli/wp-cli#6245 then? apparently the wp core download in wp-cli-tests fails, see https://github.com/wp-cli/wp-cli/actions/runs/22116136930/job/63924669886?pr=6245 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Investigates cURL error 77 failures on Windows CI (
windows-2025runner) that were blocking WordPress downloads and all behat scenarios.Root cause analysis
Unit tests (
wp-cli/wp-cli, job 63924672742) — three failures, none are real connectivity issues:testHttpRequestBadCAcert(2 failures):tempnam(sys_get_temp_dir(), 'wp-cli-badcacert-pem-')truncates to a 3-char prefix on Windows, producingwp-5EFE.tmp. The cURL error 77 message on Windows is"error adding trust anchors from file: ...\wp-5EFE.tmp"vs. the asserted"error setting certificate". Thewp-5EFE.tmppath seen in the original error report is this intentional bad-cert file, not a real SSL failure.WpOrgApiTest::test_http_request_verify@insecure:Mock_Requests_Transportguards withstrpos($verify, sys_get_temp_dir()). On Windows,sys_get_temp_dir()may return an 8.3 short path (RUNNER~1) whiletempnam()returns the long path (runneradmin), causing the guard to silently returnfalseand skip theverify → falseconversion.FileCacheTest::test_import(2 errors):ZipArchivenot found — thezipextension is included insetup-phpfor functional tests but missing for unit tests inreusable-testing.yml.Behat tests (
wp-cli/wp-cli, job 63924669886) — all 203 scenarios fail due to Windows shell quoting:cmd.exetreats single quotes as literals (not string delimiters), sowp eval 'list( $a, $b ) = ...'is tokenized at spaces. WP-CLI receives each token as a separate positional argument.Where fixes belong
testHttpRequestBadCAcertassertionwp-cli/wp-cliMock_Requests_Transportpath normalizationwp-cli/wp-clizipextension for unit testswp-cli/.githubwp evalfeature testswp-cli/wp-cli💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.