On Tuesday 18 July 2017, Karel Zak wrote: > On Tue, Jul 18, 2017 at 11:52:36AM +0200, Ruediger Meier wrote: > > On Tuesday 18 July 2017, Karel Zak wrote: > > > I have removed this dates from the test. The things are > > > internally based on time_t (=long) and uint32_t. It does not make > > > sense to use it for huge numbers. > > > > FYI I have created two travis testing branches in my private github > > repo: https://travis-ci.org/rudimeier/util-linux/builds > > > > travis-cc-test > > - testing many different compilers versions, even using > > -Werror - gcc 4.6, 4.8, 5, 6 and 7 > > - clang 3.4, 3.5, 3.9, 4.0 and 5.0 > > - OSX xcode 6.4, 7.3, 8.3 > > > > travis-cc-test > > - testing 32bit build, -m32 -Werror > > Would be possible to enable build by date? I would be nice to run > basic builds tests for each commit and enable some additional > expensive builds for example every 10 days (or/and trigger the build > by git tags, e.g. -rcN). Yep, I will sort that out soon. Maybe creating another project "ul-test" which contains only test scripts. We could add even more checks there without polluting our main repo. The tests should be invoked for interesting tags and once per week or something. To avoid unnecessary noise the extended tests should only run after at least our regular travis check finnished successfully. cu, Rudi -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
