Skip to content

[2.8] MOD-9612: Do not check for early timeouts in non-strict timeout policy#6113

Merged
raz-mon merged 1 commit into2.8from
razmon-cp_2.8_nonstrict_timeout
May 14, 2025
Merged

[2.8] MOD-9612: Do not check for early timeouts in non-strict timeout policy#6113
raz-mon merged 1 commit into2.8from
razmon-cp_2.8_nonstrict_timeout

Conversation

@raz-mon
Copy link
Collaborator

@raz-mon raz-mon commented May 8, 2025

CP of #6108 to 2.8

#6108)

* Revert "MOD-9612: Fix flaky test and change early timeout error message (#6100)"

This reverts commit 4e04202.

* Do not check for early timeouts in non-strict policy

* Fix tests
@raz-mon raz-mon requested review from alonre24 and oshadmi May 8, 2025 20:33
@codecov
Copy link

codecov bot commented May 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.56%. Comparing base (91806d1) to head (a3a84cf).
Report is 2 commits behind head on 2.8.

Additional details and impacted files
@@            Coverage Diff             @@
##              2.8    #6113      +/-   ##
==========================================
- Coverage   86.57%   86.56%   -0.01%     
==========================================
  Files         205      205              
  Lines       34694    34695       +1     
==========================================
- Hits        30036    30034       -2     
- Misses       4658     4661       +3     
Flag Coverage Δ
flow 80.91% <100.00%> (-0.23%) ⬇️
unit 41.11% <0.00%> (-0.01%) ⬇️

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.

@raz-mon raz-mon added this pull request to the merge queue May 11, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 11, 2025
@raz-mon raz-mon added this pull request to the merge queue May 13, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 13, 2025
@raz-mon raz-mon added this pull request to the merge queue May 13, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 13, 2025
@raz-mon raz-mon added this pull request to the merge queue May 13, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 13, 2025
@raz-mon raz-mon added this pull request to the merge queue May 13, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 13, 2025
@raz-mon raz-mon added this pull request to the merge queue May 14, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 14, 2025
@raz-mon raz-mon added this pull request to the merge queue May 14, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 14, 2025
@raz-mon raz-mon added this pull request to the merge queue May 14, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 14, 2025
@raz-mon raz-mon added this pull request to the merge queue May 14, 2025
Merged via the queue into 2.8 with commit 8537791 May 14, 2025
9 checks passed
@raz-mon raz-mon deleted the razmon-cp_2.8_nonstrict_timeout branch May 14, 2025 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants