Problems with CI - hitting github rate limits
by Rich Megginson
We're having some problems with CI - getting errors like this:
ERROR: GitHub: You have triggered an abuse detection mechanism. Please
wait a few minutes before you try again.
WARNING: Rate limiting hit, waiting for 1957 seconds
I'm going to scale down the number of pods used in production - perhaps
there are too many concurrent operations.
2 years, 6 months
Contributions after GSoC
by Elvira G.
I had a good experience with this project during the Google Summer of
Code and therefore I will like to continue contributing. Right now I'm
trying to add Python 2 support to the Pytest integration. However, I
must say that I will be away from home this week, so I won't be able to
see any messages until Friday!
PS: From now on I will try to ask more through IRC, I think should use
the community channels more instead of always asking Till. I hope to not
bother all of you too much :-)
Thanks for your attention and kindness,
2 years, 6 months
Re: Wrong version of CI rolled out to production
by Richard Megginson
Yes. This is now deployed in production.
-------- Original message --------From: Till Maas <till(a)redhat.com> Date: 9/2/20 3:00 AM (GMT-07:00) To: Rich Megginson <rmeggins(a)redhat.com> Cc: systemroles(a)lists.fedorahosted.org Subject: Re: [Systemroles] Wrong version of CI rolled out to production Hi,is this now moved to production for real? It is important to knowsince it will require to update the branch restrictions.ThanksTillAm Fr., 28. Aug. 2020 um 18:48 Uhr schrieb Rich Megginson <rmeggins(a)redhat.com>:>> I accidentally rolled out the wrong version of CI to production. In> deploying the staging environment, I did not notice that the container> build had been pushed to production, which caused a redeploy of> production using the staging code:> https://github.com/linux-system-roles/test-harness/pull/103 - I fixed> this and redeployed the correct code to production, but in the meantime> several system role PRs were tested with this new code. The main effect> is that the testing status will be in the form>> platform-version/ansible-2.9>> rather than the old format>> linux-system-roles-test/platform-version>> The following PRs are affected:>> https://github.com/linux-system-roles/certificate/pull/38>> https://github.com/linux-system-roles/network/pull/262>> https://github.com/linux-system-roles/storage/pull/153>> https://github.com/linux-system-roles/network/pull/234>> https://github.com/linux-system-roles/storage/pull/121>> https://github.com/linux-system-roles/storage/pull/142>> https://github.com/linux-system-roles/network/pull/267>> https://github.com/linux-system-roles/network/pull/261>> https://github.com/linux-system-roles/logging/pull/166>>> I don't think there will be any issues, it's just that the above PRs> will have statuses that should ignored. I'm not sure if the number of> statuses in any of the above PRs has increased enough that we will hit> the github page size for statuses (note that we have fixed this issue in> staging, but it has not yet been rolled out to production), or any rate> limit problems. And unfortunately the github API provides no way to> remove statuses. I will continue to monitor.> _______________________________________________> systemroles mailing list -- systemroles(a)lists.fedorahosted.org> To unsubscribe send an email to systemroles-leave(a)lists.fedorahosted.org> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines> List Archives: https://firstname.lastname@example.org... Till MaasHe/His/HimAssociate Manager, Software EngineeringNetworkManager, Nmstate, Ansible RHEL Networking System RoleRed Hat GmbH, https://de.redhat.com/, Registered seat: Grasbrunn,Commercial register: Amtsgericht Muenchen, HRB 153243,Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
2 years, 6 months