- Notifications
You must be signed in to change notification settings - Fork5.7k
test: Fix 'test_idle' test#1346
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This test annoyingly caused all PRs to appear as failed.The cause was the fact that the last message logged isn'tthe 'Received signal 15' message, but the 'Error whilegetting Updates: Conflict: terminated by setWebhook request'.
Ehm, I'm guessing you;re running multiple tests at the same time. I've never ran into this problem. Never on CI either. |
I've found this issue on CI (not locally). Check out the Travis CI builds of#1325 and#1345; they both failed on Admittedly I don't know very well what the issue at hand is, I just tried to see if this would work (I can't test CI from my fork). |
Hi, It seems travis was having some trouble with it's environment variables which made multiple jobs try to run tests on the same bot. hence the error you experienced. It should be fixed now so there's no need for this PR. Thanks anyway! |
@Eldinnie Hi; the issue seems to persist:https://travis-ci.org/python-telegram-bot/python-telegram-bot/jobs/500342043 (just FYI). |
Uh oh!
There was an error while loading.Please reload this page.
This test annoyingly caused some Travis CI checks to appear as failed, when the changes are unrelated to that test. The cause was the fact that the last message logged isn't the 'Received signal 15' message, but the 'Error while getting Updates: Conflict: terminated by setWebhook request'.