git no longer works in FreeBSD 13

[infrastation]

Expected Behavior

FreeBSD 13 used to work as expected in Cirrus CI configuration for tcpdump until August 7 (the last successful run).

Real Behavior

On August 7 FreeBSD 13 stopped working because git installed with pkg started to have linking problems (the first unsuccessful run):

ld-elf.so.1: /usr/local/bin/git: Undefined symbol "regcomp@FBSD_1.6"

FreeBSD 11 and 12 continue to work as before. Other repositories that do not install git with pkg continue to work with FreeBSD 13.

[fkorotkov]

I'm not sure what's going on here since we don't maintain the images. Members of FreeBSD community do create and maintain these images on GCP. Quick Googling didn't help much with the issue.

@emaste, maybe you saw some similar reports?

[emaste]

Sigh, sorry folks - I'll look into it.

[infrastation]

Thank you. In case it helps, it is not a goal to test the latest snapshots of FreeBSD, so if it would be simpler to switch this Cirrus configuration to release images, that would be fine. The reason why it uses the snapshots is because these were the only working image names I could quickly figure out during the setup without becoming a customer of GCP.

[emaste]

What's happening here is that the package builds for 13-CURRENT and the base image snapshots aren't coupled, and the packages were actually built for a slightly newer base system version than the snapshot. This issue should be gone with the latest base system snapshot - I'd greatly appreciate knowing if this is the case, or if it's still broken.

We're discussing short term workarounds in case this happens again, as well as build system changes to ensure it doesn't.

[infrastation]

Re-running the Cirrus CI task right now still results in the same error, for example: https://cirrus-ci.com/task/5676629479391232
I am not sure which version of freebsd-13-0-snap it is using though. If you want to get specific diagnostic output from within the task, just let me know which commands.

[fkorotkov]

Seems working without pkg update -f but still takes very long time and has weird logs. See https://cirrus-ci.com/task/4778135017226240?command=install#L3

[infrastation]

Commit the-tcpdump-group/tcpdump@96c4db3 had added pkg update -f to work around the failing FreeBSD 11 task in February 2020. The FreeBSD 11 issue was as follows:

pkg install -qy git autoconf
pkg: cached package git-2.25.0: size mismatch, fetching from remote
pkg: cached package git-2.25.0: size mismatch, cannot continue

Exit status: 3

(The Cirrus CI task is this, but for some reason it no longer displays the log, but a copy had survived elsewhere.)

Would it be more appropriate to switch to some stable images or maybe drop FreeBSD 11 and the workaround from the matrix?

[infrastation]

On a related note, I was going to declare the FreeBSD 13 task in .cirrus.yml OK to fail until there's a proper solution in place, and from the documentation it seems the condition in allow_failures can only use variables, which cannot tell which element of the expanded matrix the current task is for. In other words, this is not possible. Is this correct?

[fkorotkov]

You can do something like:

  freebsd_instance:
    image: freebsd-$FAMILY
  allow_failures: $FAMILY == "13-0-snap"
  env:
    matrix:
      - FAMILY: 11-3-snap
      - FAMILY: 12-1-snap
      - FAMILY: 13-0-snap

[infrastation]

That worked, thank you. Now FreeBSD 13 task continues to run, but does not fail the Cirrus CI status anymore. If you work a proper permanent solution out, please post it here. Leaving the issue open.

[arrowd]

That's right, it is a FreeBSD problem and has nothing to do with Cirrus CI. CURRENT is a bleeding edge branch and breakages such this happen. I'm sure it will be fixed once the image get upgraded to the new snapshot.

[infrastation]

Alright, this is not a problem of Cirrus CI. Maybe not even a problem of FreeBSD, but the way Google delivers snapshots of it. tcpdump now no longer uses the 11.3-CURRENT workaround, so 13.0-CURRENT is working again (see the linked commit). Thanks everyone for your input, closing the request.