1. 24 Jun, 2019 3 commits
  2. 19 Jun, 2019 1 commit
  3. 04 Jun, 2019 1 commit
  4. 22 May, 2019 1 commit
  5. 16 May, 2019 1 commit
  6. 17 Apr, 2019 1 commit
  7. 10 Apr, 2019 1 commit
  8. 09 Apr, 2019 1 commit
  9. 27 Mar, 2019 4 commits
  10. 12 Mar, 2019 2 commits
  11. 01 Mar, 2019 2 commits
  12. 11 Jan, 2019 1 commit
  13. 27 Dec, 2018 1 commit
    • stack/erp5: Replicate based on slave_pos, not current_pos · 58caaffc
      The query present in the sql dump sets gtid_slave_pos, which is used by
      slave_pos. current_pos relies on gtid_current_pos, which is not set here
      and hence fails to initiate replication.
      Another (unintended) effect of using slave_pos is that queries run on the
      slave will not break replication. There should be no reason to run queries
      on slave (at least, data & schema modification queries while replication
      is active), so it would seem better to fail the replication immediately in
      order to detect this. So this may not be the best solution - but at least
      this fixes this script.
      Vincent Pelletier committed
  14. 24 Dec, 2018 1 commit
  15. 17 Dec, 2018 1 commit
  16. 11 Dec, 2018 1 commit
  17. 26 Nov, 2018 1 commit
  18. 20 Nov, 2018 2 commits
  19. 19 Nov, 2018 1 commit
  20. 15 Nov, 2018 1 commit
  21. 14 Nov, 2018 5 commits
  22. 17 Sep, 2018 1 commit
  23. 11 Sep, 2018 1 commit
    • erp5: make testrunner access zserver through apache · bddfdad2
      Default behavior of runUnitTest was to listen on `127.0.0.1`/`localhost`, which is not
      allowed for SlapOS instance and caused issues when the used DNS server does not resolve localhost.
      
      Instead, we decided to run the zserver on the partition IP. Because this partition's IP is not seen as a secure origin (as defined in https://goo.gl/Y0ZkNV ) from firefox when running zelenium tests, we also add some entries in apache from balancer partition to act as an https proxy on this zserver and change the testrunners to access the https URL.
      
      See also erp5!729 for the erp5 part.
      
      /reviewed-on !374
      Jérome Perrin committed
  24. 10 Sep, 2018 2 commits
    • erp5: Rework testrunner's HTTP server · 2a457867
      We don't want runUnitTest is to listen on 127.0.0.1, as it is not
      allowed for SlapOS instances, runUnitTest wrapper is extended to include
      `--zserver` with a pre-assigned ip:port.
      
      runTestSuite starts several test in parrallel (controlled by
      `--node_quantity` argument, which is passed by erp5testnode), so we need
      to make sure that we provide it with enough ip:port. For this, we
      extended runTestSuite with a `--zserver_address_list` argument and we
      generate a wrapper with a list of `testrunner.node-count` pre-assigned
      ip:ports.
      
      Because zelenium tests needs to access this zserver over a secure origin
      (otherwise modern browser features such as service worker are not
      available), use an https proxy in the apache from the balancer
      partition.
      
      runUnitTest and runTestSuite have been extended with resp.
      `--zserver_frontend_url` and `--zserver_frontend_url_list` arguments and
      the URLs published by the balancer paritions are set in the wrappers.
      For compatibility reasons, runTestSuite pass parameters as environment
      variables.
      
      Implementation notes:
      
      This introduces a circular depencency, balancer partition needs to know
      the address of the testrunners and zope partitions needs to know the
      URLs of the corresponding http proxies on the apache. This is is handled
      by `slapos.recipe:publish-early`:
      
       1. request zope family with an empty `test-runner-apache-url-list`.
          zope is instanciated a first time.
          zope returns `test-runner-address-list` ( a list of (host, port)
          tuples )
       2. request balancer with `test-runner-address-list`
          balancer is instanciated.
          balancer returns `{{ family_name }}-test-runner-url-list` ( a list
          of apache URLs ), which are published in the root partition.
       3. zope family is re-requested with
          updated`test-runner-apache-url-list` information
      
      instance-erp5.cfg.in template was also reorganised to move
      `[publish-early]` next to `[publish]` at the bottom of the file because
      these sections are semantically related.
      Also test runner generation is moved after zope generation, because we
      want to allocate test runners ports after zopes, otherwise existing
      zopes would get new ports when existing instances are upgraded.
      Jérome Perrin committed
    • erp5: new `test-runner` instance parameter · e4d1ea03
      We have new parameters "how many parallel tests this instance can run"
      ( test-runner.node-count ) and "how many supplementary databases each
      test needs" ( test-runner.extra-database-count ).
      
      Instead of configuring "I need a total of 15 databases", we configure "I
      need to be able to run 3 tests in parallel, each test requiring 4 extra
      databases" which generates 3 * (4 +1) databases.
      
      `mariadb.test-database-amount` becomes deprecated in favour of these new
      arguments, but compatibility is preserved.
      Jérome Perrin committed
  25. 07 Sep, 2018 1 commit
  26. 30 Aug, 2018 2 commits