Does this CI error ring any bells? <https://github...
# development
h
Copy code
/home/runner/work/pants/pants/src/python/pants/bin/native_client: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/runner/work/pants/pants/src/python/pants/bin/native_client)
/home/runner/work/pants/pants/src/python/pants/bin/native_client: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/runner/work/pants/pants/src/python/pants/bin/native_client)
/home/runner/work/pants/pants/src/python/pants/bin/native_client: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/runner/work/pants/pants/src/python/pants/bin/native_client)
w
Not this exact one, but libc stuff has popped up in the past
I thought it either had to do with one of our libs (protobuf, or something else that builds C-bound libraries), or our version of ubuntu
Oh wait a sec, that happens when doing a pip install? We've had like 30 instances of those over the past couple years
Orrr just after? I can never remember if the python code is done there, or if there is some follow-on work
Silly question, does the pants-cache take the OS version into account before restoring?
h
Nuking the relevant github actions cache entries and rerunning seems to sort this out
Actually, that was premature, let’s see how this run pans out
w
There were like 4 root causes for a glibc error, the latest being Node20 I think? So, I don't know if that could even be related?
h
OK, yep, that sorted it out