LinuxSuRen / api-testing

YAML based API testing tool. 开源接口调试、测试工具。Mock Server

Home Page:https://linuxsuren.github.io/api-testing/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Error occur from `retest` GitHub Actions

LinuxSuRen opened this issue · comments

commented

Description:

What issue is being seen? Describe what should be happening instead of
the bug, for example: api-testing should not crash, the expected value isn't
returned, etc.

Repro steps:

Include sample requests, environment, etc. All data and inputs
required to reproduce the bug.

Note: If there are privacy concerns, sanitize the data prior to
sharing.

Environment:

Include the environment like api-testing version, os version and so on.

Logs:

Include the access logs and the api-testing logs.

image

commented

hi @yuluo-yx Please help to take a look at this error.

commented

It looks like every comment will trigger it.

image

commented

I just reverted it. We can add it once you fixed it.

Maybe the version should be lowercase yuluo-yx/gh-retest@v1.0.0-RC1

- uses: yuluo-yx/gh-retest@V1.0.0-RC1

sorry, is my question, It version is v1.0.0-RC1, I write was V1.0.0-RC1 😢😢

commented

But why it is triggered no matter what comment is created. I think we need to add a filter. It can be triggered only the specific comment created.

But why it is triggered no matter what comment is created. I think we need to add a filter. It can be triggered only the specific comment created.

The current logic is to get the comment content and run the failed task if it is /retest.

I'll implement his. 🤔

commented

I'm not sure if GitHub Actions support that kind of filter.

I'm not sure if GitHub Actions support that kind of filter.

Let me see the documentation and study it

@LinuxSuRen I study envoy repo command.yml. I've found that I have to run a workflows anyway, and github doesn't have a hook for that.

For more information you can refer to this comment, it's not /retest but judging from the action logs, it's still executing it, but not the retest action

action:
https://github.com/envoyproxy/envoy/actions/runs/8845882918/job/24290669995
comment:
envoyproxy/envoy#33818 (comment)

commented

I'm afraid too many triggers will burn out the GitHub Actions minutes. See also the official document.

2,000 minutes per month

I'm afraid too many triggers will burn out the GitHub Actions minutes. See also the official document.

2,000 minutes per month

got it, It's a factor that really needs to be taken into account 🤔

commented

By the way, you can make it be a webook server. And I know a free service that can deploy it. See https://zeabur.com/pricing

By the way, you can make it be a webook server. And I know a free service that can deploy it. See https://zeabur.com/pricing

tks, let me study