Closed mmazur closed 2 years ago
Hi @mmazur. Thanks for your PR.
I'm waiting for a operate-first member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
/lgtm
/test peribolos
@mmazur: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
/retest-required
@mmazur: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test
message.
I've tried looking into the failed CI job, but I don't really understand why it's failing and am unable to make it try again.
@mmazur yes we just found out there is an issue with the ci here, we suspect: https://github.com/operate-first/common/issues/63
For now can you rebase and I'll go ahead and manually merge it
Rebased.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: durandom
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
Ci still failing. 😕
/override community-management/prow/peribolos
@HumairAK: Overrode contexts on behalf of HumairAK: community-management/prow/peribolos
New team will create and maintain various SRE–related materials. It will not be performing SRE activities, as there's already a SIG Ops which has the responsibility of dealing with ops tasks on the op1st cloud.
The initial
slo-evaluator
repo is a python project for an engine evaluating and storing SLOs (code is here for the time being.).