-
Notifications
You must be signed in to change notification settings - Fork 37
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
add myself to ci #594
add myself to ci #594
Conversation
Signed-off-by: Danny <dreidenbach@nvidia.com>
7afe196
to
4b53689
Compare
/build-ci |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #594 +/- ##
=======================================
Coverage 88.78% 88.78%
=======================================
Files 81 81
Lines 5027 5027
=======================================
Hits 4463 4463
Misses 564 564 ☔ View full report in Codecov by Sentry. |
@pstjohn What CI is running here? blossom or azure? Danny is testing if it's possible to penetrate our blossom CI user list via a simple PR 😬 |
Yeah the azure CI is running, blossom likely won't run with this simple PR. See #598 for an example of what that looks like |
So I still need to add my name via this MR to run the blossom ci right? |
I believe you also need to add yourself internally; the blossom folks keep a separate list of authorized users |
/build-ci |
667274f
to
d8ddf4a
Compare
/build-ci |
Adding myself to be able to run ci --------- Signed-off-by: Danny <dreidenbach@nvidia.com> Co-authored-by: Timur Rvachov <120140748+trvachov@users.noreply.github.com>
Adding myself to be able to run ci