aboutsummaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2024-10-07ci: Install missing nproc in macos taskMarcoFalke
This avoids special-casing macos
2024-10-07ci: Add missing -DWERROR=ON to test-each-commitMarcoFalke
2024-09-30ci: Remove natpmp build option and libnatpmp dependencylaanwj
2024-09-17ci: Use `ninja` to build in macOS native CI jobHennadii Stepanov
2024-09-17Merge bitcoin/bitcoin#30902: Remove Autotools packages from CI (and depends doc)merge-script
7a8a6a06676dcb4066cc81a4e6872281a09bb00d doc: Fix comment in `contrib/devtools/check-deps.sh` script (Hennadii Stepanov) 712d105e0935d31915c067bb90c54b71f6c5f4f5 depends, doc: Do not install Autotools packages (Hennadii Stepanov) b786449e663b6534abd0239e38122b9d082b90d8 ci: Do not install Autotools packages (Hennadii Stepanov) Pull request description: This PR is a follow-up to https://github.com/bitcoin/bitcoin/pull/30752 and addresses https://github.com/bitcoin/bitcoin/pull/30752#discussion_r1758594864. ACKs for top commit: kevkevinpal: ACK [7a8a6a0](https://github.com/bitcoin/bitcoin/pull/30902/commits/7a8a6a06676dcb4066cc81a4e6872281a09bb00d) Tree-SHA512: ac701b34ebf1621be355a5b576032d30a342a5667eff47d858587ac3c60011d77bd469e524d69dae90a932f14269227886e3d170a63a2e855b29ef4fa5b9e5a4
2024-09-17ci: Use macos-14 GHA imageMarcoFalke
2024-09-14ci: Do not install Autotools packagesHennadii Stepanov
2024-09-06ci: Add missed configuration options to "Win64 native" jobHennadii Stepanov
2024-09-03scripted-diff: fuzz: Rename fuzz_seed_corpus to fuzz_corporaMarcoFalke
-BEGIN VERIFY SCRIPT- ren() { sed -i "s:\<$1\>:$2:g" $( git grep -l "$1" ) ; } ren fuzz_seed_corpus fuzz_corpora ren FUZZ_SEED_CORPUS_DIR FUZZ_CORPORA_DIR -END VERIFY SCRIPT-
2024-08-30ci: Delete no longer needed workaroundHennadii Stepanov
It was necessary at some point during the development of the CMake staging branch.
2024-08-29ci: add libzmq3-dev to test-each-commit jobfanquake
2024-08-29ci: remove bsdmainutilsfanquake
2024-08-28ci: Re-add configs removed in cmake migrationMarcoFalke
2024-08-16ci: Migrate CI scripts to CMakeHennadii Stepanov
2024-08-05ci: Silent Homebrew's reinstall warningsHennadii Stepanov
2024-07-29ci: enable berkley db on test each commit jobMax Edwards
2024-06-25ci: test-each-commit merge base optionalSjors Provoost
The ci "test-each-commit" job fetches the PR branch being tested with a depth of (# of commits in PR + 2), and then tries to run tests on commits after the most recent merge commit. When a PR is opened against a bitcoin core branch, a merge commit is always guaranteed to exist within the fetch depth, because bitcoin core branches always point at merge commits. However, in fork repositories, pull requests can be opened based on other branches that don't contain recent merge commits, and this will currently cause git rev-list to fail with fatal: bad revision '^^@'. Work around this problem by not requiring a recent merge commit, and just testing on all fetched commits if a merge commit can't be found. Co-authored-by: Ryan Ofsky <ryan@ofsky.org>
2024-06-20ci: add option for running tests without volumeMax Edwards
DANGER_CI_ON_HOST_CACHE_FOLDERS if set will mount caches in directories on the host rather than in docker volumes. Supports saving and restoring caches on Github Actions.
2024-06-18ci: remove unused bcc variable from workflowMax Edwards
2024-06-17Merge bitcoin/bitcoin#30193: ci: move ASan job to GitHub Actions from Cirrus CIAva Chow
9eea51d9058ad638861aa4b94c1c6e71caeb8765 ci: move Asan / LSan / USDT job to Github Actions (Max Edwards) 4b527fa93b9763a33842069bc07446313cbf5e0f ci: add IPV6 network to ci container (Max Edwards) Pull request description: PR for moving the ASAN + LSAN + USDT + friends job to github actions from Cirrus. The motivation for this PR is that this task needs a full VM (or bare metal) to function, because of the tracepoints. It can not run in a container on an arbitrary Linux, because the outside machine must exactly match the specification of the distro used in the CI task config. This requires more maintenance for the persistent worker, and I think moving to GHA will reduce the maintenance burden, or at least make it possible for anyone to work on. Also, it makes it easier to run the task on forks (bitcoin-inquisition, bitcoin-knots, devel forks, ...) without having to set-up a real machine. ACKs for top commit: maflcko: review ACK 9eea51d9058ad638861aa4b94c1c6e71caeb8765 achow101: ACK 9eea51d9058ad638861aa4b94c1c6e71caeb8765 hebasto: ACK 9eea51d9058ad638861aa4b94c1c6e71caeb8765. Tree-SHA512: 1111c1c9e3a11e725dff1344643fff3c91fb9b4d7c1cc9a7d507a8f146f5223316a00272030b41ae37ecb59d044f2e90e1cd907450049b25f094f0b60643d4c7
2024-06-12ci: move Asan / LSan / USDT job to Github ActionsMax Edwards
Moving it from Cirrus CI so it can be easier to maintain and used by forks
2024-06-07ci: Use relative paths in `win64-native` CI job consistentlyHennadii Stepanov
This change improves readability. Also the `Tee-Object` cmdlet is used when appropriate.
2024-06-07ci: Remove no longer needed workaround for GHA Windows imagesHennadii Stepanov
GHA Windows images previously had multiple VC Build Tools installed, which required specifying the `VCPKG_PLATFORM_TOOLSET_VERSION` explicitly to avoid linker errors. This issue has been resolved as per https://github.com/actions/runner-images/issues/9701.
2024-05-15ci: Roll test-each-commit UbuntuMarcoFalke
2024-05-15ci: Remove clang version pin in test-each-commitMarcoFalke
2024-04-18ci, msvc: Add "Run fuzz binaries" stepHennadii Stepanov
2024-04-18ci, msvc: Add "Clone fuzz corpus" stepHennadii Stepanov
2024-03-29ci: Pull in qtbase5-dev instead of seperate low-level librarieslaanwj
Fix CI build for t64 migration.
2024-03-12Merge bitcoin/bitcoin#29620: ci: add print of powershell version to win64 jobfanquake
115c283516b8550485df752656e9b863be5903a1 ci: add print of powershell version to win64 job (Max Edwards) Pull request description: Extraction of just printing powershell version from closed PR: https://github.com/bitcoin/bitcoin/pull/29581 See https://github.com/bitcoin/bitcoin/pull/29581#issuecomment-1984212990 for the cause of a CI failure which was a powershell update. This PR will make it easier to notice in the future that PS has changed. ACKs for top commit: hebasto: ACK 115c283516b8550485df752656e9b863be5903a1. We still use PowerShell in some steps of the "Win64 native" CI job. Tree-SHA512: 4c7ba9df4f0a98491120326f05e877a995f43a387fe9bbd193549b32f5a4488f85f83e472c9277db457110a7deda04f08832fe6e8129aff4b0b7278be23d4e35
2024-03-10ci: Add workaround for Homebrew's python link errorHennadii Stepanov
Promoting Homebrew's python@3.12 to the default python3 breaks symbolic links on macOS x86_64. This change adds a workaround for that issue. Also see: https://github.com/actions/runner-images/issues/9471 etc.
2024-03-06ci: add print of powershell version to win64 jobMax Edwards
2024-03-02ci: Fix functional tests step for pull requests in Windows GHA jobHennadii Stepanov
This functionality has been broken since the Windows runner image version `20240128.1.0`.
2024-02-28ci: print python version on win64 native jobMax Edwards
2024-01-25ci: Update cache actionHennadii Stepanov
This change fixes deprecation warnings for Node.js 16 actions in the GHA CI. See: - https://github.com/marketplace/actions/cache - https://github.com/actions/cache/releases/tag/v4.0.0
2024-01-08ci: Switch native macOS CI job to Xcode 15.0Hennadii Stepanov
2023-12-14ci: Set `HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK` to avoid failuresHennadii Stepanov
Homebrew attempts to check for outdated dependents or those with broken linkage. Such behavior might lead to failures when Homebrew updates them on old macOS images. This change prevents such behavior.
2023-12-12Revert "ci: Only run functional tests on windows in master"Hennadii Stepanov
This reverts commit aba4a5887b44bf7cbee9ea0a8e02bb92c1b4147b.
2023-12-07build: Require C++20 compilerMarcoFalke
2023-11-24Revert "ci: Avoid toolset ambiguity that MSVC can't handle"Hennadii Stepanov
This reverts commit 91d5bd8ac9a28725c735f8e6900bc85673bb190a.
2023-11-24ci: Set MSVC toolset version explicitlyHennadii Stepanov
This change avoids toolset incompatibilities that cause linker errors.
2023-11-24ci: Run vcpkg with path prefixHennadii Stepanov
The GHA VS installation includes its own vcpkg package manager, which is available since VS 17.6. This change avoids any ambiguity about which copy of vcpkg we run.
2023-11-22ci: Switch from `apt` to `apt-get`Hennadii Stepanov
2023-11-22ci: Update apt cacheHennadii Stepanov
2023-11-17ci: Avoid toolset ambiguity that MSVC can't handleHennadii Stepanov
This change is required to work with the new windows-2022 image version 20231115 properly.
2023-11-08ci: remove note re M1 usagefanquake
M1 is now available in GitHub CI, but we don't currently have a plan to use it, so remove the comment.
2023-11-05ci: Drop no longer needed "Fix Visual Studio installation" stepHennadii Stepanov
The underlying issue has been fixed in the image version 20231029.
2023-11-01build: Update `qt` package up to 5.15.11Hennadii Stepanov
2023-10-09Merge bitcoin/bitcoin#28573: github actions: Fix test-one-commit when parent ↵fanquake
of head is merge commit 88c8e3a0e4d6bee015a348536c6e12a2c7835896 github actions: Fix test-one-commit when parent of head is merge commit (Ryan Ofsky) Pull request description: Instead of figuring out the commit *after* the last merge and rebasing on that with a ~1 suffix, just figure out the last merge commit directly and rebase on it. This way, if HEAD happens to be a merge commit, the rebase just succeeds immediately without blank variables or errors. Explanation of the problem from https://github.com/bitcoin/bitcoin/pull/28497#issuecomment-1743430631: > The problem is that the PR only contains a one commit after the last merge, so the job _should_ be skipped, but the `pull_request.commits != 1` check is not smart enough to skip it because the PR is based on another PR and has merge ancestor commits. So specifically what happens is that after HEAD~ is checked out, the new HEAD is a merge commit, so the range `$(git log --merges -1 --format=%H)..HEAD` is equivalent to HEAD..HEAD, which is empty, so the `COMMIT_AFTER_LAST_MERGE` variable is empty and the rebase command fails. Note: In the current version of this PR, the "test each commit" job is skipped, because this PR only contains a single commit. But I manually verified the code works in earlier versions of the PR that included dummy commits. ACKs for top commit: maflcko: lgtmrecr ACK 88c8e3a0e4d6bee015a348536c6e12a2c7835896 RandyMcMillan: utACK 88c8e3a Tree-SHA512: a6865b5c8b96eb0b622b3255971a3cf050dd0f5a356cdfcf7f0cbb659e4a363612e8e62b3ae4fd6b5d9a40bc29176891bc4690659b026c5ef8feea25c8e263cc
2023-10-05github actions: Fix test-one-commit when parent of head is merge commitRyan Ofsky
Instead of figuring out the commit *after* the last merge and rebasing on that with a ~1 suffix, just figure out the last merge commit directly and rebase on it. This way, if HEAD happens to be a merge commit, the rebase just succeeds immediately without blank variables or errors. From https://github.com/bitcoin/bitcoin/pull/28497#issuecomment-1743430631: The problem is that the PR only contains a one commit after the last merge, so the job _should_ be skipped, but the `pull_request.commits != 1` check is not smart enough to skip it because the PR is based on another PR and has merge ancestor commits. So specifically what happens is that after HEAD~ is checked out, the new HEAD is a merge commit, so the range `$(git log --merges -1 --format=%H)..HEAD` is equivalent to HEAD..HEAD, which is empty, so the `COMMIT_AFTER_LAST_MERGE` variable is empty and the rebase command fails.
2023-10-04Merge bitcoin/bitcoin#28561: build: Update `qt` package up to 5.15.10fanquake
6988a2f097e9af50e1b4222550b2593bfc5685ea build: Update qt package up to 5.15.10 (Hennadii Stepanov) Pull request description: The Qt 5.15.10 contains at least three important for us fixes: - https://github.com/qt/qtbase/commit/8bb90ab760310c9bc82b6ecbe068532fcb4e7822, which allows us to drop the [`dont_hardcode_x86_64.patch`](https://github.com/bitcoin/bitcoin/blob/fd8ab08558ccfb62f2d0a64d2d0d4dcefba977bc/depends/patches/qt/dont_hardcode_x86_64.patch) - https://github.com/qt/qtbase/commit/8467beddb7239cc213ae13900fa30e3d26df5e78, which allows us to drop the [`fix_montery_include.patch`](https://github.com/bitcoin/bitcoin/blob/fd8ab08558ccfb62f2d0a64d2d0d4dcefba977bc/depends/patches/qt/fix_montery_include.patch) - https://github.com/qt/qtbase/commit/df08a21fa4e7139d46ec68bcf264c922789c4f3a, which addresses https://github.com/bitcoin/bitcoin/pull/28349#issuecomment-1743519614 ACKs for top commit: fanquake: ACK 6988a2f097e9af50e1b4222550b2593bfc5685ea. Tree-SHA512: 838c44cf0d7508714f35887bb1f0983e59d96764f08f467bbd03d102d7152e797daeedc178afb03141115cc3be623e4ef7c4c4c65c0a8d1f0bb9702c9a6f8fc6
generated by cgit v1.2.3 (git 2.26.2) at 2025-02-17 15:00:24 +0000