1. 30 Jul, 2021 1 commit
    • Vincent Pelletier's avatar
      stack/erp5: Make replicating mariadb write to their own binlogs. · 2b1d5b16
      Vincent Pelletier authored
      This change has no effect on stand-alone setups (which is what is
      automatically deployed).
      On setups configured to replicate from another database, it allows them to
      takeover the role of the primary server, which allows rebuilding a
      redundant setup. On such setup, the cost of this option is the extra I/O
      load of binlogs being written to (in addition to the relay log and
      database), and the corresponding disk space use.
  2. 29 Jul, 2021 3 commits
    • Łukasz Nowak's avatar
    • Thomas Gambier's avatar
    • Kirill Smelkov's avatar
      Fix build for zodbtools/pygolang/nxdtest/... tests · 3d6db516
      Kirill Smelkov authored
      Commit 7d1ea024 (version up: zc.buildout 2.7.1+slapos013) switched buildout to
      not use egg wheels, even for wheels that are source-only without any binaries.
      As the result some eggs stopped to install because they setup_require other
      eggs and neither buildout handles setup_requires automatically, nor there is
      explicit setup_require declaration in corresponding components.
      An example of such egg is python-dateutil: it setup_requires setuptools-scm,
      and without switching python-dateutil to zc.recipe.egg:custom with
      setup_requires the build fails.
      The way 7d1ea024 used to workaround this is to mark all such eggs with :whl
      suffix marking them that "it is ok to use wheel for this particular egg". The
      complete list of eggs for which such markings was done in 7d1ea024 is:
      However this list is not really complete because after 7d1ea024 the build
      started to fail for e.g. zodbtools test:
              Traceback (most recent call last):
                File "<string>", line 10, in <module>
                File "/srv/slapgrid/slappart16/srv/testnode/dfp/soft/c670f74c8de08964f63c4b9f7d48c3d1/eggs/setuptools-44.1.1-py2.7.egg/setuptools/command/easy_install.py", line 2321, in main
                File "/srv/slapgrid/slappart16/srv/testnode/dfp/soft/c670f74c8de08964f63c4b9f7d48c3d1/eggs/setuptools-44.1.1-py2.7.egg/pkg_resources/__init__.py", line 786, in resolve
                  raise DistributionNotFound(req, requirers)
              pkg_resources.DistributionNotFound: The 'setuptools-scm' distribution was not found and is required by the application
              An error occurred when trying to install pytest 4.6.11. Look above this message for any errors that were output by easy_install.
                Installing zodbtools-python.
                Base installation request: 'zodbtools[test]'
                  Requirement of zodbtools[test]: mock
                  Requirement of zodbtools[test]: pytz
                  Requirement of zodbtools[test]: freezegun
                  Requirement of zodbtools[test]: pytest
                  Requirement of zodbtools[test]: dateparser
                  Requirement of zodbtools[test]: six
                  Requirement of zodbtools[test]: pygolang>=0.0.0.dev6
                  Requirement of zodbtools[test]: zope.interface
                  Requirement of zodbtools[test]: zodburi
                  Requirement of zodbtools[test]: ZODB
                  Requirement of mock: funcsigs>=1
                  Requirement of mock: six
                  Requirement of freezegun: python-dateutil>=2.7
                Getting distribution for 'pytest==4.6.11'.
              Error: Couldn't install: pytest 4.6.11
      and similarly for pygolang and nxdtest tests.
      I would be more comfortable if the fix would be to teach buildout to either
      handle setup_requires automatically, or to automatically install wheels if the
      wheel is source-only. However, given the way - that 7d1ea024 started to use
      to handle such situations - let's fix this via explicitly marking pytest, and
      other related eggs that setup_require something and are source-only, as :whl.
      NOTE we did not notice the problem earlier because on testnodes, after the
      switch to new buildout, pytest egg was already installed and incremental
      rebuild did not need to reinstall pytest egg. So most of pygolang and zodbtools
      test results remained in "ok" state, and only zodbtools-kirr, that was recently
      reconfigured or changed testnode, indicated this issue. That's why the problem
      remained unnoticed for a long time.
      /reviewed-by @jerome
      /reviewed-on !1026
  3. 28 Jul, 2021 2 commits
  4. 27 Jul, 2021 2 commits
  5. 26 Jul, 2021 2 commits
  6. 23 Jul, 2021 2 commits
  7. 20 Jul, 2021 2 commits
  8. 16 Jul, 2021 2 commits
    • Lisa Casino's avatar
      html5as: update with the new recipe · e6668258
      Lisa Casino authored
    • Kirill Smelkov's avatar
      v↑ tempstorage(ZODB4) 2.12.2 -> 3-nxd · 610bad24
      Kirill Smelkov authored
      In 6e696faa "v↑ tempstorage 2.12.2 -> 5.2(ZODB5) 3-nxd(ZODB4-wc2)" we upgraded
      tempstorage for ZODB5 and ZODB4-wc2, but were careful and left tempstorage,
      that was being used with ZODB4, intact. However @tomo suggests that we should
      also upgrade tempstorage for ZODB4 because of the loadBefore fixes and not to
      further grow divergence in between ZODB4 and ZODB4-wc2:
          I understand that keeping the same version of tempstorage for ZODB 4 is to
          be on the safe side but I'd rather change it to tempstorage4-wc2 anyway. I mean
          we have a bugfix but we are afraid to apply it. Also, The less difference
          between ZODB 4 and ZODB 4-wc2 the better (everything will be more tested this way).
          ( !1009 (comment 137985) )
      -> So let's do that.
  9. 15 Jul, 2021 3 commits
    • Jérome Perrin's avatar
      software/erp5: fix tmpdir in caucase partition · d96b6895
      Jérome Perrin authored
      This was introduced recently, in 0aecb41a (software: Use local tmp for
      caucase, 2021-05-18). This is harmless, but uses a weird-looking directory
    • Jérome Perrin's avatar
      component/tesseract: fix permissions of downloaded traineddata · 7df9bc95
      Jérome Perrin authored
      With the default umask of running slapos node, the default umask create files
      that are only readable by user, not by group:
          slapuser10@COMP-1234:~$ ls -al /opt/slapgrid/bf0ccebdbd76d491bcbe16b7998529b2/parts/tesseract/share/tessdata/
          total 125296
          drwxr-x--- 4 slapsoft slapsoft 4096 Jul 13 05:57 .
          drwxr-x--- 3 slapsoft slapsoft 4096 Jul 13 05:57 ..
          -rw------- 1 slapsoft slapsoft 44366093 Jul 13 05:57 chi_sim.traineddata
          drwxr-x--- 2 slapsoft slapsoft 4096 Jul 13 05:57 configs
          -rw------- 1 slapsoft slapsoft 23466654 Jul 13 05:57 eng.traineddata
          -rw------- 1 slapsoft slapsoft 14213351 Jul 13 05:57 fra.traineddata
          -rw------- 1 slapsoft slapsoft 35659159 Jul 13 05:57 jpn.traineddata
          -rw------- 1 slapsoft slapsoft 10562874 Jul 13 05:57 osd.traineddata
          -rw-r--r-- 1 slapsoft slapsoft 572 Jul 13 05:57 pdf.ttf
          drwxr-x--- 2 slapsoft slapsoft 4096 Jul 13 05:57 tessconfigs
      but when using multiple users, partitions users are members of slapsoft group,
      so these files needs to be group readable.
    • Thomas Gambier's avatar
  10. 13 Jul, 2021 7 commits
  11. 12 Jul, 2021 4 commits
  12. 08 Jul, 2021 7 commits
  13. 06 Jul, 2021 2 commits
    • Jérome Perrin's avatar
      software/{kvm,monitor,caddy-frontend}/test: keep using slapos node instance --all · fe4d60b9
      Jérome Perrin authored
      This softwares have some missing promises, so we keep using slapos node instance
      --all in the test, so that test keep passing after we change standalone slapos
      to not use --all anymore.
    • Jérome Perrin's avatar
      stack/monitor: run monitor-globalstate once from buildout · 8fe8ac61
      Jérome Perrin authored
      monitor-globalstate (which is supposed to create monitor configuration file
      accessed by HTTP as .../public//monitor.global.json) runs by cron every 2
      minutes. This crontab also uses randomsleep to add a delay - but there's a
      promise waiting for this monitor configuration file to be available, so the
      instanciation had to wait for this and if this was sometimes causing problems
      in software release tests because promise did not succeed fast enough.
      To prevent this pattern where slapos node instance has to wait for a crontab
      to be executed, we run that script a first time from buildout.
  14. 02 Jul, 2021 1 commit
    • Xavier Thompson's avatar
      slapos-sr-testing: Add instance parameters to filter what is tested · c2856de1
      Xavier Thompson authored
      The two following instance parameters now exist:
      - `only-sr`: a list of software releases names to test
      - `unittest-args`: a list of arguments for unittest
      By default:
      - all software releases are tested
      - the unittest arguments are ["discover", "-v"]
      Single values are accepted even if they are not in a list.