Travis CI: Expected - Waiting for status to be reported

[DimitriPapadopoulos]

@adrienverge I keep seeing this error message when creating a pull request. Can you check the repository settings and make sure it has been migrated as described below?

Known Issue: Travis CI reports “Expected - Waiting for status to be reported” on the GitHub Status API, but the status never arrives

[DimitriPapadopoulos]

Perhaps have a look at the latest comments:

BanzaiMan
Could you try syncing your data, https://travis-ci.com/account/repositories or https://travis-ci.org/account/repositories, and restart (portions of, if appropriate) the builds?

BanzaiMan
@darth If you have the authorization, could you try resetting the check status integration? (Disable and re-enable the repo?) You might need to restart the (parts of) the affected builds, unfortunately.

[DimitriPapadopoulos]

Alternatively can you integrate PR #731 and #733? Test ./tests/lint/run.sh passes locally.

[adrienverge]

I tried what the latest comments suggest, but disabling the repo on https://travis-ci.org/account/repositories fails with: "An error happened when we tried to alter settings on GitHub."

Anyway, I merged #731 and #733. Feel free to ping me if needed!

[DimitriPapadopoulos]

Perhaps you need to "revoke access in GitHub and log in again in Travis CI":

• API Error when trying to travis enable a github repo
• Pushes won’t trigger new builds anymore after the project has been inactive for a long time

[DimitriPapadopoulos]

Now #734 fails too. It looks like pull requests are currently out-of-order. If the above links don't work, we might have to open a ticket on the Travis site. I cannot do that as I don't have access to the GitHub settings.

[adrienverge]

I just did that. Can you check again? I don't have a way to relaunch pending builds without closing then reopening pull requests.

[DimitriPapadopoulos]

Works just fine. Hopefully we won't see this Travis CI failure again.

[DimitriPapadopoulos]

Again all new PRs are "Waiting for status to be reported". I think this is relevant, but in theory you should have already applied relevant changes:

• Known Issue: Travis CI reports “Expected - Waiting for status to be reported” on the GitHub Status API, but the status never arrives

[DimitriPapadopoulos]

See:

• fix a possible null pointer dereference #740
• add set-default-route=[01] #741

[DimitriPapadopoulos]

@adrienverge Travis CI still fails, see new pull request #755 for example. I cannot look into this (perhaps by opening an issue against Travis) because I cannot see or modify the set up of the repository.

[adrienverge]

@DimitriPapadopoulos I'm sorry about that :/

Last days, I experienced the same problem on other GitHub repositories. I'm hoping they will eventually fix it.

In the meantime, I removed the merge protection, which means you and Martin can merge even when tests didn't pass (or weren't reported).

[DimitriPapadopoulos]

I have found 11 Travis CI issues containing Expected - Waiting for status to be reported and all of them are closed:
https://github.com/travis-ci/travis-ci/issues?q=is%3Aissue+Expected+-+Waiting+for+status+to+be+reported
Perhaps we should look into each of these issues and make sure we have applied all necessary changes.

Then we could open our own issue, but it looks like they rather expect such issues to be discussed on the Travis CI Community forum these days.

In the meantime it might be worth trying travis_retry:
https://docs.travis-ci.com/user/common-build-problems/#timeouts-installing-dependencies

[DimitriPapadopoulos]

The most relevant post on the forum is probably this one:
Known Issue: Travis CI reports “Expected - Waiting for status to be reported” on the GitHub Status API, but the status never arrives
Most other posts refer to this post.

[adrienverge]

TL;DR: It should work now 👍

Thanks again @DimitriPapadopoulos, your last link is indeed the most relevant. Switching from travis-ci.org to travis-ci.com (hence from continuous-integration/travis-ci to Travis CI - Pull Request reports) should solve their bug, according to this post.

But their .org → .com transition is rather buggy, and it was impossible to "just enable" openfortivpn in travis-ci.com. I encountered at least two of their bugs (for example most of my repos were listed, but some, including openfortivpn, didn't show up in the list, even while trying all the solutions from travis-ci/travis-ci#8689, while revoking/re-granting all access from GitHub, and using private/clean browsers). I think this has something to do with the temporary openfortivpn-ghsa-qcxx-7rxx-cgxx repo, because this one randomly showed up/not showed up in the list.
Finally, I tried joining travis-ci.com beta, just in case. It allowed me to try an automatic migration of the openfortivpn repo. Luckily, that finally worked... After 50 min spent on this problem.

The required check for pull requests is now the "new" one:

PS: Since the old travis-ci.org integration is now revoked, old and current pull requests don't have Travis reports (green icons) anymore.

PPS: I'll 🤞 and close this. Feel free to reopen if needed!

[DimitriPapadopoulos]

Excellent! Thank you for taking the time to look into this Travis CI mess.