Rebuild catalina images

[real-or-random]

I know the catalina images are deprecated but could you nevertheless trigger a rebuild?

The brew in these images is 12 months old and uses an old upstream URL that makes installing packages fallback to building from source, which takes forever (and fails if the source is on gnu.org, which is down currently -- but that's a different issue):
https://cirrus-ci.com/task/4557392686874624?logs=brew#L1

[real-or-random]

Just checking if you have seen this.

[fkorotkov]

Seems I missed it. Thanks for pinging!

Is it so necessary for you to support Catalina? It's pretty painful for us to rebuild old images and distribute them. monterey-base won't work for you?

[real-or-random]

At the moment we're sticking to Catalina because it's the most recent version supported by Valgrind (or actually this fork https://github.com/LouisBrunner/valgrind-macos -- upstream Valgrind's support for macOS is hopelessly outdated).

If it's a non-trivial amount of work to update, then no need to do it. We can just run brew update.

[andreineculau]

@real-or-random from experience on another CI, try to uninstall brew completely and reinstall it back e.g.

/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/uninstall.sh)"
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

[real-or-random]

Thanks. Are you saying this is better than brew update? Can you explain why?

[andreineculau]

Better is in the eye of the beholder. My metrics showed better performance, lower I/O. But my scenario involves a high number (almost 100) of "brew install" calls, with hundreds of dependencies.

…

-- http://andreineculau.com

On 30 Jan 2022, at 17:27, Tim Ruffing ***@***.***> wrote:  Thanks. Are you saying this is better than brew update? Can you explain why? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

[real-or-random]

Not exactly related but we often see this error here (typically at least one once in a build):
https://github.com/ElementsProject/secp256k1-zkp/runs/5006963149

So it seems this an error returned by the GitHub server. But of course it could be related to us using a too old Git locally... If anyone has a clue, please tell me.

I don't now, I may try your suggestion @andreineculau, maybe it works around this problem as well...

[andreineculau]

Indeed, I believe my suggestion would not hit this particular issue, which I think it's due to the garbage collection getting triggered, and since the local repo is too old... Though my suggestion *could* take longer, it does end up with a cleaner env, and less headaches. If you don't want to remove homebrew and start fresh, I don't know if you tried any of these: * https://discourse-mediawiki.wmflabs.org/t/cant-pull-mediawiki-core/389/3 * https://stackoverflow.com/a/7363357/465684 * or maybe simply turn off gc https://stackoverflow.com/a/28092576/465684

…

On Fri, Feb 4, 2022 at 10:41 AM Tim Ruffing ***@***.***> wrote: Not exactly related but we often see this error here (typically at least one once in a build): https://github.com/ElementsProject/secp256k1-zkp/runs/5006963149 So it seems this an error returned by the GitHub server. But of course it could be related to us using a too old Git locally... If anyone has a clue, please tell me. I don't now, I may try your suggestion @andreineculau <https://github.com/andreineculau>, maybe it works around this problem as well... — Reply to this email directly, view it on GitHub <#41 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFM4QK6CBSHXYKXOMZFOCLUZONNTANCNFSM5KOHJ56A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Y Software AB http://ysoftware.se Andrei Neculau http://andreineculau.com

[real-or-random]

I don't think so. The problem is on the server ("remote") but I can't turn off gc on the server.