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

cc no effect #968

Open
1 task done
wuhuizuo opened this issue Jun 21, 2022 · 5 comments
Open
1 task done

cc no effect #968

wuhuizuo opened this issue Jun 21, 2022 · 5 comments
Labels
lifecycle/rotten type/bug The issue is confirmed as a bug.

Comments

@wuhuizuo
Copy link
Contributor

Bug Report

  • I have searched the issues of this repository and believe that this is not a duplicate.

Related link

  • Which project:

  • PR or Issue Link:

Steps to reproduce(Optional)

What is expected?

/cc can assign reviewer

What is actually happening?

no effect
chaos-mesh/chaos-mesh#3343 (comment)

it happened before two years ago
chaos-mesh/chaos-mesh#3192 (comment)
chaos-mesh/chaos-mesh#3293 (comment)

@wuhuizuo wuhuizuo added the type/bug The issue is confirmed as a bug. label Jun 21, 2022
@wuhuizuo
Copy link
Contributor Author

@STRRL

@STRRL
Copy link

STRRL commented Jun 21, 2022

it happened before two years ago
chaos-mesh/chaos-mesh#3192 (comment)
chaos-mesh/chaos-mesh#3293 (comment)

More detail about that: @YangKeao is always Chaos Mesh Maintainer since 2 years ago.

Command /cc still worked on 2022-04-27: chaos-mesh/chaos-mesh#3192 (comment)
but it did not work after 2022-05-25(maybe even earlier): chaos-mesh/chaos-mesh#3293 (comment)

@Mini256
Copy link
Member

Mini256 commented Jun 21, 2022

From the log, it shows finished, but it is not actually executed. I think the problem may occur in the GitHub API.

{"author":"Mini256","component":"hook","event-GUID":"e7235560-f146-11ec-98ce-79abc5f226bf","event-type":"issue_comment","file":"prow/hook/events.go:338","func":"k8s.io/test-infra/prow/hook.(*Server).handleIssueCommentEvent","level":"info","msg":"Issue comment created.","org":"chaos-mesh","pr":3362,"repo":"chaos-mesh","severity":"info","time":"2022-06-21T09:45:38Z","url":"https://github.com/chaos-mesh/chaos-mesh/pull/3362#issuecomment-1161516018"}
{"author":"Mini256","component":"hook","event-GUID":"e7235560-f146-11ec-98ce-79abc5f226bf","event-type":"issue_comment","file":"prow/plugins/assign/assign.go:148","func":"k8s.io/test-infra/prow/plugins/assign.handle","level":"info","msg":"Adding reviewer(s) to chaos-mesh/chaos-mesh#3362: [YangKeao]","org":"chaos-mesh","plugin":"assign","pr":3362,"repo":"chaos-mesh","severity":"info","time":"2022-06-21T09:45:38Z","url":"https://github.com/chaos-mesh/chaos-mesh/pull/3362#issuecomment-1161516018"}
{"author":"Mini256","client":"github","component":"hook","event-GUID":"e7235560-f146-11ec-98ce-79abc5f226bf","event-type":"issue_comment","file":"prow/github/client.go:889","func":"k8s.io/test-infra/prow/github.(*client).log","level":"info","msg":"RequestReview(chaos-mesh, chaos-mesh, 3362, [YangKeao])","org":"chaos-mesh","plugin":"assign","pr":3362,"repo":"chaos-mesh","severity":"info","time":"2022-06-21T09:45:38Z","url":"https://github.com/chaos-mesh/chaos-mesh/pull/3362#issuecomment-1161516018"}
{"author":"Mini256","client":"github","component":"hook","duration":"445.642315ms","event-GUID":"e7235560-f146-11ec-98ce-79abc5f226bf","event-type":"issue_comment","file":"prow/github/client.go:891","func":"k8s.io/test-infra/prow/github.(*client).log.func2","level":"debug","msg":"RequestReview(chaos-mesh, chaos-mesh, 3362, [YangKeao]) finished","org":"chaos-mesh","plugin":"assign","pr":3362,"repo":"chaos-mesh","severity":"debug","time":"2022-06-21T09:45:38Z","url":"https://github.com/chaos-mesh/chaos-mesh/pull/3362#issuecomment-1161516018"}

@ti-chi-bot
Copy link
Member

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle stale

@ti-chi-bot
Copy link
Member

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-community-infra or Mini256.
/lifecycle rotten

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

4 participants