Skip to content

fix: bump semconv from v1.39.0 to v1.40.0 in tracing.go - #1690

Open
ci-operator wants to merge 1 commit into
konflux-ci:mainfrom
ci-operator:fix-tracing-semconv-version
Open

fix: bump semconv from v1.39.0 to v1.40.0 in tracing.go#1690
ci-operator wants to merge 1 commit into
konflux-ci:mainfrom
ci-operator:fix-tracing-semconv-version

Conversation

@ci-operator

Copy link
Copy Markdown
Contributor

A grpc dependency bump transitively moved otel/sdk to v1.43.0, which
uses semconv v1.40.0 internally. The schema mismatch made
resource.Merge fall back to resource.Default(), reporting service.name
as unknown_service:manager instead of integration-service. Bumping the
pin to v1.40.0 fixes it.

Maintainers will complete the following section

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 27, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:36 PM UTC · Completed 5:42 PM UTC

Commit: 9ee3c25 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.50

@fullsend-ai-review

fullsend-ai-review Bot commented Aug 27, 2026

Copy link
Copy Markdown

Looks good to me

Previous run

Looks good to me

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added the ready-for-merge All reviewers approved — ready to merge label Aug 27, 2026
@ci-operator

Copy link
Copy Markdown
Contributor Author

/rerun

@14rcole

14rcole commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

/retest

@codecov-commenter

codecov-commenter commented Sep 1, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.94%. Comparing base (ef6599a) to head (93e8b9c).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1690      +/-   ##
==========================================
+ Coverage   69.02%   74.94%   +5.92%     
==========================================
  Files          74       74              
  Lines       10617    10617              
==========================================
+ Hits         7328     7957     +629     
+ Misses       2522     1912     -610     
+ Partials      767      748      -19     
Flag Coverage Δ
e2e-tests 38.07% <ø> (?)
unit-tests 69.00% <ø> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
pkg/tracing/tracing.go 89.53% <ø> (-3.49%) ⬇️

... and 37 files with indirect coverage changes


Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef6599a...93e8b9c. Read the comment docs.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@dirgim

dirgim commented Sep 3, 2026

Copy link
Copy Markdown
Member

Hi @ci-operator can you rebase on the latest main to resolve the issues with the CI?

Matches the schema version vendored otel/sdk uses internally, avoiding
a resource.Merge conflict.

Assisted-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Signed-off-by: Josiah England <jengland@redhat.com>
@ci-operator
ci-operator force-pushed the fix-tracing-semconv-version branch from 68e1e58 to 93e8b9c Compare September 3, 2026 17:43
@fullsend-ai-review

fullsend-ai-review Bot commented Sep 3, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 5:44 PM UTC · Completed 5:54 PM UTC

Commit: 9ee3c25 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $2.08

@fullsend-ai-review fullsend-ai-review Bot added the risk/low PR risk: low label Sep 3, 2026
@fullsend-ai-review

Copy link
Copy Markdown

Risk Assessment: low (1/5)

Details

Single-line semconv version bump in stable tracing module with zero churn, no protected paths, and no regression history.

@dirgim

dirgim commented Sep 4, 2026

Copy link
Copy Markdown
Member

/ok-to-test

@14rcole

14rcole commented Sep 4, 2026

Copy link
Copy Markdown
Collaborator

/retest

@konflux-ci-qe-bot

Copy link
Copy Markdown

Scenario: konflux-e2e
@ci-operator: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name Status Rerun command Build Log Test Log
konflux-e2e-f5h2p Failed /retest View Pipeline Log View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

  1. Install ORAS (see the ORAS installation guide).
  2. Download artifacts with the following commands:
mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/integration-service:konflux-e2e-f5h2p

Test results analysis

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

➡️ [failed] [It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when a new Component with specified custom branch is created should lead to build PipelineRun finishing successfully [integration-service, github-status-reporting, custom-branch]

Click to view logs

build pipelinerun fails for NameSpace/Application/Component stat-rep-xppu/integ-app-77i0/test-component-pac-l339hm with logs: Pipelinerun 'test-component-pac-l339hm-on-pull-request-qpqv8' didn't succeed

Expected success, but got an error:
    <*errors.errorString | 0xc000e0c930>: 
    Pipelinerun 'test-component-pac-l339hm-on-pull-request-qpqv8' didn't succeed
    
    {
        s: "Pipelinerun 'test-component-pac-l339hm-on-pull-request-qpqv8' didn't succeed\n",
    }

➡️ [failed] [It] [integration-service-suite Forgejo Status Reporting of Integration tests] Forgejo with status reporting of Integration tests in the associated merge request when a new Component with specified custom branch is created triggers a Build PipelineRun [integration-service, forgejo-status-reporting, custom-branch]

Click to view logs

Unexpected error:
    <*fmt.wrapError | 0xc000d13ca0>: 
    fork of konflux-qe/konflux-test-integration to konflux-qe/konflux-test-integration-4gg7bp already exists but failed to fetch: The target couldn't be found.
    {
        msg: "fork of konflux-qe/konflux-test-integration to konflux-qe/konflux-test-integration-4gg7bp already exists but failed to fetch: The target couldn't be found.",
        err: <*errors.errorString | 0xc000c3aa50>{
            s: "The target couldn't be found.",
        },
    }
occurred

➡️ [failed] [It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when we start creation of a new Component B should lead to build PipelineRun finishing successfully [integration-service, group-snapshot-creation]

Click to view logs

Expected success, but got an error:
    <*errors.errorString | 0xc00116a140>: 
    unable to retrigger pipelinerun for component group-5wgy:python-component-8ovj89: timed out waiting for new PipelineRun to appear after retriggering it for component group-5wgy:python-component-8ovj89
    {
        s: "unable to retrigger pipelinerun for component group-5wgy:python-component-8ovj89: timed out waiting for new PipelineRun to appear after retriggering it for component group-5wgy:python-component-8ovj89",
    }

➡️ [failed] [It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if the finalizer was removed from all of the related Integration pipelineRuns [integration-service]

Click to view logs

Expected success, but got an error:
    <*errors.errorString | 0xc0011673c0>: 
    error occurred while waiting for Integration PLR (associated with IntegrationTestScenario: integration-test-mcid) to NOT have the finalizer. Error: context deadline exceeded
    {
        s: "error occurred while waiting for Integration PLR (associated with IntegrationTestScenario: integration-test-mcid) to NOT have the finalizer. Error: context deadline exceeded",
    }

OCI Artifact Browser URL

View in Artifact Browser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge All reviewers approved — ready to merge risk/low PR risk: low size: XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants