Skip to content

tests: configure github remaining limit + read token #9800

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

Merged
merged 12 commits into from
Jan 16, 2020

Conversation

sapk
Copy link
Member

@sapk sapk commented Jan 16, 2020

In order to not trigger API limits in CI,

This is a simple configuration to not failed when we have 3 running jobs of unit-test in parallel for CI.

We should also provide a github key (I think I have the rights to do it) with minimum permission to increase the limit and not have to wait. Done!

@sapk sapk added topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. labels Jan 16, 2020
@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

This currently doesn't work because we already are over API rates. I think I could create a function to refresh api rate before.

@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Jan 16, 2020
@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

Another improvement, could also to call RefreshRate if rate is nil in sleep function.

@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

While other jobs aren't filtering it will still keep failing when they consume the full api rate in parallel.

@GiteaBot GiteaBot added lgtm/need 1 This PR needs approval from one additional maintainer to be merged. and removed lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. labels Jan 16, 2020
@sapk sapk changed the title ci: configure github remaining limit tests: configure github remaining limit Jan 16, 2020
@sapk sapk added type/testing topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile and removed topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile labels Jan 16, 2020
@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

Now the test use GITHUB_READ_TOKEN env variable as access token (empty by default)

@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

I added github_read_token (user https://github.com/gitea-test with only read email) to drone

@sapk sapk changed the title tests: configure github remaining limit tests: configure github remaining limit + read token Jan 16, 2020
@codecov-io
Copy link

codecov-io commented Jan 16, 2020

Codecov Report

Merging #9800 into master will increase coverage by 0.1%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##           master    #9800     +/-   ##
=========================================
+ Coverage   42.19%   42.29%   +0.1%     
=========================================
  Files         603      603             
  Lines       78868    78868             
=========================================
+ Hits        33278    33359     +81     
+ Misses      41511    41419     -92     
- Partials     4079     4090     +11
Impacted Files Coverage Δ
services/pull/check.go 52.7% <0%> (-2.71%) ⬇️
models/repo.go 46.98% <0%> (+0.24%) ⬆️
models/error.go 31.31% <0%> (+0.54%) ⬆️
models/pull.go 42.59% <0%> (+0.6%) ⬆️
modules/migrations/gitea.go 8.34% <0%> (+1.45%) ⬆️
modules/repository/repo.go 27.83% <0%> (+1.54%) ⬆️
services/pull/temp_repo.go 34.18% <0%> (+2.56%) ⬆️
modules/migrations/migrate.go 25.78% <0%> (+4.21%) ⬆️
services/pull/patch.go 67.92% <0%> (+5.03%) ⬆️
models/task.go 32.72% <0%> (+17.27%) ⬆️
... and 2 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e8a3ae0...61a24fc. Read the comment docs.

@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Jan 16, 2020
@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

I have merged #9796 before this one to re-validate that it passed with the token will others are failing.

@sapk
Copy link
Member Author

sapk commented Jan 16, 2020

Now CI failed for an other reason on sqlite test ... It will never end 😄

Copy link
Member

@6543 6543 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice !

@6543
Copy link
Member

6543 commented Jan 16, 2020

and it passed 👍

@sapk sapk merged commit 11885da into go-gitea:master Jan 16, 2020
@sapk sapk deleted the skip-github-api branch January 16, 2020 15:15
6543 pushed a commit to 6543-forks/gitea that referenced this pull request Jan 19, 2020
* ci: configure remaining github limmit

* prepend with github since package is common to all migrations

* add RefreshRate

* Update github.go

* add missing space

* go fmt

* Read env variable GITHUB_READ_TOKEN for token

* Update .drone.yml
sapk added a commit that referenced this pull request Jan 19, 2020
* ci: use docker image for golangci-lint (#9737)

* ci: re-ordering Drone CI for optimizing time (#9719)

* ci: try re-ordering for optimizing time

* ci: try re-ordering for optimizing time

* ci: try re-ordering for optimizing time

* ci: try re-ordering for optimizing time

* ci: try re-ordering for optimizing time

* ci: try re-ordering for optimizing time

* ci: try offloading mysql8 to arm64

* Revert "ci: try offloading mysql8 to arm64"

This reverts commit c60de5d.

* ci: try offloading pgsql to arm64

* ci: activate ldap on arm64

* ci: test mysql8 in place pgsql arm64

* chore: clean un-needed move

* typo

* ci: revert runnning mysql on arm64

* ci: run compliance on arm

* chore: limit change

* chore: readd maybe need for release fetch-tags

* ci: remove docker-linux-amd64-dry-run

* ci: remove docker-linux-amd64-dry-run

* Revert "ci: remove docker-linux-amd64-dry-run"

This reverts commit 0715f65.

Co-authored-by: zeripath <[email protected]>
Co-authored-by: Lunny Xiao <[email protected]>

* ci: use new mssql image (#9720)

Co-authored-by: Lunny Xiao <[email protected]>

* ci: run notify on arm64 (#9762)

* ci: run notify on arm64

Free one jobs on amrd64

* Update .drone.yml

* Update .drone.yml

* Update .drone.yml

Based on: https://github.com/appleboy/drone-discord/blob/master/.drone.yml#L339

* improve trigger

Co-authored-by: techknowlogick <[email protected]>

* ci: move some integration tests on arm64 (#9747)

* tests: configure github remaining limit + read token (#9800)

* ci: configure remaining github limmit

* prepend with github since package is common to all migrations

* add RefreshRate

* Update github.go

* add missing space

* go fmt

* Read env variable GITHUB_READ_TOKEN for token

* Update .drone.yml

* ci: simplify tag/release by always running coverage (#9774)

* ci: simplify tag/release by always running coverage

* use mod and vendor for unit test coverage

* remove not needed lfs for unit test

* use arm drone agent for docs (#9776)

* run translations pipeline on arm server (#9865)

* add git-check to Makefile

Co-authored-by: Antoine GIRARD <[email protected]>
Co-authored-by: zeripath <[email protected]>
Co-authored-by: Lunny Xiao <[email protected]>
Co-authored-by: techknowlogick <[email protected]>
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. skip-changelog This PR is irrelevant for the (next) changelog, for example bug fixes for unreleased features. topic/build PR changes how Gitea is built, i.e. regarding Docker or the Makefile type/testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants