Skip to content

status check -> merge via CLU -> new status check#802

Open
ZackarySantana wants to merge 2 commits intoevergreen-ci:mainfrom
ZackarySantana:another-one
Open

status check -> merge via CLU -> new status check#802
ZackarySantana wants to merge 2 commits intoevergreen-ci:mainfrom
ZackarySantana:another-one

Conversation

@ZackarySantana
Copy link
Contributor

No description provided.

@evergreen-ci-staging
Copy link

There is an existing patch(es) for this commit SHA:

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.

@ZackarySantana
Copy link
Contributor Author

ZackarySantana commented Feb 6, 2026

My base commit is 4aa48dc before merging. Patch. Latest is 4139a07. The patch says #801 PR because they share the same commit hash, see the Evergreen bot comment above.

The CLI gives: 4aa48dc

@ZackarySantana
Copy link
Contributor Author

ZackarySantana commented Feb 6, 2026

Nothing changed. My base commit is 4aa48dc before merging. Patch. Latest is 4139a07

The CLI gives: 4139a07

@ZackarySantana
Copy link
Contributor Author

evergreen retry

@ZackarySantana
Copy link
Contributor Author

It gives the right one now (4139a07), patch.

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.

1 participant