search

gfngfn / SATySFi

A statically-typed, functional typesetting system
GNU Lesser General Public License v3.0
1.16k stars 83 forks source link

Is Travis CI testing NOT working? #224

Closed y-yu closed 3 years ago

y-yu commented 4 years ago
y-yu commented 4 years ago

I encountered the same thing in https://github.com/rust-lang-ja/book-ja-pdf/pull/5 . And it was solved by this way 👇

  1. Access to the GitHub applications admin page
    • And look at Authorized OAuth Apps tab
  2. Look for the Travis CI for Open Source in the tab
    • image
  3. Revoke the Travis CI for Open Source
  4. Access to https://travis-ci.org/ (NOT travis-ci.com) and sign out if you are signed in
  5. Sign in the ~circle-ci.org~ travis-ci.org by your GitHub account
  6. Authorize ~Circle CI~ Travis CI for GitHub again

Good luck!

gfngfn commented 4 years ago

I’m sorry for the late response. I performed just now the procedure you had kindly introduced to me!

gfngfn commented 4 years ago

Is this sufficient to run CI next time when pushing commits to this repository? I mean I wonder whether I still have another task like activating the connection of this repository and Circle CI.

y-yu commented 4 years ago

Sorry, I wrote circle-ci.org. It was a mistake!!! I insisted travis-ci.org. I fixed my procedure. Please read and try it again 🙇

gfngfn commented 4 years ago

I understand. I signed in to travis-ci.org just now.

gfngfn commented 4 years ago

The CI seems working well. Thank you very much for your kind introduction!

y-yu commented 4 years ago

CI is running like that 👉 https://travis-ci.org/github/gfngfn/SATySFi/builds/677166453 but the results are not shown from GitHub.... 😇

image

I think that the connection between GitHub and Travis CI has still been broken. Maybe my forked repository name is notSATySFi, it is the reason... 🤔why CI results will not be shown.

Sorry I cannot help you for now because I cannot see what happens in detail.... 🙇

qnighy commented 4 years ago

travis-ci.org uses the old GitHub statuses API, while travis-ci.com the new checks API. They were originally separated based on open source / commercial distinction, but .com is now open for open source projects and Travis encourages migration from .org. That may be the reason the statuses are not shown.

y-yu commented 4 years ago

Thanks! I'm still using travis-ci.org so travis-ci.org haven't gave up to support the latest GitHub API yet, I think... However Travis encourages migration from .org. so it would be better to try out travis-ci.com in any case. I agree to use travis-ci .com instead of .org.

y-yu commented 3 years ago

We decided to leave from Travis CI for GitHub Actions and it's done by #250 #255 #256.