1. 21 Sep, 2020 1 commit
  2. 07 Sep, 2020 4 commits
  3. 07 Aug, 2020 1 commit
  4. 07 Apr, 2020 2 commits
  5. 06 Apr, 2020 3 commits
  6. 11 Dec, 2019 1 commit
  7. 27 Mar, 2019 1 commit
  8. 20 Feb, 2019 1 commit
  9. 19 Feb, 2019 2 commits
  10. 14 Aug, 2018 1 commit
  11. 13 May, 2018 1 commit
  12. 11 May, 2018 2 commits
  13. 12 Oct, 2017 1 commit
  14. 10 Oct, 2017 1 commit
  15. 07 Oct, 2017 1 commit
  16. 05 Oct, 2017 2 commits
  17. 19 Sep, 2017 1 commit
  18. 13 Sep, 2017 2 commits
  19. 12 Sep, 2017 3 commits
  20. 10 Aug, 2017 3 commits
  21. 09 Aug, 2017 1 commit
  22. 06 Aug, 2017 1 commit
  23. 05 Aug, 2017 1 commit
    • Nat Goodspeed's avatar
      Update build-cmd.sh for more nuanced test builds. · f0986966
      Nat Goodspeed authored
      Encapsulate increasingly sophisticated boilerplate around running library unit
      tests, which we'd been manually synchronizing for three platforms, in a new
      run_tests shell function.
      
      Some Boost libraries have multiple libs/$library/test subdirectories with
      Jamfiles. On encountering those, we used to emit a warning and skip them
      entirely. I was shocked to see that warning for several different libraries in
      a local build: I'd had no idea we weren't running those tests. Rework
      run_tests logic to loop over every libs/$library/test subdirectory with a
      Jamfile.
      
      In fact, rework test logic to generate the list of test subdirectories
      *first*, piping them to the run_tests script, which reads from its stdin. This
      allows the calling logic to use grep -v to eliminate specific problem test
      subdirectories, a finer granularity than skipping all tests for that library.
      (It also allows temporary local edits to engage run_tests for some specific
      test subdirectory while iterating on a failure.)
      
      Eliminate suppress_tests shell function: we now have a more straightforward
      way of bypassing certain specific libraries or tests within libraries.
      
      Introduce sep shell function to produce a separator line within build log
      output to help find particular passages.
      
      Replace deprecated Boost.Coroutine with Boost.Coroutine2.
      f0986966
  24. 24 Oct, 2016 2 commits
  25. 24 Aug, 2016 1 commit