Skip to content
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

Lsuhsc downtime #4318

Merged
merged 3 commits into from
Nov 21, 2024
Merged

Lsuhsc downtime #4318

merged 3 commits into from
Nov 21, 2024

Conversation

jdost321
Copy link
Contributor

No description provided.

Copy link
Collaborator

@osg-bot osg-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greetings @jdost321,

Thank you for your pull request.

Your requested changes affect one or more downtime files, but are not eligible for downtime automerge; OSG Staff will need to manually review this PR.

-- OSG-BOT 🔍


Output from the automerge downtime check script:

Falling back to merge-base c0758066d08548abc3ee8db845bc05a04d714d2f to list changes instead of unmerged PR base 41d89613d1dbddab2bf294aed9333a0a4e48c253
New Downtime 1972068975 modified for resource 'LSUHSC-Tigerfish-CE2'
Commit is not eligible for auto-merge:
 - PR head d15f0a1d1220d09f7bc0028292c102200aafe3f6 is out-of-date: 41d89613d1dbddab2bf294aed9333a0a4e48c253 is not merged
 - File 'projects/ND_Thain.yaml' is not a downtime file.
 - File 'projects/UCF_Karalidi.yaml' is not a downtime file.


@jdost321
Copy link
Contributor Author

I don't know what happened when I created this pr.. I only made the commit for the downtime in the LSUHSC-Tigerfish_downtime.yaml file.. not sure how some other files got touched..or how to fix this?

@matyasselmeci matyasselmeci merged commit 4993d58 into opensciencegrid:master Nov 21, 2024
4 checks passed
@matyasselmeci
Copy link
Collaborator

I'm not sure what happened either; the only thing I noticed was that the extra commits that got in were merged into master only five minutes before your PR so maybe something was out of date. Anyway, fixed.

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.

4 participants