Skip to content

Conversation

plammens
Copy link
Contributor

@plammens plammens commented Feb 17, 2019

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'.

This test annoyingly caused all PRs to appear as failed.
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'.
@Eldinnie
Copy link
Member

Ehm, I'm guessing you;re running multiple tests at the same time. I've never ran into this problem. Never on CI either.

@plammens
Copy link
Contributor Author

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 test_idle and didn't change (as far as I can see) any code that should affect that test.

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).

@Eldinnie
Copy link
Member

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 Eldinnie closed this Feb 19, 2019
@plammens
Copy link
Contributor Author

plammens commented Mar 1, 2019

@Eldinnie Hi; the issue seems to persist: https://travis-ci.org/python-telegram-bot/python-telegram-bot/jobs/500342043 (just FYI).

@github-actions github-actions bot locked and limited conversation to collaborators Aug 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants