You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TEST_RUNNER_PORT_MIN: "14000"# Must be larger than 12321, which is used for the http cache. See https://cirrus-ci.org/guide/writing-tasks/#http-cache
7
-
CI_FAILFAST_TEST_LEAVE_DANGLING: "1"# Cirrus CI does not care about dangling processes and setting this variable avoids killing the CI script itself on error
8
-
CCACHE_MAXSIZE: "200M"
9
-
CCACHE_DIR: "/tmp/ccache_dir"
10
-
CCACHE_NOHASHDIR: "1"# Debug info might contain a stale path if the build dir changes, but this is fine
4
+
### compiler options
5
+
HOST:
6
+
WRAPPER_CMD:
7
+
# Specific warnings can be disabled with -Wno-error=foo.
8
+
# -pedantic-errors is not equivalent to -Werror=pedantic and thus not implied by -Werror according to the GCC manual.
9
+
WERROR_CFLAGS: -Werror -pedantic-errors
10
+
MAKEFLAGS: -j4
11
+
BUILD: check
12
+
### secp256k1 config
13
+
ECMULTWINDOW: 15
14
+
ECMULTGENKB: 22
15
+
ASM: no
16
+
WIDEMUL: auto
17
+
WITH_VALGRIND: yes
18
+
EXTRAFLAGS:
19
+
### secp256k1 modules
20
+
EXPERIMENTAL: no
21
+
ECDH: no
22
+
RECOVERY: no
23
+
SCHNORRSIG: no
24
+
ELLSWIFT: no
25
+
### test options
26
+
SECP256K1_TEST_ITERS:
27
+
BENCH: yes
28
+
SECP256K1_BENCH_ITERS: 2
29
+
CTIMETESTS: yes
30
+
# Compile and run the tests
31
+
EXAMPLES: yes
11
32
33
+
# A self-hosted machine(s) can be used via Cirrus CI. It can be configured with
34
+
# multiple users to run tasks in parallel. No sudo permission is required.
35
+
#
12
36
# https://cirrus-ci.org/guide/persistent-workers/
13
37
#
14
-
# It is possible to select a specific persistent worker by label. Refer to the
38
+
# Generally, a persistent worker must run Ubuntu 23.04+ or Debian 12+.
39
+
#
40
+
# The following specific types should exist, with the following requirements:
41
+
# - small: For an x86_64 machine, recommended to have 2 CPUs and 8 GB of memory.
42
+
# - medium: For an x86_64 machine, recommended to have 4 CPUs and 16 GB of memory.
43
+
# - arm64: For an aarch64 machine, recommended to have 2 CPUs and 8 GB of memory.
44
+
#
45
+
# CI jobs for the latter configuration can be run on x86_64 hardware
46
+
# by installing qemu-user-static, which works out of the box with
47
+
# podman or docker. Background: https://stackoverflow.com/a/72890225/313633
48
+
#
49
+
# The above machine types are matched to each task by their label. Refer to the
15
50
# Cirrus CI docs for more details.
16
51
#
17
-
# Generally, a persistent worker must run Ubuntu 23.04+ or Debian 12+.
18
-
# Specifically,
52
+
# When a contributor maintains a fork of the repo, any pull request they make
53
+
# to their own fork, or to the main repository, will trigger two CI runs:
54
+
# one for the branch push and one for the pull request.
55
+
# This can be avoided by setting SKIP_BRANCH_PUSH=true as a custom env variable
# RESTART_CI_DOCKER_BEFORE_RUN=1 screen cirrus worker run --labels type=todo_fill_in_type --token todo_fill_in_token
42
87
# ```
43
-
#
44
-
# The following specific types should exist, with the following requirements:
45
-
# - small: For an x86_64 machine, recommended to have 2 CPUs and 8 GB of memory.
46
-
# - medium: For an x86_64 machine, recommended to have 4 CPUs and 16 GB of memory.
47
-
# - noble: For a machine running the Linux kernel shipped with exaclty Ubuntu Noble 24.04. The machine is recommended to have 4 CPUs and 16 GB of memory.
48
-
# - arm64: For an aarch64 machine, recommended to have 2 CPUs and 8 GB of memory.
skip: $CIRRUS_REPO_FULL_NAME == "BGL-core/gui" && $CIRRUS_PR == "" # No need to run on the read-only mirror, unless it is a PR. https://cirrus-ci.org/guide/writing-tasks/#conditional-task-execution
91
+
# Allow forks to specify SKIP_BRANCH_PUSH=true and skip CI runs when a branch is pushed,
0 commit comments