ci: Force `ccache` package version for MSVC build #25929

pull hebasto wants to merge 2 commits into bitcoin:master from hebasto:220825-msvc changing 1 files +3 −3

hebasto commented at 7:23 AM on August 25, 2022: member

The recent update of the ccache package from 4.6.1 to 4.6.2 broke our MSVC CI build.

This PR forces the working version 4.6.1.
ci: Force `ccache` package version for MSVC build
The ccache 4.6.2 is broken.
905f6142e7
DrahtBot added the label Tests on Aug 25, 2022
fanquake commented at 7:45 AM on August 25, 2022: member

What about the point update actually broke things? Has it been reported upstream?
hebasto commented at 7:52 AM on August 25, 2022: member

What about the point update actually broke things? Has it been reported upstream?

Checking the https://github.com/ccache/ccache repository...

cc @sipsorcery
sipsorcery commented at 7:54 AM on August 25, 2022: member

ACK 905f6142e7665c24e666bbe34bec19d422efdafa.
hebasto commented at 8:42 AM on August 25, 2022: member

What about the point update actually broke things? Has it been reported upstream?

Checking the https://github.com/ccache/ccache repository...

git log --oneline v4.6.1..v4.6.2 shows nothing suspicious...

hebasto commented at 9:28 AM on August 25, 2022: member

As all caches (Qt, vcpkg tools, vcpkg binary, ccache) have been invalidated, a couple of minutes lacks to finish a build before timeout.

Do you mind increasing CPU number:

--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -97,8 +97,8 @@ task:
   name: "Win64 native [vs2022]"
   << : *FILTER_TEMPLATE
   windows_container:
-    cpu: 4
-    memory: 8G
+    cpu: 6
+    memory: 12G
     image: cirrusci/windowsservercore:visualstudio2022
   timeout_in: 120m
   env:

ci: Increase `windows_container` resources

Required to fit timeout when all build caches are invalidated.

cda62657e9

MarcoFalke merged this on Aug 25, 2022
MarcoFalke closed this on Aug 25, 2022
hebasto deleted the branch on Aug 25, 2022
sidhujag referenced this in commit db02530150 on Aug 25, 2022
hebasto commented at 10:35 PM on August 28, 2022: member

What about the point update actually broke things? Has it been reported upstream?

It has been fixed in v4.6.3 (tested in my Cirrus account).

This PR forces the working version 4.6.1.

Nevertheless, I'd prefer to stick to well-known v4.6.1 for now.
fanquake referenced this in commit 3b85e17b49 on Oct 14, 2022
bitcoin locked this on Aug 28, 2023

Contributors

Labels