New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
travis-ci: Add more recent compilers, small fixes, and Caliper testing #744
Commits on Aug 10, 2016
-
travis-ci: use build matrix instead of custom CC
Use travis.yml matrix.include array to add extra test targets to the matrix, instead of custom CC environment variables.
-
-
-
-
-
-
-
-
-
-
-
travis-ci: enable caliper on clang-3.8 builds
Allow configure ARGS to be modified in travis matrix.include. Somewhat randomly pick clang-3.8 build to add --enable-caliper to ./configure, so we get some compile testing of this code.
-
-
t/t2007-caliper.t: Add simple tests for caliper support
If Flux is configured with --enable-caliper, then attempt to run under `flux start --caliper-profile=thread-trace` and ensure a valid Caliper trace file is emitted.
-
-
travis-ci: use --enable-caliper for coverage testing
So that we run Caliper tests during coverage testing, build with ./configure --enable-caliper during coverage test run in Travis.
-
NEWS: convert to Markdown format
Convert NEWS file to Markdown format, and put dates into ISO 8601 format
-
NEWS: rename official NEWS file NEWS.md
Rename NEWS to NEWS.md so it is rendered as markdown on GitHub, place a pointer to the real NEWS.md file in NEWS.
-
travis-ci: automate GitHub release upload on tags
Setup automated release uploading to GitHub releases via the Travis `deploy` section. Currently, the releases are hard-coded to be a prelease, the prelease boolean should be removed once non-prelease versions of flux-core are being tagged. There is an issue with creating multi-line release "body" (Release Notes) via Travis, so for now, we place a link to the in-tree NEWS.md file, with an anchor to the most recent entry. A condition is set to ensure that we only attempt to deploy from the first job of a Travis build, see `on.condition` in the deploy section. This assumes that TRAVIS_JOB_NUMBER is constructed of the BUILD number and a numeric job number starting at 1.