GitHub PR is being built but result is not shown

Travis CI Discussions & Feedback
1

I have Travis CI set up on a GitHub repository to build the commits to every PR. This worked fine until ~2-4 weeks ago. I noticed that within a PR the result of the building process is not shown within the PR. I thought I might have messed up the configuration or something else.

Today, I came around to try to fix this and found that the commit is correctly build by Travis CI, but the result is not reported back.

Example:

PR: https://github.com/pmeier/pystiche/pull/40

Travis CI build: https://travis-ci.org/pmeier/pystiche/builds/642793488

Does someone have an idea what is going on?

2

We also encountered the problem, travis-ci did not report the build status:

d7f7e00c29b0a47b3a4e7ad97
d7f7e00c29b0a47b3a4e7ad971538Ɨ870 106 KB

continuous-integration/travis-ci Expected ā€” Waiting for status to be reported

We solved it after some operations, you may have a try:

  1. Revoke authorization of travis-ci from github:
    Go to Sign in to GitHub Ā· GitHub, find ā€œTravis CI for Open Sourceā€ row and click ā€œā€¦ā€ then click the dropdown ā€œRevokeā€ button.

  2. Reset Access of ā€œTravis CI for Open Sourceā€ (Iā€™m not sure if this is necessary): Go to github organization home page and click ā€œSettingsā€ - " Third-party access", find the ā€œTravis CI for Open Sourceā€ and click the ā€œEditā€ button, then it will jump to ā€œAccess Reviewā€ page, my url like this https://github.com/organizations/hugegraph/settings/oauth_application_policy
    https://github.com/orgs/hugegraph/policies/applications/1508
    click ā€œDeny accessā€ then click ā€œGrant accessā€.

  3. Re-authorize travis account:
    Go to https://travis-ci.org/, and sign out the account, then click ā€œSign in with GitHubā€, and it will jump to ā€œAuthorize Travis CI for Open Sourceā€ page, click the green ā€œAuthorize travis-ciā€ button. Well everything is done.

It works fine for me.

2 Likes
3

It worked, thanks. Mind that I canā€™t confirm if step 2. is necessary, since Iā€™m not part of an organisation.

4

I can confirm that was not necessary in my case. Revoking access and authorising it again fixed the issue.

6

It worked too for the chess engine Stockfish, thanks a lot!