summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
diff options
context:
space:
mode:
authoremilylange <git@emilylange.de>2024-04-10 17:52:51 +0200
committeremilylange <git@emilylange.de>2024-04-10 22:09:56 +0200
commit117a1a6a2cbfec20f16c997f48b0abd277477429 (patch)
tree9a47c39fedbdc54d8e082e95bfe53175ae784815 /pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch
parent2cd2419baffeb8360c81f1c571d2a1340ff651d4 (diff)
nixos/tests/forgejo: test Forgejo Runner registration and workflow
Instead of only testing the runner registration, which doesn't tell us all that much, we now test a (very simple) but actual workflow directly runner on the host (type `:host`). For this to work, we cache the official `actions/checkout` action from GitHub as FOD and essentially mirror one version of it to Forgejo as part of the test. Since Forgejo does not yet provide an API endpoint for the workflow status (whether a workflow is running, failed or successful), we have to resort to parsing html for now. It has some rather over the top poll logic, but I feel like will work for quite some time without issues going unnoticed or whatever (TM). This is essentially a response to a bug I found in `services.gitea-actions-runner`, because we had no way to test that module besides the runner registration (which, again, doesn't really tell us all that much).
Diffstat (limited to 'pkgs/development/python-modules/termplotlib/gnuplot-subprocess.patch')
0 files changed, 0 insertions, 0 deletions