-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Fix [suggest] #2604
Fix [suggest] #2604
Conversation
|
Is it possible to have a smoke test for this functionality? |
It gets tested as part of the service test run. The test was failing, but hadn’t been picked up on yet. |
I don't see any failures in https://github.com/badges/shields/commits/master - is service test run is a manual process? |
The full service-test run is here: https://circleci.com/gh/badges/daily-tests The suggest tests will be passing now because the fix is merged. We can’t run all the tests on every commit so we run affected tests as parts of PRs. The brackets around suggest in the PR indicate that test suite ran here. Occasionally a change will affect something unexpected so it gets caught later by the daily tests. |
Why? It is only 4 minutes in the daily log. |
Our PR build runs in about 20 seconds; 4 minutes is much too slow. The other issue is that the service tests rely on external services. #927 is the discussion about that. We used to run the full suite on every commit to master, but stopped because they often fail for reasons outside our control. The thing we could use more help with is keeping up with fixing the failures identified tests (i.e. #1359). |
I see. Is there a way to make a "yellow" badge status if tests are failed because of external services and resort to "red" if there is something wrong with the code? |
Ref #2420 (comment)