Travis configured on Master, running CI test on a fork

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Travis configured on Master, running CI test on a fork

Jeffrey Walton-3
Hi Everyone,

I believe we have Travis setup on my fork at https://travis-ci.org/noloader/cryptopp/builds/ . The travis.yml is located in Master, so I'm using Crypto++'s configuration.

Its currently testing the following combinations:

  * Linux, GCC, default build
  * Linux, GCC, No ASM
  * Linux, GCC, Asan
  * Linux, GCC, UBsan

  * Linux, Clang, default build
  * Linux, Clang, No ASM
  * Linux, Clang, Asan
  * Linux, Clang, UBsan

  * OS X, Clang, default build
  * OS X, Clang, No ASM
  * OS X, Clang, Asan
  * OS X, Clang, UBsan

Some of the builds fail at the moment, but they do not indicate problems in our code. For example, UBsan fails on Linux under GCC because GCC is 4.8, which predates Undefined Behavior Sanitizer (GCC is too old). I don't know how to detect the compiler version in Travis to schedule/not-schedule the job. Also see https://stackoverflow.com/q/44213719/608639.

If all goes well, then we may ask Wei to enable Travis on his GitHub. Until then we will run it on forks.

Jeff

--
--
You received this message because you are subscribed to the "Crypto++ Users" Google Group.
To unsubscribe, send an email to [hidden email].
More information about Crypto++ and this group is available at http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups "Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Loading...