1. 11 Feb, 2020 1 commit
  2. 10 Feb, 2020 9 commits
  3. 07 Feb, 2020 2 commits
    • Jérome Perrin's avatar
      ERP5JS: render before commit · dc02bfa8
      Jérome Perrin authored
      Since 264ded5c in ERP5JS we render the form directly after a successful edit, but this was done sometimes too early, namely, the next form was rendered before interaction workflows and this leads to problems like the ones discussed in nexedi/erp5!982 (comment 92893)
      
      /reviewed-on nexedi/erp5!1040
      dc02bfa8
    • Jérome Perrin's avatar
      knowledge_pad_ui_test: fix a random failure · ed44bee5
      Jérome Perrin authored
      This test click on the delete button which deletes by an ajax request
      and immediatly after open the "wait for activities" page. Sometimes the
      second request starts before the first is committed, so there are no
      activities to wait for.
      
      When using ZServer, we had only one worker thread, so this was not
      visible, but with wsgi we have more than one so it happened sometimes.
      
      Use an old jQuery trick to wait that the first request is no longer in
      flight.
      
      /reviewed-on nexedi/erp5!1038
      ed44bee5
  4. 06 Feb, 2020 3 commits
  5. 05 Feb, 2020 3 commits
  6. 04 Feb, 2020 1 commit
  7. 03 Feb, 2020 5 commits
  8. 31 Jan, 2020 8 commits
  9. 30 Jan, 2020 3 commits
  10. 29 Jan, 2020 5 commits
    • Jérome Perrin's avatar
      calendar: make PresencePeriod support timezone with daylight saving · 5b3f2426
      Jérome Perrin authored
       - update PresencePeriod.getNextPeriodicalDate with fixes from 6155f7ff
       - do not use addToDate, but simply DateTime arithmetics that unlike addToDate, works correctly
      5b3f2426
    • Jérome Perrin's avatar
    • 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.
      325395e8
    • 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.
      35768fa2
    • 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:
      
        srv/
          shared/
            (shared parts to install selenium runner)
          slapos/
            soft/
              (selenium-runner software)
          testnode/
            foo/ # test suite with reference foo
              inst/
                (partitions of tested software)
              shared/
                (shared parts to install tested software)
              soft/
                (tested software)
      
      and in the configuration srv/shared will be set as initial
      shared_part_list.
      
      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
      srv/testnode/foo/shared/.
      
      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.
      316f23c0