Commits and merges will trigger a CI build for those people who integrate Travis. If BLAKE2 does not have a Travis account, then the tests will not run. It is no big deal because test will run on forks of libb2.
@sneves, you may want to run a personal fork of libb2 and enable Travis on it. This config makes no changes to BLAKE2/libb2, while enabling CI testing for your fork. I use a similar setup for Crypto++. Wei does not have Travis integration, but my personal testing fork has Travis integration.
This commit adds Travis testing.
A sample test report can be found here.
Commits and merges will trigger a CI build for those people who integrate Travis. If BLAKE2 does not have a Travis account, then the tests will not run. It is no big deal because test will run on forks of libb2.
@sneves, you may want to run a personal fork of libb2 and enable Travis on it. This config makes no changes to BLAKE2/libb2, while enabling CI testing for your fork. I use a similar setup for Crypto++. Wei does not have Travis integration, but my personal testing fork has Travis integration.