pocmatos
2020-5-4 05:43:26

So our jobs have been quite flaky. We still have a problem with portlib which we have a bug for but a lot of the times it’s a github runners problem. Since this is installed/updated automatically in the vms from github we have no control over it.


pocmatos
2020-5-4 05:43:31

Here’s the last one:https://github.com/racket/racket/actions/runs/94744519


pocmatos
2020-5-4 05:43:57

The error messages:


pocmatos
2020-5-4 05:44:02

nodename nor servname provided, or not known


pocmatos
2020-5-4 05:44:17

and Exit code 1 returned from process: file name '/Users/runner/runners/2.169.1/bin/Runner.PluginHost', arguments 'action "GitHub.Runner.Plugins.Artifact.PublishArtifact, Runner.Plugins"'.


pocmatos
2020-5-4 05:44:27

are definitely annoying to say the least.


pocmatos
2020-5-4 05:44:53

or here:



pocmatos
2020-5-4 05:45:03

The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.


pocmatos
2020-5-4 05:46:45

Apart from github we have problems of our own like, jobs are failing on branches like on v7.7:



pocmatos
2020-5-4 05:46:57

Invalid pattern '../racketcgc-ubuntu-18.04-cify-x64_git12c2bff87d8e42aac9503a23e68503a9744ccc99.tar.bz2'. Relative pathing '.' and '..' is not allowed.


pocmatos
2020-5-4 05:47:15

I haven’t looked closer but my first thought is that the pattern should be the same in master.


pocmatos
2020-5-4 05:47:21

Why doesn’t it fail there?!?!?