Update openshift-tests-extension to latest#3250
Conversation
Update from v0.0.0-20260127 to v0.0.0-20260612. This pulls in the ForwardingOutputInterceptor fix from openshift/onsi-ginkgo#23 which ensures stdout/stderr from test code is captured into CapturedStdOutErr instead of leaking to the process stdout. This fixes false test failures caused by test output contaminating JSON results in parallel execution. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
WalkthroughThe ChangesDependency Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: anuragthehatter The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/retest |
|
@anuragthehatter: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
Summary
openshift-tests-extensionfromv0.0.0-20260127tov0.0.0-20260612openshift/onsi-ginkgowith theForwardingOutputInterceptorfix (TRT-2539: Capture stdout/stderr in RunSpec while forwarding output in real-time onsi-ginkgo#23)Root cause
RunSpecinopenshift/onsi-ginkgo'ssuite_patch.gopreviously usedNoopOutputInterceptor, so any directos.Stdoutwrites from test code (kube e2e framework STEP logs,exutil.CLIoutput) leaked to process stdout alongside the JSON result. The harness then failed to parse the mixed output as JSON, reporting passing tests as failures withDeserialization Error: invalid character 'S' looking for beginning of value.Test plan
go buildpasses🤖 Generated with Claude Code
Summary by CodeRabbit