Open guangy10 opened 2 days ago
Why am I start getting fetch_tests - Unauthorized
error on all the PRs I'm creating?
This seems to be happening more often, @ydshieh would you know what might be happening? Otherwise I'll reach out to the CircleCI team, this is hindering work on the repo
I've asked the CircleCI team @guangy10, very sorry for the inconvenience.
Might be related to
Allow CI could be run on private forked repositories (e.g. new model additions) (#33594)
But not happening on all external contributor's PRs. Strange
Could you first try ..?
https://support.circleci.com/hc/en-us/articles/360048210711-How-to-Refresh-User-Permissions
Another thing to check
If you're following the fork instead of the upstream repo
A user who submits a pull request to your repository from a fork, but no pipeline is triggered with the pull request. This can happen when the user is following the project fork on their personal account rather than the project itself on CircleCI.
This will cause the jobs to trigger under the user's personal account. If the user is following a fork of the repository on CircleCI, we will only build on that fork and not the parent, so the parent’s PR will not get status updates.
In these cases, the user unfollows their fork of the project on CircleCI. This will trigger their jobs to run under the organization when they submit pull requests. Those users can optionally follow the source project if they wish to see the pipelines.
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.
Could you first try ..?
https://support.circleci.com/hc/en-us/articles/360048210711-How-to-Refresh-User-Permissions
Weird. Used to work fine on my old PRs. Tried "Refresh Permission". Let's see if it can be unblocked.
@ydshieh It's getting worse after re-fresh the permissions. check_circleci_user starts failing.
Another thing to check
If you're following the fork instead of the upstream repo
A user who submits a pull request to your repository from a fork, but no pipeline is triggered with the pull request. This can happen when the user is following the project fork on their personal account rather than the project itself on CircleCI. This will cause the jobs to trigger under the user's personal account. If the user is following a fork of the repository on CircleCI, we will only build on that fork and not the parent, so the parent’s PR will not get status updates. In these cases, the user unfollows their fork of the project on CircleCI. This will trigger their jobs to run under the organization when they submit pull requests. Those users can optionally follow the source project if they wish to see the pipelines.
"In these cases, the user unfollows their fork of the project on CircleCI. " I have no idea how to unfollow my fork on CircleCI. I don't even see if I'm following transformers on CircleCI. I created a CircleCI account with exact email and linked to my github, and I can't see any project I'm following..
so please be sure "Build forked pull requests" is enabled in Project Settings > Advanced
@ydshieh Their Wiki is so bad. I can't find this setting from anywhere.
Hmm, weird CircleCI issue ...
Could you check a last time:
top-left (like in the image): organization : switch to your own org, follow transformers
there.
Optionally: Then switch to huggingface
(if you can find it) and follow transformers
there
If still not working, I could try to push a commit.
What does this PR do?
Adding
generate
support for exported model. Addinggemma2-2b
toExecuTorch
with tests. Adding an integration test forgemma-2b
that we've enabled already.Additional Test in
ExecuTorch
Running
gemma2-2b
E2E:Before submitting
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR.
@ArthurZucker @gante @amyeroberts @qubvel