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

Trigger openvino slow tests with openvino-test label #751

Merged
merged 7 commits into from
Jun 8, 2024
Merged

Conversation

echarlaix
Copy link
Collaborator

@echarlaix echarlaix commented Jun 6, 2024

So that the openvino-test label can trigger the OpenVINO slow tests as discussed @eaidova @helena-intel

@echarlaix echarlaix added the openvino-test Trigger OpenVINO slow tests label Jun 6, 2024
@HuggingFaceDocBuilderDev

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.

@echarlaix echarlaix removed the openvino-test Trigger OpenVINO slow tests label Jun 7, 2024
@echarlaix echarlaix marked this pull request as ready for review June 7, 2024 10:01
@echarlaix
Copy link
Collaborator Author

@helena-intel @eaidova let me know if that works for you

@helena-intel
Copy link
Collaborator

Thanks @echarlaix ! Is there a way for a PR author to add this label or can only repo owners do that? I don't see a way for me to do it in the UI.

In case not everyone knows: the basic test yaml file has a workflow_dispatch trigger so PR authors can always run this test manually in their fork too
image

@echarlaix
Copy link
Collaborator Author

Is there a way for a PR author to add this label or can only repo owners do that? I don't see a way for me to do it in the UI.

I think a triage role should be enough

@echarlaix echarlaix merged commit 906668b into main Jun 8, 2024
15 checks passed
@echarlaix echarlaix deleted the label branch June 8, 2024 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants