Issues importing GCC 7.2.0 tarball
by Sam Thursfield
Hi all
I got stuck in a timesink today trying to update our gcc-tarball repo.
I don't have time to fix these issues but I will write them up here
for posterity.
Firstly, the GCC 7.2 tarball from https://ftp.gnu.org/gnu/gcc/gcc-7.2.0/
doesn't import correctly with Lorry's `lorry.tar-importer` script, nor
with the `contrib/fast-import/import-tars.perl` script from Git that it
is based on.
The script fails with an error like this:
fatal: Unsupported command: // any later version.
fast-import: dumping crash report to fast_import_crash_10201
The exact message varies, but the issue seems to be that it's sending
source code as `git fast-import` commands, causing `git fast-import` to
raise an error.
GCC publish checksums for their release tarballs and I have verified
that the file didn't get corrupted during transmission. There `tar -t`
command doesn't report any issue with the tarball and `tar -x` can
successfully extract everything.
To add to the fun, Lorry fails to recognise that the import failed. I
have narrowed this down to what looks like a Python 2 bug. If I run the
tarball import command in my shell or using subprocess.Popen from Python
3, I get a non-zero exit code. However if I run it using
subprocess.Popen from Python 2, I get a returncode of 0.
I don't have time to dig further into either of these problems, so
instead I've manually pushed a gcc-7.2.0 tag to our delta/gcc-tarball
repo.
Sam
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575
5 years
GitLab CI runners outage
by Sam Thursfield
Hi,
Codethink provides some GitLab CI runners which are used by the Baserock
and BuildStream projects.
These recently broke; the symptom was GitLab CI jobs failing with this
error[1]:
Running with gitlab-runner 10.1.0 (c1ecf97f)
on baserock-manager-runner2 (f45ec36a)
ERROR: Preparation failed: exit status 1
Will be retried in 3s ...
ERROR: Preparation failed: exit status 1
Will be retried in 3s ...
ERROR: Preparation failed: exit status 1
Will be retried in 3s ...
ERROR: Job failed (system failure): exit status 1
I diagnosed the issue by running `journalctl --follow` in the manager
VM, then retrying a job. Amongst the noise was this line:
Dec 14 12:01:06 ubuntu-1gb-lon1-01 gitlab-runner[1478]:
time="2017-12-14T12:01:06Z" level=error msg="Error creating machine:
Error in driver during machine creation: POST
https://api.digitalocean.com/v2/droplets: 422 You specified an invalid
image for Droplet creation." driver=digitalocean
name=runner-f45ec36a-machine-1513252861-90d58fd0-baserock operation=create
The issue is that we were trying to boot the machine with the
fedora-25-x64 image, but Fedora 25 recently hit end-of-life so
DigitalOcean have presumably deleted it.
The fix is to edit /etc/gitlab-runner/config.toml and update the
runners.machine.MachineOptions setting to boot the fedora-27-x64 image
instead -- our GitLab CI pipelines seem to be working again now.
Presumably we will need to do the same thing again in just under a
year's time :-)
Sam
[1]. such as https://gitlab.com/BuildStream/buildstream/-/jobs/44538627
--
Sam Thursfield, Codethink Ltd.
Office telephone: +44 161 236 5575
5 years, 5 months