Artifactspublic-v0

curl

master
ply4 git calls110 ms288 KiB2 cachedprotocol v2
80 lines3.2 KiBRaw

Continuous Integration for curl

curl runs in many different environments, so every change is run against a large number of test suites.

Every pull request is verified for each of the following:

  • it still builds, warning-free, on Linux, macOS, Windows, BSDs, with both clang and gcc, autotools and cmake, out-of-tree and in-tree.
  • it still builds fine on Windows with all supported MSVC versions
  • it follows rudimentary code style rules
  • the test suite still runs 100% fine
  • the release tarball (the "dist") still works
  • different TLS backends and options still compile and pass tests

If the pull-request fails one of these tests, it shows up as a red X and you are expected to fix the problem. If you do not understand what the issue is or have other problems to fix the complaint, ask and other project members can likely help out.

Consider the following table while looking at pull request failures:

CI platform as shown in PRStateWhat to look at next
Linux / macOS / Windows / ...stableall errors and failures
Code analyzersstablenew findings
checkdocs / checksrc / dist / ...stableall errors and failures
AppVeyorstableall errors and failures
buildbot/curl_Schannel ...stableall errors and failures
curl.curl (linux ...)stableall errors and failures

Sometimes the tests fail or run slowly due to a dependency service temporarily having issues, for example package downloads, or virtualized (non-native) environments. Sometimes a flaky failed test may occur in any jobs.

Windows jobs have a number of flaky issues, most often, these:

  • test run hanging and timing out after 20 minutes.
  • test run aborting with 2304 (hex 0900) or 3840 (hex 0F00).
  • test run crashing with fork errors.
  • steps past the test run exiting with -1073741502 (hex C0000142).

In these cases you can try to update your pull requests to rerun the tests later as described below.

A detailed overview of test runs and results can be found on Test Clutch.

CI servers

Here are the different CI environments that are currently in use, and how they are configured:

GitHub Actions (GHA)

GitHub Actions runs the following tests:

  • Tests with a variety of different compilation options, OSes, CPUs.
  • Static analysis and sanitizers: clang-tidy, address sanitizer, memory sanitizer, thread sanitizer, CodeQL, valgrind, torture tests.

These are each configured in different files in .github/workflows.

Fuzz tests run in the curl-fuzzer repo.

AppVeyor CI

AppVeyor runs a variety of different Windows builds, with different compilation options.

As of October 2025 @bagder, @mback2k, @jay, @vszakats, @dfandrich and @danielgustafsson have administrator access to the AppVeyor CI environment. Additional admins/group members can be added on request.

The tests are configured in appveyor.yml.

1<!--
2Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
4SPDX-License-Identifier: curl
5-->
7# Continuous Integration for curl
9curl runs in many different environments, so every change is run against a
10large number of test suites.
12Every pull request is verified for each of the following:
14- it still builds, warning-free, on Linux, macOS, Windows, BSDs, with both
15 clang and gcc, autotools and cmake, out-of-tree and in-tree.
16- it still builds fine on Windows with all supported MSVC versions
17- it follows rudimentary code style rules
18- the test suite still runs 100% fine
19- the release tarball (the "dist") still works
20- different TLS backends and options still compile and pass tests
22If the pull-request fails one of these tests, it shows up as a red X and you
23are expected to fix the problem. If you do not understand what the issue is or
24have other problems to fix the complaint, ask and other project members can
25likely help out.
27Consider the following table while looking at pull request failures:
29| CI platform as shown in PR | State | What to look at next |
30| ----------------------------------- | ------ | -------------------------- |
31| Linux / macOS / Windows / ... | stable | all errors and failures |
32| Code analyzers | stable | new findings |
33| checkdocs / checksrc / dist / ... | stable | all errors and failures |
34| AppVeyor | stable | all errors and failures |
35| buildbot/curl_Schannel ... | stable | all errors and failures |
36| curl.curl (linux ...) | stable | all errors and failures |
38Sometimes the tests fail or run slowly due to a dependency service temporarily
39having issues, for example package downloads, or virtualized (non-native)
40environments. Sometimes a flaky failed test may occur in any jobs.
42Windows jobs have a number of flaky issues, most often, these:
43- test run hanging and timing out after 20 minutes.
44- test run aborting with 2304 (hex 0900) or 3840 (hex 0F00).
45- test run crashing with fork errors.
46- steps past the test run exiting with -1073741502 (hex C0000142).
48In these cases you can try to update your pull requests to rerun the tests
49later as described below.
51A detailed overview of test runs and results can be found on
52[Test Clutch](https://testclutch.curl.se/).
54## CI servers
56Here are the different CI environments that are currently in use, and how they
57are configured:
59### GitHub Actions (GHA)
61GitHub Actions runs the following tests:
63- Tests with a variety of different compilation options, OSes, CPUs.
64- Static analysis and sanitizers: clang-tidy, address sanitizer,
65 memory sanitizer, thread sanitizer, CodeQL, valgrind, torture tests.
67These are each configured in different files in `.github/workflows`.
69Fuzz tests run in the [curl-fuzzer repo](https://github.com/curl/curl-fuzzer).
71### AppVeyor CI
73AppVeyor runs a variety of different Windows builds, with different compilation
74options.
76As of October 2025 `@bagder`, `@mback2k`, `@jay`, `@vszakats`, `@dfandrich`
77and `@danielgustafsson` have administrator access to the AppVeyor CI
78environment. Additional admins/group members can be added on request.
80The tests are configured in `appveyor.yml`.
Diagnostics4 git calls · 110 ms
CallStatusSizeTime0110 ms
discover200152 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=152
git.server.agent=gitty/1.0
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch object-format
git.server.fetch=shallow filter sideband-all
git.protocol.version=2
git.pkt.frames=8
git.pkt.data=6
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=152
git.pkt.payload.max=34
ls-refs200149 B · hit3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=149
git.response.cache=HIT
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=149
git.pkt.payload.max=78
git.ls_refs.count=2
git.ls_refs.head=refs/heads/master
fetchblob:none · deepen 10200287 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=105
git.response.bytes=293470
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=blob:none
git.fetch.filter.requested=tree:0
git.fetch.filter.fallback=blob:none
git.fetch.filter.learned=false
git.fetch.wants=31c911efe5652725e930f4d2e60c9060e5f6646d
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=10
git.pkt.data=8
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=293470
git.pkt.payload.max=65516
git.sideband.band1.bytes=293354
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=87
git.pack.bytes=293354
git.pack.ofs_delta=0
git.pack.ref_delta=1
git.pack.chain.max=1
git.pack.trailer=6a646bcda6740bab42e321b51998b52ea15146c0
git.pack.full=86
Open pack map
fetch2001.6 KiB105 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=1625
git.response.cache=MISS
git.response.duration_ms=105
git.fetch.wants=63ae79f14acf9420fd0908bc65178db0e6efc8c7
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=3
git.pkt.data=2
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=1625
git.pkt.payload.max=1604
git.sideband.band1.bytes=1603
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://5ad2236b39de4c8bd8f6270ea63f3ea9.artifacts.cloudflare.net/git/public-v0/curl.git
Ref
refs/heads/master
Commit
31c911efe5652725e930f4d2e60c9060e5f6646d
cf-ray
a5e2bfd7af8389da
Request
b3d8158e…
Protocol
v2 · sha1
Agent
gitty/1.0
Filter
advertised
Fetch
shallow filter sideband-all
Capabilities
agent ls-refs fetch object-format