Skip to content

Regression fixes and prepare 0.2.0#121

Open
refi64 wants to merge 9 commits into
mainfrom
wip/refi64/prep-0.2.0
Open

Regression fixes and prepare 0.2.0#121
refi64 wants to merge 9 commits into
mainfrom
wip/refi64/prep-0.2.0

Conversation

@refi64

@refi64 refi64 commented Jun 19, 2026

Copy link
Copy Markdown
Collaborator

Contains the gitlab-runner upgrade to work with newer GitLab, plus three regression fixes for the runner:

The latter two should now be caught via the test suite, and the first should be caught by the newly added, vaguely horrifying smoke test bash script.

refi64 added 4 commits June 19, 2026 14:46
Since our on_event was skipping the inner filter, the disabled bits
would stay set for the next event, which coincidentally could end up
being an event logged with `gitlab.output=true` directly. This seems
to not have come up in testing because the events that got accidentally
disabled were TRACE events that we didn't really care about anyway.

The tests are also modified to only enable TRACE-level logging when
OBO_TEST_TRACE is set, that way the tests are doing logging with a setup
more similar to the runner proper.
Since the CLI trace logs end up in the same place as the output logs, we
need a small hack to differentiate them in one test, but it's only
enabled when test tracing is enabled and thus shouldn't cause problems
elsewhere.
gitlab-runner 0.0.8+ adds support for artifact filtering, which we were
preparing for here...but the current syntax does not actually match
GitLab's own syntax and instead treats the patterns as globs for
individual files (not directories). Thus, we need to turn the results
directory name into a glob in order for them to actually be uploaded as
artifacts.
Otherwise, generated pipelines might end up with bad `artifacts` items
without it being caught during testing.
@refi64 refi64 force-pushed the wip/refi64/prep-0.2.0 branch from 36e5d02 to 3ee5231 Compare June 19, 2026 22:36
refi64 added 5 commits June 19, 2026 17:39
This contains a fix for infinite looping when downloading the logs when
reqwest uses HTTP/2.
This isn't a complete integration test or similar, but it can run a
simple "pipeline" with either the CLI or the runner and then grab and
display the resulting artifacts.
This makes it easier to bump the version for the CLI + runner and
reduces duplication.
@refi64 refi64 force-pushed the wip/refi64/prep-0.2.0 branch from 3ee5231 to 6f6123e Compare June 19, 2026 22:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant