Skip to content

Do not run binary size check on push to main #7096

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 4, 2025

Conversation

yurishkuro
Copy link
Member

@yurishkuro yurishkuro commented May 4, 2025

Which problem is this PR solving?

  • When previous PR Add filterprocessor #7094 was force-merged with binary size check failing (there's no way to override that check to succeed), the same check failed on main AND the steps to update the binary size cache did not run

Description of the changes

  • Change the check for size to not run when on the main branch

Testing

  • The check is expected to still fail for this PR and will have to be force-merged
  • But then the same check on main should succeed and update the cached value

Signed-off-by: Yuri Shkuro <[email protected]>
@yurishkuro yurishkuro added the changelog:ci Change related to continuous integration / testing label May 4, 2025
@yurishkuro yurishkuro requested a review from a team as a code owner May 4, 2025 03:25
@yurishkuro yurishkuro requested a review from pavolloffay May 4, 2025 03:25
@yurishkuro yurishkuro changed the title fix Do not run binary size check on push to main May 4, 2025
Copy link

codecov bot commented May 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.11%. Comparing base (673dbd1) to head (2de034c).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #7096   +/-   ##
=======================================
  Coverage   96.11%   96.11%           
=======================================
  Files         358      358           
  Lines       21585    21585           
=======================================
  Hits        20747    20747           
  Misses        631      631           
  Partials      207      207           
Flag Coverage Δ
badger_v1 9.91% <ø> (ø)
badger_v2 2.05% <ø> (ø)
cassandra-4.x-v1-manual 14.91% <ø> (ø)
cassandra-4.x-v2-auto 2.04% <ø> (ø)
cassandra-4.x-v2-manual 2.04% <ø> (ø)
cassandra-5.x-v1-manual 14.91% <ø> (ø)
cassandra-5.x-v2-auto 2.04% <ø> (ø)
cassandra-5.x-v2-manual 2.04% <ø> (ø)
elasticsearch-6.x-v1 20.17% <ø> (ø)
elasticsearch-7.x-v1 20.25% <ø> (ø)
elasticsearch-8.x-v1 20.43% <ø> (ø)
elasticsearch-8.x-v2 2.05% <ø> (ø)
grpc_v1 11.46% <ø> (ø)
grpc_v2 2.05% <ø> (ø)
kafka-3.x-v1 10.19% <ø> (ø)
kafka-3.x-v2 2.05% <ø> (ø)
memory_v2 2.05% <ø> (ø)
opensearch-1.x-v1 20.30% <ø> (ø)
opensearch-2.x-v1 20.30% <ø> (ø)
opensearch-2.x-v2 2.05% <ø> (ø)
query 2.05% <ø> (ø)
tailsampling-processor 0.55% <ø> (ø)
unittests 94.92% <ø> (ø)

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@yurishkuro yurishkuro merged commit 148d4ef into jaegertracing:main May 4, 2025
57 of 58 checks passed
@yurishkuro yurishkuro deleted the bin-size-on-main3 branch May 4, 2025 03:41
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
## Which problem is this PR solving?
- When previous PR jaegertracing#7094 was force-merged with binary size check failing
(there's no way to override that check to succeed), the same check
[failed](https://github.com/jaegertracing/jaeger/actions/runs/14816241094/job/41597074760)
on `main` AND the steps to update the binary size cache did not run

## Description of the changes
- Change the check for size to not run when on the main branch

## Testing
- The check is expected to still fail for this PR and will have to be
force-merged
- But then the same check on main should succeed and update the cached
value

Signed-off-by: Yuri Shkuro <[email protected]>
amilbcahat pushed a commit to amilbcahat/jaeger that referenced this pull request May 4, 2025
## Which problem is this PR solving?
- When previous PR jaegertracing#7094 was force-merged with binary size check failing
(there's no way to override that check to succeed), the same check
[failed](https://github.com/jaegertracing/jaeger/actions/runs/14816241094/job/41597074760)
on `main` AND the steps to update the binary size cache did not run

## Description of the changes
- Change the check for size to not run when on the main branch

## Testing
- The check is expected to still fail for this PR and will have to be
force-merged
- But then the same check on main should succeed and update the cached
value

Signed-off-by: Yuri Shkuro <[email protected]>
Signed-off-by: amol-verma-allen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:ci Change related to continuous integration / testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants