Skip to content

Conversation

@booxter
Copy link
Contributor

@booxter booxter commented May 6, 2025

No description provided.

@booxter booxter force-pushed the ihrachyshka-py312-smoke-variant branch from 6a42d79 to 57b31f0 Compare May 6, 2025 21:32
@mergify mergify bot added the CI/CD Affects CI/CD configuration label May 6, 2025
@booxter
Copy link
Contributor Author

booxter commented May 6, 2025

@RobotSail
Copy link
Member

Thank you for adding this @booxter , this will be very helpful to have as we broaden the scope of software versions we intend to support.

@mergify mergify bot added the ci-failure label May 7, 2025
@booxter booxter force-pushed the ihrachyshka-py312-smoke-variant branch from 57b31f0 to 3d8bf12 Compare May 20, 2025 20:19
@booxter booxter marked this pull request as ready for review May 20, 2025 20:20
@booxter booxter changed the title ci: add Python 3.11 and 3.12 matrix to smoke workflow tests ci: add 3.12 smoke workflow flavor May 20, 2025
@mergify mergify bot removed the ci-failure label May 20, 2025
@booxter booxter marked this pull request as draft May 20, 2025 20:21
@booxter booxter force-pushed the ihrachyshka-py312-smoke-variant branch 2 times, most recently from cff36ad to bcfddb2 Compare May 20, 2025 21:21
@mergify mergify bot added the ci-failure label May 20, 2025
Yes, it's a lot of duplication. Until we have some way to generate
workflows from a template, we have to have it: matrix doesn't apply
because if used, it will use the same single ec2 runner for both 3.11
and 3.12 runs - and while it works, it slows down feedback almost by x2
because these are run sequentially.

Signed-off-by: Ihar Hrachyshka <[email protected]>
@booxter booxter force-pushed the ihrachyshka-py312-smoke-variant branch from bcfddb2 to 53f9ef9 Compare May 20, 2025 21:48
@mergify mergify bot added ci-failure and removed ci-failure labels May 20, 2025
@booxter
Copy link
Contributor Author

booxter commented May 20, 2025

Leaving out EC2 runner reusable action work to a separate issue: #557

@booxter booxter marked this pull request as ready for review May 20, 2025 22:10
@booxter
Copy link
Contributor Author

booxter commented May 20, 2025

That the patch is working can be observed here for py311: https://github.com/instructlab/training/actions/runs/15148654764/job/42590466635

For 3.12 flavor, we'll have to merge the patch before we can trigger it in Workflow UI to prove it works. I don't expect issues with it; but if any arise, we'll deal with them.

@booxter booxter requested review from JamesKunstle and RobotSail May 20, 2025 22:12
@mergify mergify bot added the ci-failure label May 20, 2025
@mergify mergify bot added the one-approval label May 20, 2025
@booxter
Copy link
Contributor Author

booxter commented May 21, 2025

Not sure why mergify believes there's a ci-failure (as per label). Everything that ran is green (there's not much because pull_request_target workflows can't be validated with regular checks - hence manual execution linked above.

@mergify mergify bot removed the one-approval label May 21, 2025
@ktdreyer
Copy link
Contributor

I'm not sure about the ci-failure label, but I think I know why Mergify doesn't merge this. The Mergify results for this PR shows an unchecked box next to this line: #review-requested=0

The problem is that @JamesKunstle is marked as a reviewer and he has not approved this PR.

In the past, developers handle this situation by removing pending reviewers from the PR.

@RobotSail RobotSail removed the request for review from JamesKunstle May 21, 2025 18:56
@RobotSail RobotSail merged commit 1532531 into main May 21, 2025
10 of 12 checks passed
@RobotSail RobotSail deleted the ihrachyshka-py312-smoke-variant branch May 21, 2025 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI/CD Affects CI/CD configuration ci-failure

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants