1. 26 Apr, 2018 1 commit
  2. 25 Apr, 2018 1 commit
  3. 24 Apr, 2018 3 commits
  4. 23 Apr, 2018 1 commit
  5. 17 Apr, 2018 3 commits
  6. 16 Apr, 2018 6 commits
  7. 15 Apr, 2018 2 commits
  8. 13 Apr, 2018 2 commits
  9. 12 Apr, 2018 6 commits
  10. 10 Apr, 2018 9 commits
  11. 07 Apr, 2018 1 commit
  12. 06 Apr, 2018 1 commit
  13. 05 Apr, 2018 1 commit
  14. 04 Apr, 2018 3 commits
    • Julien Muchembled's avatar
      096993a3
    • Kazuhiko Shiozaki's avatar
    • Jérome Perrin's avatar
      slapos-testing: use buildout to install eggs · b9f53fc3
      Jérome Perrin authored
      Instead of having running test installing eggs with setuptools during `python setup.py test`, which fails for `caucase` because one of its dependency (namely `cryptography`) cannot be installed so easily, we want to install the dependencies via buildout, using the same installation methods than in the actual software profiles using our eggs.
      
      What I initially believed would be a small change turned out to be a long journey, especially because of using a develop version of `slapos.recipe.cmmi` caused signature changes in the parts installed by this recipe ( `git`, `openssl` etc - some parts that takes a bit of time to install ) so I had to fight with the software being reinstalled each time. Even though the cases which leads to reinstallation are understood (this even involved fixing a bug in buildout nexedi/slapos.buildout!14 ), this is still the case. Some solutions are proposed in the commit message of f4b6eedafd52b0d64f8b2bd1b57c752e02c88a65 , but this reached a state where we can consider first merging with this known problem or discuss ways of improving that before merging if it's considered as blocking. Current state is that it takes one hour to re-install what has to be reinstalled and run the test suite on test runner.
      
      Despite this issue, this approach already improve things, because:
       * `caucase` tests are running (and passing)
       * some `slapos.cookbook` are improved so that they reuse eggs from the buildout and do not install again eggs when the are run.
       *  ... and some other small cleanups
      
      This depends on nexedi/erp5!619 on the `erp5.util` side.
      
      /reviewed-on nexedi/slapos!309
      b9f53fc3