Gitiles
Code Review Sign In
gerrit.cesnet.cz / github / onqtam / doctest / af39baeb80cd994ddcc5a477cf5bdcd94e429194
  1. af39bae Correct format string for unsigned char (#154) by Thomas Bleher · 6 years ago
  2. 04f3798 Correctly document when a main() entry point will be created (#155) by Thomas Bleher · 6 years ago
  3. f3843c4 fixed ussue #147 by onqtam · 6 years ago
  4. 1204486 added reporters link in reference sections by onqtam · 6 years ago
  5. cb6a29f minor stuff by onqtam · 6 years ago
  6. bba24e8 changelog for version 2.0.0 by onqtam · 6 years ago 2.0.0
  7. c734f30 sloppy documentation of the current state of the reporter interface. by onqtam · 6 years ago
  8. f8d5719 version 2.0.0 by onqtam · 6 years ago
  9. 2865aa0 small docs fixes by onqtam · 6 years ago
  10. 8954085 using the .svg files for the logo/icon (and also moved and renamed them) - relates #141 and #145 by onqtam · 6 years ago
  11. 80718be small docs update by onqtam · 6 years ago
  12. a9f53e7 Update README.md by area55 · 6 years ago
  13. 1172609 Add files via upload by area55 · 6 years ago
  14. 25277bb finally resolved issue #126 and #143 "properly" - turns out the problem is this: when using clang from xcode - that means libc++. in that case I include <iosfwd> instead of forward-declaring std::ostream myself. Then if the user includes somewhere only the doctest header and <string> and then does a comparison - then and only then will there be some linker issue which I previously had managed to resolve by telling the users to also include <iostream> in that place in their tests. This is a toolchain issue when using the <iosfwd> header - the details are still not clear to me but I managed to get the linker to pull in what is necessary by adding a dummy unused global function in the implementation of doctest that uses operator<< of std::string to print to std::cout. by onqtam · 6 years ago
  15. d221656 removed the last traces of gcc on osx in travis CI by onqtam · 6 years ago
  16. cec8faa updated numbers for benchmarks by onqtam · 6 years ago
  17. 169d4c8 updated charts for benchmarks by onqtam · 6 years ago
  18. 4d6c853 latest benchmark numbers from linux by onqtam · 6 years ago
  19. 24bd962 benchmarks under windows redone for doctest/catch by onqtam · 6 years ago
  20. 4ab5e6b fixed #143 for real - found the reason for the errors related to the REQUIRE macro not being defined - was disabling exceptions in the feature detection after clang/msvc became non-mutually exclusive. Also detecting if exceptions are disabled for MSVC properly - relates to 44 by onqtam · 6 years ago
  21. b62ecf4 reworked warning suppression macros in order to properly support clang-cl - relates #143 by onqtam · 6 years ago
  22. 8f10044 clang builds should finally be passing now! by onqtam · 6 years ago
  23. 8aecdee oh come on! clang builds - warnings... by onqtam · 6 years ago
  24. 65cf692 builds should pass now... by onqtam · 6 years ago
  25. d9340f5 updates to documentation - relates #4 by onqtam · 6 years ago
  26. a2e77c7 implemented a full example of using doctest in a threaded environment - relates to #4 by onqtam · 6 years ago
  27. 1f2750f documented the thread safety features of doctest - relates #4 by onqtam · 6 years ago
  28. 2d48a31 my previous commit was wrong - the actual problem was that I was supplying -ltsan to all sanitizers - not just tsan - so that is why asan builds were failing by onqtam · 6 years ago
  29. a4d2069 changed order of flags - since that is the only change since the gcc 5-8 tsan builds started failing... by onqtam · 6 years ago
  30. 3c549c9 disabled thread sanitizer for a few clang versions - see these builds: https://travis-ci.org/onqtam/doctest/builds/417926743 by onqtam · 6 years ago
  31. 7a72f31 So I just asked myself: "why...? why are you doing this to yourself? where is the self love" - and now I remove all CI builds on travis with GCC installed with homebrew on Mac OS - life should be a bit better now. Not sure why I did those initially and why it took me 2+ years to figure out that they bring 0 value. Letting go is hard. Only XCode/clang builds on Mac OS from now on. by onqtam · 6 years ago
  32. d9d22d7 removed a no-longer needed include guard and also removing the -ltsan and gold linker for clang on linux for the thread sanitizer - lets see... by onqtam · 6 years ago
  33. b4297f4 fixed #143 for real - had to separate the windows/clang compiler detection since they are not mutually exclusive because of clang-cl... (+ suppressed a clang warning about strtok) by onqtam · 6 years ago
  34. 009691a set the linker to gold for the rest of the GCC sanitizer builds (also clang - even though there I get a segmentation fault and not a linking error) and moved the -ltsan linking flag from all sanitizer builds to only linux builds to fix OSX by onqtam · 6 years ago
  35. 4391967 trying again the thread sanitizers... by onqtam · 6 years ago
  36. f150276 added the gold linker for the sanitizers where needed... I guess that's when a newer than the default GCC is used but ld is not the latest so we need gold by onqtam · 6 years ago
  37. 1ee2d2b lets see if we need the gold linker still for the sanitizers... since these are the only 4 builds that just failed on the CI (god I hate this part of the project development) by onqtam · 6 years ago
  38. e58aa53 removed last reference to 32/64 bitness by onqtam · 6 years ago
  39. 558afbb re-enabled some ASAN options which were problematic a few years ago with old GCC versions (patched since) by onqtam · 6 years ago
  40. 589fd21 removed 32 bit mode builds from travis CI - its about time I simplify my life and make builds faster... 32 bit mode is still checked with VS 2015 and 2017 on appveyor! by onqtam · 6 years ago
  41. dd40fa9 moved the -std=c++0x flag in a single place by onqtam · 6 years ago
  42. 2cd4f08 made the travis config a bit better by onqtam · 6 years ago
  43. 531e9ca suppressing warnings for deprecated declarations such as isatty and fileno when using clang-cl - closes #143 by onqtam · 6 years ago
  44. ae08840 adding -ltsan and also proper TSAN_OPTIONS - relates #4 - lets see if atleast some builds pass... :( by onqtam · 6 years ago
  45. 7b7bb8a windows builds with mingw should pass now by onqtam · 6 years ago
  46. 258aff5 linking the executables for the thread sanitizer as potision independent by onqtam · 6 years ago
  47. 7b7d161 should link properly on linux/osx by onqtam · 6 years ago
  48. 5017768 added thread sanitizer tests - relates #4 by onqtam · 6 years ago
  49. ce1b204 bumping the osx image for gcc 6/7/8 from a no-longer supported xcode 9.3 to the latest by onqtam · 6 years ago
  50. 25fff35 removing asan 64 for osx images with xcode older than 10 - see this build: https://travis-ci.org/onqtam/doctest/builds/417181981 by onqtam · 6 years ago
  51. 10c2018 removing support for xcode 6 and 7 - only 8+ is supported due to the support for thread_local - relates #4 - see this: https://stackoverflow.com/questions/28094794/why-does-apple-clang-disallow-c11-thread-local-when-official-clang-supports by onqtam · 6 years ago
  52. c9b4e1f added an example with concurrent threads doing assertions - relates #4 (currently ctest fails on it...) by onqtam · 6 years ago
  53. 4ca0078 last bit of thread-synchronization done (for the debug output window reporter for windows when attached to a VS debugger) - relates #4 by onqtam · 6 years ago
  54. 2151e3c removed support for GCC 4.7 and VS 2013 ... they have extensions for thread local storage (__thread and __declspec(thread) respectively) but it works only for POD types... relates #4 by onqtam · 6 years ago
  55. 224e167 all CI builds (VS 2013, GCC 4.7) should pass now! Also the other VS builds should pass - doing a normal ostringstream resetting... relates $4 by onqtam · 6 years ago
  56. f03cfd9 made all logging macros thread-safe (and also optimized stringification - no need to allocate streams anymore - reusing a single one) - relates #4 by onqtam · 6 years ago
  57. 09fd51d added xcode10 osx image - https://blog.travis-ci.com/2018-08-16-xcode-10-beta-is-now-available by onqtam · 6 years ago
  58. 7c606ea updating osx build matrix according to this: https://blog.travis-ci.com/2018-07-19-xcode9-4-default-announce by onqtam · 6 years ago
  59. 8bf6dc6 support for VS 15.8 by onqtam · 6 years ago
  60. b170581 docs... non-interesting change by onqtam · 6 years ago
  61. 81d496f calling asserts from different threads spawned from within a single test case is now safe! using the SUBCASE macro in multiple threads will remain a big NO. TODO: logging macros such as INFO() and CAPTURE()... relates #4 and also PR #117 which was a good starting point for this! by onqtam · 6 years ago
  62. 758d092 the last 0 as null usages are gone by onqtam · 6 years ago
  63. 4d87d56 moved to nullptr, removed c++98-compat warning suppressions for clang (also long-long and 0 as null for gcc/clang) by onqtam · 6 years ago
  64. eac6787 tiny changes by onqtam · 6 years ago
  65. 25bfda9 hopefully fixing builds... by onqtam · 6 years ago
  66. 917d79d fixing builds... relates #114 by onqtam · 6 years ago
  67. 8171c48 polished the feature for allowing the use of asserts outside of a testing context (also example and docs) - relates #114 by onqtam · 6 years ago
  68. 6b05c20 disabling output comparison for the playground project by onqtam · 6 years ago
  69. 1d68a13 - added the ability to call asserts outside of a testing context without recompiling! currently the fast asserts are optimized for runtime speed to the maximum but the other asserts are not. Sadly logging macros - like INFO() - aren't supported... yet! - closes #114 - the way to do it is to call setAsDefaultForAssertsOutOfTestCases() on a doctest::Context and optionally to register a custom handler with doctest::Context::setAssertHandler() by onqtam · 6 years ago
  70. 6439abc clearing some flags after each call to the test_case_end function when reentering for subcases by onqtam · 6 years ago
  71. d7360b1 fixing clang builds... by onqtam · 6 years ago
  72. b63d394 no clang 3.3/3.4... by onqtam · 6 years ago
  73. bfc4a01 trying to get clang 3.3 and 3.4 working on travis by onqtam · 6 years ago
  74. fd1a1ea adding back clang 3.3 and 3.4 to the build matrix by onqtam · 6 years ago
  75. fdb8fcc removing the coverage_maxout .cpp file from the coverage report since its been moved to another folder by onqtam · 6 years ago
  76. 3ac4c3f code coverage to the max! by onqtam · 6 years ago
  77. f931b08 removed duplicated function by onqtam · 6 years ago
  78. 1cb49f8 trying to get 2 more clangs builds to pass by onqtam · 6 years ago
  79. 5401630 a bit more cleanup by onqtam · 6 years ago
  80. 981c843 fixing clang builds by onqtam · 6 years ago
  81. 25568b1 bench scripts work for python 3.x - TODO: make it download catch header if not found! by onqtam · 6 years ago
  82. 355b829 compacted some code by onqtam · 6 years ago
  83. 086eb82 fixing builds by onqtam · 6 years ago
  84. 07e5363 compacted namespaces a bit by onqtam · 6 years ago
  85. 42b60db moved implementation details into an anonymous namespace (still inside of doctest but outside of detail - reason for this: not to have 3 namespaces nested into each other, downside: had to use detail in doctest (for convenience) - hope it doesn't break anywhere...) by onqtam · 6 years ago
  86. 3fe13ff fixing builds by onqtam · 6 years ago
  87. 35c9336 went... a LOT further: moved almost all implicitly generated inline special member functions from the fwd part and into impl - compile times dropped even further by some 10% for the header cost by onqtam · 6 years ago
  88. d6e8661 fixing static analysis issues by onqtam · 6 years ago
  89. 732287e this should fix the builds by onqtam · 6 years ago
  90. 54b5bb9 using gcc 8 on appveyor by onqtam · 6 years ago
  91. 2d364b9 moved a bunch of code out of fwd and into impl - should improve compile times (and was a bit easier thanks to c++11 "= default" ) by onqtam · 6 years ago
  92. 493c813 using auto and modern for loops - relates #137 by onqtam · 6 years ago
  93. 4317c82 lets see those builds clean! by onqtam · 6 years ago
  94. eb6f370 directly using override since VS 2010 and GCC 4.6 are dropped! relates #137 by onqtam · 6 years ago
  95. dcdb43c builds should pass now! no more Visual Studio 2010/2012 and Gcc 4.6 - relates #137 by onqtam · 6 years ago
  96. 0c764a7 lets see which compilers are able to build the following code in c++11 mode - here I'm using all features I'm interested in. Based on this I shall update the supported compilers matrix and CI builds... by onqtam · 6 years ago
  97. be46017 using c++11 variadic templates for the templated test cases! relates #137 and #38 by onqtam · 6 years ago
  98. 0cec5b1 further simplification of macros since we always have variadic macros now by onqtam · 6 years ago
  99. 35b94a8 some cleanup of the header by onqtam · 6 years ago
  100. 42fa9c4 damn clang-tidy... see this build for the errors: https://travis-ci.org/onqtam/doctest/jobs/385392164 by onqtam · 6 years ago