> I've just checked a few PRs and it seems that the Travis CI is not being run.
> The Appveyor build is running, but I don't think that runs the tests.
Yes, I've noticed this across a few projects (OB, Avogadro, etc.). IMHO, I may
try to migrate directly to GitHub actions to replace Travis.
If
Looking at the link in that tweet you Liked, Geoff, it may be that we need
to transition to the Travis GitHub App, rather than whatever we were doing.
Or are we on that already?
- Noel
On Wed, 8 Apr 2020 at 09:45, Noel O'Boyle wrote:
> I've just checked a few PRs and it seems that the Travis
I've just checked a few PRs and it seems that the Travis CI is not being
run. The Appveyor build is running, but I don't think that runs the tests.
Regards,
- Noel
___
OpenBabel-Devel mailing list
OpenBabel-Devel@lists.sourceforge.net
The InChI code was not working. This has been fixed (by others). Now
there should only be one test failing (and I will work on this now).
Does your dashboard automatically build? I can't see any new test
results.
- Noel
On 20 November 2013 16:14, Noel O'Boyle baoille...@gmail.com wrote:
Ignore
it only builds when commits are made to the acpharis copies of the
repository (because that's the only place I have permissions for adding the
post-commit hooks to github). I merged into master to trigger a new build
and everything passes.
I'll submit my pull request that has the .travis.yml file
Ignore my last question - obviously the answer is on the dashboard. Doh!
- Noel
On 20 November 2013 09:36, Noel O'Boyle baoille...@gmail.com wrote:
Awesome. I am currently in the process of reviving our CDash builds
but the more automated build systems the better.
I've been looking at those
I was interested in having Travis Continuous Integration set up for
openbabel. If you're not familiar, when enabled, each commit to a
repository in github will be built and have the unit tests run
automatically. I believe it will also analyze pull requests, and so on. I
think it also e-mails the
