mirror of
https://github.com/curl/curl.git
synced 2026-04-14 00:51:42 +08:00
7dd5bb77c3
With Schannel and Unicode, `-shallow=13`. It finishes in 12 minutes,
making it the slowest Windows job. It's still on par with torture jobs
on other platforms (though they manage to fit `-shallow=25`).
Also `-shallow=13` still caught leaks in multiple tests.
Also:
- test2300: exclude from CI Windows torture tests.
- experimental.
The downside of going with deeper torture tests, is that it requires
increasing the job timeout. This in turns means that a hung job takes
more minutes to be killed (due to GitHub bugs where a hung step does not
honor the per-step timeout on Windows, another bug where a hung job gets
killed +5 minutes above the workflow timeout, and another bug (or
feature?) where other failed/hung jobs in the the workflow cannot be
restarted till the last job finishes or gets killed. And all this
probably related to a Perl bug which makes it hang on fork errors, which
is turn related to Cygwin/MSYS2 runtime bugs which breaks fork in case
of curl's mixed MSYS2-Perl/native-curl-binaries environment.)
The end result in longer forced waits before being able to restart flaky
jobs, which slows down iterations and annoying.
Also tried:
- non-c-ares job: detected known issues much less often.
- replaced libidn2 with WinIDN: detected known issues much less often.
- runtests -j9-j20 values: did not make a difference.
- other `-shallow` values: 20 is the max feasible, but comes with the
downside described above.
Ref: #19675 (reboot of)
Follow-up to
|
||
|---|---|---|
| .. | ||
| appveyor-status.yml | ||
| checkdocs.yml | ||
| checksrc.yml | ||
| codeql.yml | ||
| configure-vs-cmake.yml | ||
| curl-for-win.yml | ||
| distcheck.yml | ||
| fuzz.yml | ||
| http3-linux.yml | ||
| label.yml | ||
| linux-old.yml | ||
| linux.yml | ||
| macos.yml | ||
| non-native.yml | ||
| windows.yml | ||