Skip to content

Conversation

@agaudreault
Copy link
Member

The main problem is with the resource tracking. When tests are run by a retry, or executed locally, it is possible that resources already exist in terminating state (done at the start of tests during the EnsureCleanState) and the tests will pick these up.

This change will increase stability, and is a small step towards parallelism.
Related to #24307

As a result, current e2e are updated if they were hardcoding the ApplicationName

@agaudreault agaudreault requested a review from a team as a code owner December 17, 2025 22:42
@bunnyshell
Copy link

bunnyshell bot commented Dec 17, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@codecov
Copy link

codecov bot commented Dec 17, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.58%. Comparing base (216611f) to head (1481ca2).
⚠️ Report is 194 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #25720      +/-   ##
==========================================
- Coverage   62.59%   62.58%   -0.01%     
==========================================
  Files         353      353              
  Lines       50120    50120              
==========================================
- Hits        31374    31370       -4     
- Misses      15729    15731       +2     
- Partials     3017     3019       +2     

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

Signed-off-by: Alexandre Gaudreault <[email protected]>
@agaudreault agaudreault enabled auto-merge (squash) December 17, 2025 23:23
@agaudreault agaudreault merged commit 13b8b45 into argoproj:master Dec 17, 2025
27 checks passed
kingbj940429 pushed a commit to kingbj940429/argo-cd that referenced this pull request Jan 16, 2026
@reggie-k reggie-k added the cherry-pick/3.3 Candidate for cherry picking into the 3.3 release label Feb 3, 2026
@argo-cd-cherry-pick-bot
Copy link

❌ Cherry-pick failed for 3.3. Please check the workflow logs for details.

argo-cd-cherry-pick-bot bot pushed a commit that referenced this pull request Feb 3, 2026
Signed-off-by: Alexandre Gaudreault <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick/3.3 Candidate for cherry picking into the 3.3 release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants