An error occurred fetching the project authors.
  1. 24 Apr, 2020 1 commit
  2. 17 Feb, 2020 2 commits
  3. 02 Feb, 2020 1 commit
    • Jérome Perrin's avatar
      slapos.cookbook/testing: fix missing version pin for mock · 826042a9
      Jérome Perrin authored
      Because we run egg tests with setup.py test, which installs missing
      eggs, if an egg was not installed by buildout, then it installed before
      running test. This was the case for mock, which is now python3 only (
      https://pypi.org/project/mock/4.0.0b1/ ) and we started to see test
      failures.
      
      To solve this issue, refactor the setup definition to use
      extra_requires, which seems to work fine in buildout now. Keep
      test_requires because it's the what `python setup.py test` uses.
      
      Clean buildout profiles to install slapos.cookbook[test] for test
      instead of duplicating the content of test_requires.
      
      /reviewed-on nexedi/slapos!690
      826042a9
  4. 07 Oct, 2019 1 commit
  5. 02 Apr, 2019 1 commit
  6. 21 Jan, 2019 1 commit
  7. 21 Dec, 2018 1 commit
  8. 27 Nov, 2018 1 commit
  9. 26 Nov, 2018 2 commits
  10. 26 Oct, 2018 1 commit
  11. 28 Sep, 2018 1 commit
  12. 30 Aug, 2018 1 commit
  13. 29 Aug, 2018 1 commit
  14. 28 Aug, 2018 1 commit
  15. 13 Aug, 2018 1 commit
  16. 31 Jul, 2018 1 commit
  17. 21 Jul, 2018 1 commit
  18. 18 Jul, 2018 3 commits
  19. 11 Jul, 2018 1 commit
  20. 04 Apr, 2018 1 commit
    • Jérome Perrin's avatar
      slapos-testing: rework to use buildout to install eggs and dependencies · c91c4722
      Jérome Perrin authored
      Instead of letting `python setup.py test` install the depencies, use
      buildout way of installing the eggs.
      
      This software use `interpreter` recipe of `zc.recipe.egg` to install a
      python with all eggs pre-installed. This is a way to get all the
      dependencies at install time instead of getting them at run time from
      pypi when running `python setup.py test`.
      `erp5.util.testsuite` has been extended to support a parameter to
      specify which python interpreter to use.
      
      One issue is that this way of installing eggs by buildout cause chicken
      and egg problem: cloning repository containing `slapos.recipe.cmmi`
      needs git, and to compiling git needs `slapos.recipe.cmmi`.
      The consequence of this is that re-running software will install too
      many parts again.
      One solution for this would be to clone `slapos.recipe.cmmi` with a
      `git` command provided by testnode or system package.
      Another solution would be to not install `slapos.recipe.cmmi` develop
      egg, simply install the egg from it's current pypi version while
      installing the software (running tests will be from the git checkout
      anyway).
      For now this is open issue.
      
      Another point of attention is that `python setup.py test` install the
      requirements listed in `test_requires`, but `zc.recipe.egg` does not
      provide a way of installing these. Some of our packages have `[test]`
      entrypoints, in this case, the software installs the test entrypoints.
      For others, we install the eggs.
      
      Other improvements:
       * use a simple `slapos.recipe:wrapper` instead of `slapos.cookbook:egg_test`
       * fix the typo in repository name erp5-util-repository ->
         erp5.util-repository ( this mean we will have to fix the test suites in
         nexedi ERP5 )
       * document "what is this software" and a scenario of how this software
         can be used to develop slapos eggs.
       * switch to buildout-hash.cfg for easier template hash management.
      c91c4722
  21. 16 Mar, 2018 1 commit
  22. 25 Jan, 2018 1 commit
  23. 11 Dec, 2017 1 commit
  24. 18 Oct, 2017 1 commit
  25. 13 Oct, 2017 1 commit
  26. 03 Jun, 2017 1 commit
  27. 19 May, 2017 3 commits
  28. 04 Nov, 2016 1 commit
  29. 29 Sep, 2016 1 commit
  30. 22 Sep, 2016 1 commit
  31. 05 Aug, 2016 2 commits
  32. 04 Aug, 2016 1 commit
  33. 15 Feb, 2016 1 commit