1. 09 Nov, 2021 2 commits
  2. 27 Sep, 2021 1 commit
  3. 17 Aug, 2021 2 commits
  4. 17 Jun, 2021 1 commit
  5. 15 Jun, 2021 1 commit
  6. 14 Jun, 2021 1 commit
  7. 10 Jun, 2021 1 commit
  8. 03 Dec, 2020 1 commit
  9. 17 Nov, 2020 3 commits
  10. 27 Oct, 2020 2 commits
    • Jérome Perrin's avatar
      testnode: advertise log URL with log_frontend_url · daf3d133
      Jérome Perrin authored
      testnode use to publish the URL of logs so that Nexedi ERP5 can
      display link to "view logs". This URL was an IPv6 URL on a certificate
      which does not validate.
      Now testnode software release request a shared frontend for these
      logs and generate a config file with log_frontend_url set.
      testnode now advertise the URL of log using the log frontend url
      from config.
      Also simplify frontend_url key to manage it using the same way.
    • Jérome Perrin's avatar
      testnode: pass arguments as environment variables · fcbdb89b
      Jérome Perrin authored
      introduced recently, they are passed to runTestSuite using the usual
      way of running runTestSuite once with --help to inspect supported
      arguments and passing the argument only if runTestSuite supports them,
      but these arguments are not necessarily heavy to compute and are always
      known (unlike for example firefox path which is only known if seleniumrunner
      extra software was installed), so simplify all this by passing the
      parameters are environment variables.
  11. 15 Sep, 2020 1 commit
    • Jérome Perrin's avatar
      testnode: propagate test_node_title to runTestSuite · e17936a4
      Jérome Perrin authored
      runTestSuite accept a --test_node_title argument, which is used in
      createTestResult API call, so that task distributor can keep track of which
      node executed which task, but since it was not passed, we did not know which
      test node executed which test result line.
  12. 19 May, 2020 5 commits
  13. 14 May, 2020 3 commits
  14. 30 Apr, 2020 1 commit
  15. 27 Apr, 2020 6 commits
  16. 29 Jan, 2020 3 commits
    • Jérome Perrin's avatar
      Eggtest: support --shared_part_list · 325395e8
      Jérome Perrin authored
      Shared parts received from test node will be passed as
      SLAPOS_TEST_SHARED_PART_LIST environment variable to egg tests.
      This will be useful for SLAPOS-SR tests.
    • Jérome Perrin's avatar
      testnode: pass shared_part_list to runTestSuite who understand it · 35768fa2
      Jérome Perrin authored
      Some test suites who install software during the test, such as SLAPOS-SR
      tests, could benefit from reusing already installed shared parts.
      The convention is that --shared_part_list is a os.pathsep (:) separated
      list of paths of read-only shared parts in which the test is not allowed
      to write.
    • Jérome Perrin's avatar
      testnode: SlapOS shared parts support · 316f23c0
      Jérome Perrin authored
      Shared parts speed up compilation time and is becoming the standard in
      SlapOS software installations, so it makes sense to use it in our test
      nodes, as it also gives one more opportunity to test this feature.
      erp5testnode configuration file supports a new shared_part_list option,
      that can be set to a \n separated list of paths to use for shared parts,
      following the same rules as slapos.core and slapos.recipe.cmmi (ie. the
      first ones are read-only and the last one is read-write).
      This shared_part_list option will be set in slapos.cfg used to compile
      both the "software for testnode" (ie. selenium-runner) and later the
      softwares under tests.
      The software under tests will also use a local directory for each test
      suite to install shared suite.
      The directory structure is now:
            (shared parts to install selenium runner)
              (selenium-runner software)
            foo/ # test suite with reference foo
                (partitions of tested software)
                (shared parts to install tested software)
                (tested software)
      and in the configuration srv/shared will be set as initial
      When installing selenium-runner, srv/shared/ is used to write shared
      parts. These shared parts are never removed.
      When installing software under test, srv/shared/ and
      srv/testnode/foo/shared/ are used. If parts are found in srv/shared they
      are used, if they are not found, they are installed in
      In practice, this should mean that the shared parts installed by
      selenium-runner will be reused for all tested softwares and this should
      speed up initial installation of these softwares.
      Currently, nothing is implemented regarding removal of unused shared
      parts, but in our case:
       - srv/testnode/foo/shared/ will be removed when "foo" is removed.
       - srv/shared/ should be used only when installing selenium-runner.
      If this starts to use too much disk space, one quick and dirty
      workaround could be to destroy the test node instance and re-create it.
  17. 26 Nov, 2019 1 commit
  18. 21 Nov, 2019 1 commit
  19. 25 Oct, 2019 1 commit
  20. 23 Oct, 2019 1 commit
  21. 14 Oct, 2019 1 commit
  22. 10 Oct, 2019 1 commit