Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / google-fruit / 1e44d55d4e8264624c1244d5e7e5412dce370a78 / extras
  1. 9f2423a Don't run Boost.DI benchs with Clang 3.6, it doesn't work. by Marco Poletti · 7 years ago
  2. 63e309e When running CI tests, run bazel test with the --test_output=errors flag, so that it reports errors in the log. by Marco Poletti · 7 years ago
  3. aba33ad Add support for list-valued benchmark dimensions in the format_bench_results.py script. by Marco Poletti · 7 years ago
  4. b5d8769 Change fruit_wiki_benchs_fruit.yml to run some benchmarks under more compilers. by Marco Poletti · 7 years ago
  5. 2abc4db Fix a bug in the run_benchmarks.py script that caused some dimensions not to be exported when running a fruit_executable_size benchmark. by Marco Poletti · 7 years ago
  6. 4c5d6d3 Change Travis CI tests to use Ubuntu 17.04 instead of 16.04 and Clang 4.0 instead of 3.9. by Marco Poletti · 7 years ago
  7. 0e7cb0e Add a Dockerfile for Ubuntu 17.04, for CI testing in Travis CI. by Marco Poletti · 7 years ago
  8. ecb092b Update the Dockerfiles used for CI testing on Linux, adding Clang 4.0 and python3-setuptools. by Marco Poletti · 7 years ago
  9. 6ee6dcb No longer test using Ubuntu 15.10, 16.04 has been out for a while now. by Marco Poletti · 7 years ago
  10. e826123 Various updates to the benchmarking code: by Marco Poletti · 7 years ago
  11. cb5c60f Migrate Fruit's end-to-end tests from nose2 to pytest, improving parallelization. by Marco Poletti · 7 years ago
  12. d5191c6 Increase the DH_COMPAT level used for building deb packages to 5 (from 4) and move it to a debian.compat file. by Marco Poletti · 7 years ago
  13. a6ec192 Specify CMAKE_BUILD_TYPE explicitly when building binary packages for Fruit. by Marco Poletti · 7 years ago
  14. 3df0bae Fix 'make install', a path was incorrect. Also start testing 'make install' in Travis CI, to catch this kind of issue sooner the next time. by Marco Poletti · 7 years ago
  15. 2481eed Use the MSVC 2015 image for AppVeyor tests with MinGW, AppVeyor's MSVC 2017 system image doesn't have MinGW ATM. by Marco Poletti · 7 years ago
  16. 7168d34 Add more debug prints to the AppVeyor test script. by Marco Poletti · 7 years ago
  17. 91e9f72 Add more detail to the debug prints in postsubmit.bat. by Marco Poletti · 7 years ago
  18. 1451d77 Add a couple debugging prints to postsubmit.bat, to investigate build failures with MinGW on the MSVC 2017 AppVeyor image. by Marco Poletti · 7 years ago
  19. 56e84d4 Introduce a FRUIT_USES_BOOST CMake flag to allow building Fruit without Boost. by Marco Poletti · 7 years ago
  20. 73940f0 Clean up the AppVeyor config/script now that it works for MinGW, and disable runs with MSVC 2017 for now since that system image doesn't have Boost. by Marco Poletti · 7 years ago
  21. 9a1a6c3 No longer specify explicitly the path to make/gcc/g++ to cmake, when testing in AppVeyor with MinGW. by Marco Poletti · 7 years ago
  22. 4b0c452 More changes to the AppVeyor config/script: by Marco Poletti · 7 years ago
  23. d56b6e6 More changes to the AppVeyor config/script: by Marco Poletti · 7 years ago
  24. f7c3434 postsubmit.bat: retire some no longer useful debug prints and introduce a few new ones. by Marco Poletti · 7 years ago
  25. 59b3a02 Some more changes to the AppVeyor config/script. by Marco Poletti · 7 years ago
  26. d1f189e Add even more debug prints to the AppVeyor scripts, switch from pip to pip3 and put the MinGW binary dir as the end of PATH instead of the beginning. by Marco Poletti · 7 years ago
  27. 4459535 Some changes to the AppVeyor config/script: by Marco Poletti · 7 years ago
  28. d6c59cd Don't expand variables that might contain parentheses in (...) blocks of the AppVeyor script. This confuses CMD.exe. by Marco Poletti · 7 years ago
  29. 1a41f1c Add even more debug prints to the AppVeyor script. Also, consider vcvarsall.bat's execution error non-fatal. by Marco Poletti · 7 years ago
  30. baa1889 Specify vcvarsall.bat's dir instead of the file directly in the AppVeyor config. by Marco Poletti · 7 years ago
  31. 8399370 Add MinGW's bin directory to PATH when testing Fruit with MinGW on AppVeyor. MinGW's GCC fails to start if MinGW is not in PATH. by Marco Poletti · 7 years ago
  32. 0f06c03 Quote variables in the AppVeyor script directly instead of the AppVeyor config, to avoid having quotes where there shouldn't be any (e.g. PATH). by Marco Poletti · 7 years ago
  33. 70a5537 Set PATH to a fixed string in the AppVeyor script, to avoid undesired interference from directories in the default PATH. by Marco Poletti · 7 years ago
  34. db07dbf Fix a string comparison in the AppVeyor script, != is not an allowed operator in Windows batch files. by Marco Poletti · 7 years ago
  35. 6845cfd Various fixes to the AppVeyor config/script: by Marco Poletti · 7 years ago
  36. aeb58f2 Add some more debugging prints in the AppVeyor test script, to investigate an error when running CMake. by Marco Poletti · 7 years ago
  37. 0b31f7e Various improvements to the AppVeyor config/script: by Marco Poletti · 7 years ago
  38. 42a37e1 Try running postsubmit.bat with CALL instead of directly, to see if that works. by Marco Poletti · 7 years ago
  39. 1c6b631 Merge branch 'master' of https://github.com/google/fruit by Marco Poletti · 7 years ago
  40. 8acf626 Change the PATH variable via setx instead of set when running CI tests on Windows. by Marco Poletti · 7 years ago
  41. f3cdac6 Test against Clang 4.0 instead of 3.9 on OS X, now that 4.0 is released. by Marco Poletti · 7 years ago
  42. ac9372d Add an appveyor.xml file for CI with AppVeyor (and a postsubmit.bat script). by Marco Poletti · 7 years ago
  43. 905dc09 Support building Fruit with MSVC. by Marco Poletti · 7 years ago
  44. 81c74e3 Revert a symlink change unadvertently added to the previous commit by Marco Poletti · 7 years ago
  45. dcc51a5 Fix quoting of variables in ifs in CMake files. by Marco Poletti · 7 years ago
  46. 3bff564 Update the Travis CI postsubmit scripts for OS X to use GCC/Clang from the homebrew core tap instead of homebrew/versions (they were moved). by Marco Poletti · 7 years ago
  47. ef78c1f Change OS X Travis CI tests to use Clang 3.7 instead of Clang 3.6 as lowest version. Clang 3.6 is no longer available. by Marco Poletti · 7 years ago
  48. 56c39c6 No longer use travis_wait, since all presubmits now complete in <15 minutes. Removing this means that the log will appear in real time instead of being delayed to the end of the test execution. by Marco Poletti · 8 years ago
  49. 782eed3 (Attempt to) fix the executable path for Clang 3.9 on OS X, it's currently not found (when running tests in Travis CI). by Marco Poletti · 8 years ago
  50. bb54139 Disable Asan in GCC postsubmit tests on OS X. This also no longer works since mid-December due to a change in the Travis CI environment. by Marco Poletti · 8 years ago
  51. c3b083e Test against Clang 3.9 instead of Clang 3.8 in Travis CI. by Marco Poletti · 8 years ago
  52. e58a442 Disable Ubsan in OS X tests with GCC 6, it doesn't work anymore. Something must've changed in the Travis CI environment between 10 December and 22 December causing this combination to start failing (it's not due to a Fruit commit). by Marco Poletti · 8 years ago
  53. 78a6729 Don't use PCHs in postsubmit tests with GCC 4.8. by Marco Poletti · 8 years ago
  54. 190c88a Refactor the postsubmit testing code to allow switching the use of PCHs on/off in each row of the build matrix. by Marco Poletti · 8 years ago
  55. a22c68b When running OS X tests in Travis CI, only install Valgrind if it's actually needed. by Marco Poletti · 8 years ago
  56. 67db7ae Go back to testing against OS X 10.11 in most OS X tests. Valgrind can't (yet) be installed on Sierra. by Marco Poletti · 8 years ago
  57. 713502b Run OS X tests on a more recent version of OS X (except tests for old GCC/Clang versions). by Marco Poletti · 8 years ago
  58. c2bf6ed No longer unconditionally install GCC 4.8 in OS X tests. This takes a long time in recent OS X versions (likely due to a lack of pre-compiled GCC binaries) and causes OS X tests that use recent XCode versions to time out. This will likely break some other tests, that once identified will be fixed in a followup commit. by Marco Poletti · 8 years ago
  59. 7937802 Don't use PCHs in tests if the compiler and GCC and we're testing with the undefined behavior sanitizer. by Marco Poletti · 8 years ago
  60. 4b210eb Test against XCode 8.2 instead of 8.1 now that Travis CI supports it. by Marco Poletti · 8 years ago
  61. 1e45b9c Extend the timout for Travis CI test from 20 to 30min. 20min are often not enough in OS X. by Marco Poletti · 8 years ago
  62. b6e8903 Use travis_wait in all Travis CI commands, to avoid meaningless timeouts. by Marco Poletti · 8 years ago
  63. 51653e7 Use XCode 7.3 instead of 7.1 in Travis CI tests (since Travis CI will retire the 7.1 image in ~1 week) and 8.1 instead of 8 (since that's now available). by Marco Poletti · 8 years ago
  64. 6df80a7 Use extras/bazel_root as WORKSPACE root for Bazel, using symlinks so that Fruit lives under //third_party/fruit instead of //. by Marco Poletti · 8 years ago
  65. 8072dca Re-add support for running e2e Fruit tests with bazel. by Marco Poletti · 8 years ago
  66. e9997dd Add Clang 3.9 to the dockerfiles used for CI testing. by Marco Poletti · 8 years ago
  67. af3ff96 Revert to using Clang 3.8 in OS X tests, the Clang 3.9 tests are failing due to an installation issue. by Marco Poletti · 8 years ago
  68. 51ff15b Stop testing with ASan/UBSan in old Ubuntu versions (in Travis CI). They're unlikely to uncover real problems and they increase the size of the build matrix. by Marco Poletti · 8 years ago
  69. 218458f Test with Clang 3.9 and GCC 6 on OS X, instead of Clang 3.8 and GCC 5. by Marco Poletti · 8 years ago
  70. fe8aa52 No longer test on OS X with clang 3.7 (since we're testing with 3.6 and 3.8) and XCode 7.3 (since we're testing with 7.1 and 8). by Marco Poletti · 8 years ago
  71. 3b4a2ed Run some quick 'smoke tests' at the beginning of the test run in Travis CI, to find most issues sooner. by Marco Poletti · 8 years ago
  72. a1ebbf2 Don't run with ASan/UBSan on OSX with Clang 3.8, it doesn't work. by Marco Poletti · 8 years ago
  73. 7522a33 Disable ASan/UBSan in combinations where they don't work (in Travis CI). by Marco Poletti · 8 years ago
  74. a816ce4 Simplify postsubmit.sh, removing bits that are no longer needed now that there's a single postsubmit.sh run per row in the Travis CI build matrix. by Marco Poletti · 8 years ago
  75. fdb4155 Check in a simple git hook to check that the .travis.yml file is updated. by Marco Poletti · 8 years ago
  76. 92b2a02 Add a comment at the top of .travis.yml to highlight the fact that it was auto-generated. by Marco Poletti · 8 years ago
  77. 0d8c181 Re-add comments on disabled tests that used to be in .travis.yml into extras/scripts/travis_yml_generator.py. Also re-enable a test that was disabled by mistake. by Marco Poletti · 8 years ago
  78. 297a6bb Export the OS env variable in .travis.ci too, the presubmit script expects it. by Marco Poletti · 8 years ago
  79. 116e1da Various changes to the .travis.yml generator: properly export environment variables, run additional tests that were previously commented-out, and make the test name appear in the Travis CI dashboard. by Marco Poletti · 8 years ago
  80. 6938782 Dynamically-generate the .travis.yml file, for increased readability and conciseness. Also split rows of the test matrix to increase parallelization where possible. by Marco Poletti · 8 years ago
  81. e6e9045 Install Clang 3.8 on OSX before testing with it in Travis CI. by Marco Poletti · 8 years ago
  82. 4cf5205 Fix various test failures due to the python test rewrite. by Marco Poletti · 8 years ago
  83. 5498f4f Fix testing dockerfiles for 14.04 and 15.10: the python3-sh package didn't exist at that time, install it via pip instead. by Marco Poletti · 8 years ago
  84. 530c4c0 Various improvements/fixes to the nose-based tests. Notably, adding nose2 to the basesystem dockerfiles used in Travis CI and moved from nose2's multiprocess to running each python file sequentially and relying on ctest's parallelization. by Marco Poletti · 8 years ago
  85. 2d34eac Add an internal YML file with tables that have more detail than the ones in the wiki. by Marco Poletti · 8 years ago
  86. d753167 Add some synthetic dimensions to benchmark results: di_library_git_commit_hash and di_library_version_name, in addition to compiler_name which no longer has special handling. by Marco Poletti · 8 years ago
  87. e4db0ab Add a simple benchmark definition yml file with a single benchmark. by Marco Poletti · 8 years ago
  88. b7fe050 Fix the benchmarking code so that it works with both Fruit <2.1.0 and >=2.1.0. by Marco Poletti · 8 years ago
  89. 5aed85a Add a --continue-benchmarks option to run_benchmarks.py. by Marco Poletti · 8 years ago
  90. 3c07b9f Increase the number of iterations in each loop of the runtime benchmarks by 2.5x, there's too much variance otherwise. by Marco Poletti · 8 years ago
  91. 1559d1f Split the yml file for Fruit and Boost.DI benchmarks so that benchmarks can be easily repeated for new versions of each. by Marco Poletti · 8 years ago
  92. 584a6cd Minor simplification to the benchmark code, using defaultdicts instead of setdefault(). by Marco Poletti · 8 years ago
  93. 0316a00 Reimplement the storage for PartialComponent to: by Marco Poletti · 8 years ago
  94. 26cf514 Add a simple script to find Fruit implementation types without unit tests. by Marco Poletti · 8 years ago
  95. 2b13ff9 Add a script to analyze the symbol size in the generated benchmark code. by Marco Poletti · 8 years ago
  96. b22aceb Use rpath flags for dynamic linking of benchmark code, instead of using LD_LIBRARY_PATH. by Marco Poletti · 8 years ago
  97. dcd6e6e Remove obsolete targets from the BUILD file for benchmarks. by Marco Poletti · 8 years ago
  98. d94b25e Fix a couple remaining issues with the benchmark code and introduce YAML files to configure the tests to run and the tables to produce with the test results. Also improve code quality of benchmarking code. by Marco Poletti · 8 years ago
  99. 1a23d0b Introduce python scripts to run multiple benchmarks and analyze the results. by Marco Poletti · 8 years ago
  100. bc1c7bc Rewrite the benchmark code in python, slightly changing the generated benchmark, and add a Boost.DI benchmark generator. by Marco Poletti · 8 years ago