-
Notifications
You must be signed in to change notification settings - Fork 397
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
Application error when running test #83
Comments
Same for us. We're getting Error: "Unkown" when trying to trigger a test on https://speedtracker.org/test and the API responds with 503 and the same body as above. Ping @eduardoboucas |
The problem is that GitHub blocked our bot, saying it was committing too frequently to too many forks of the dashboard repo. I’m still trying to find the best alternative going forward, that allows people to use the platform for free and without too much hassle in the installation process. The obvious choice would be to start storing tests in a database, but what database would carry costs that I’m not willing to take on my own. A crowdfunded solution that would allow people to make small contributions in order to keep the service alive would be great, but I don’t know how to start such a movement and whether it would be fruitful. I haven’t had enough time to even look into it, to be honest. Any suggestions welcome! Thanks and sorry about this. |
Speedtracker-bot stopped committing to our repo on April 2. Is this related? I've got a separate instance running for a personal project and that's still appears to be working fine (running tests once a day) – what's the difference? |
Maybe there's some way that commits can be done not from the bot, but from some user that we share permissions to? Like our own bot, so it won't be the same for all users and won't be blocked.. |
I trigger speedtracker test as a part of my deploy process, but I started getting heroku’s application errors some time ago:
Also does not work when using web UI (https://speedtracker.org/test):
The text was updated successfully, but these errors were encountered: