fix(lint): resolve golangci-lint errors in testing context

[alex-cobas]

Changes

Since Go 1.24, the golangci-lint linter usetesing reports errors when context.Background() or context.TODO() are used in tests. This commit updates the codebase to use t.Context() as recommended by Go 1.24 release documentation.

Refactor some TestRealWaiter* functions to send errors through a chan error instead of calling t.Errorf inside goroutines. This ensures that all logging and test assertions occur in the main test thread to avoid panics caused by logging after the test has completed.

Fixes #8805

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
• Has Tests included if any functionality added or changed
• pre-commit Passed
• Follows the commit message standard
• Meets the Tekton contributor standards (including functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: alex-cobas (bf5bd42)

[alex-cobas]

/kind misc

[waveywaves]

/ok-to-test

[waveywaves]

@alex-cobas please sign the CLA when you get the chance

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
cmd/entrypoint/runner.go	86.2%	84.5%	-1.7

[waveywaves]

/ok-to-test

[alex-cobas]

/retest

[alex-cobas]

@waveywaves what’s the correct way to initiate the GitHub Actions checks if they haven’t started automatically?

[AlanGreene]

A maintainer of this repo will need to approve the GitHub Actions workflows before they run.
The /ok-to-test only applies to the Prow-based checks, @waveywaves

[waveywaves]

/retest

[alex-cobas]

@waveywaves the last run (https://github.com/tektoncd/pipeline/actions/runs/15400505687) didn’t show any failed Actions, and the /retest command doesn’t appear to trigger a new run 🤷‍♂️

[alex-cobas]

/test all

[tekton-robot]

@alex-cobas: No presubmit jobs available for tektoncd/pipeline@main

In response to this:

/test all

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alex-cobas]

@afrittoli @pritidesai @dibyom @jerop
Please, take a look when you get a chance. Thank you!

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[vdemeester]

/lgtm