1. 05 Nov, 2020 22 commits
    • Léo-Paul Géneau's avatar
      software/helloworld: move to python 3 · 31673681
      Léo-Paul Géneau authored
      31673681
    • Léo-Paul Géneau's avatar
      76cd34d6
    • Kirill Smelkov's avatar
      *: Factor-out NumPy version into component/numpy/ · dc65dcc6
      Kirill Smelkov authored
      Move `numpy=1.16.4` from all over the place into component/numpy.
      Don't move if a different numpy version is used, or it looks like a
      software cares to use exactly particular version.
      Downgrade pygolang/test.cfg from numpy=1.16.6 to numpy=1.16.4 and use
      common numpy component version - using numpy=1.16.6 is not required for
      pygolang testing and so this downgrade is acceptable. It will be better
      to upgrade NumPy to latest in component/numpy/ as a future separate step.
      
      See previous patch where it was decided and explained that version for
      component <X> lives in component/X/.
      dc65dcc6
    • Kirill Smelkov's avatar
      Move dependent egg-versions for added components to stack/slapos.cfg · f52c59c9
      Kirill Smelkov authored
      Move versions for eggs that component/{ZEO,pygolang,zodbtools,pytest}
      depend on out of component/ and into stack/slapos.cfg
      
      Leave version of component <X> inside component/<X>.
      
      I was asked to do so:
      
      nexedi/slapos!839 (comment 119170)
      f52c59c9
    • Kirill Smelkov's avatar
    • Jérome Perrin's avatar
      fixup! gdb: New component · 1b3d2ea9
      Jérome Perrin authored
      I tried to use this gdb in a software release installed by slapos-sr-testing (which perform some extra checks that we only do in slapos-sr-testing at the moment) and it complains that:
      
      ```
      ======================================================================
      ERROR: setUpModule (test)
      ----------------------------------------------------------------------
      Traceback (most recent call last):
        File "/srv/slapgrid/slappart9/srv/slapos/soft/24930952d96110d7e0142b49eba918a8/parts/slapos.core-repository/slapos/testing/testcase.py", line 168, in setUpModule
          installSoftwareUrlList(cls, [software_url], debug=debug)
        File "/srv/slapgrid/slappart9/srv/slapos/soft/24930952d96110d7e0142b49eba918a8/parts/slapos.core-repository/slapos/testing/testcase.py", line 378, in installSoftwareUrlList
          checkSoftware(cls.slap, software_url)
        File "/srv/slapgrid/slappart9/srv/slapos/soft/24930952d96110d7e0142b49eba918a8/parts/slapos.core-repository/slapos/testing/testcase.py", line 336, in checkSoftware
          raise RuntimeError('\n'.join(error_list))
      RuntimeError: /srv/slapgrid/slappart9/srv/slapos/inst/slappart7/tmp/shared/gdb/d14016b094c3637c4ebf6a3df4a8c64d/bin/gdb uses system library /usr/lib/x86_64-linux-gnu/libexpat.so.1.6.8 for libexpat.so.1
      
      ----------------------------------------------------------------------
      Ran 0 tests in 462.686s
      ```
      
      I saw this on a debian KVM on which I don't think I installed any system package except `slapos-node`, but `libexpat1-dev` is installed for some reason, so configure detected it and the built binary is linked against it. I checked some test nodes and `/usr/include/expat.h` seems present on some testnodes, so probably some test nodes will also have this problem. For that, I suggest to build a gdb using slapos `libexpat`, so that we build something more reproductible and not depending on the host system (that's important if we want to use binary cache, but can also be a problem if system packages get remove/upgraded). As you might be thinking now, that's a kind of infinite problem, because we can not add anything that configure might detect, but that's how we usually do for this for now.
      
      While looking at this, I also realised that we were using a .tar.xz URL here, for which rely our recipe will use `xz` command. Because some machines might not have that command, we usually put `xz-utils` in PATH.
      
      How about including something like this ?
      1b3d2ea9
    • Kirill Smelkov's avatar
      wendelin.core: Add way to run tests · eea4467e
      Kirill Smelkov authored
      Just like with pygolang and zodbtools add way to run wendelin.core tests
      via nxdtest with test instance organized with help of stack/nxdtest.cfg
      
      Test agains ZODB4 and ZODB5 for the reasons explained in previous patch.
      
      Wendelin.core already had [wendelin.core-dev], so we only have to add
      test*.cfg in this patch.
      eea4467e
    • Kirill Smelkov's avatar
      zodbtools: Add way to run tests · 8b174431
      Kirill Smelkov authored
      Following approach used for pygolang in the previous patch lets add
      testing support for zodbtools:
      
      - Add zodbtools/buildout-dev.cfg that overrides [zodbtools] to use the
        software from git checkout.
      
      - Add zodbtools/test<X>.cfg that is software-release to create a test
        instance to be run under testnode. To help itself on this task this
        software release uses just-added stack/nxdtest.cfg and
        [python-interpreter] from pygolang, so the code in zodbtools is
        minimal.
      
      Zodbtools can be tested against both ZODB4 and ZODB5 because we still
      use ZODB4 as our primary ZODB version, but it is no longer supported by
      upstream which considers only ZODB5 as current.
      8b174431
    • Kirill Smelkov's avatar
      pygolang: Add way to run tests · dfd5177e
      Kirill Smelkov authored
      - Add pygolang/buildout-dev.cfg that overrides [pygolang] to use the
        software from git checkout.
      
      - Add pygolang/test.cfg that is software-release to create a test
        instance to be run under testnode. This software release uses
        just-added stack/nxdtest.cfg to help itself on this task, so the code
        in pygolang is minimal.
      
      A new section [python-interpreter] is added, because python interpreters
      that zc.recipe.egg generates don't process `-m args` correctly and
      handle subprocess well. I had to workaround that with code from
      gpython.pymain to be able to run `python -m pytest --<pytestarg>` and to
      spawn children processes with preserving sys.path. Comments around and
      inside [python-interpreter] has more details on this topic.
      dfd5177e
    • Kirill Smelkov's avatar
      pytest: New component · db8def43
      Kirill Smelkov authored
      Pytest is used to test wendelin.core, zodbtools and pygolang
      It is also used in component/unstable/pyodide, but currently via pip.
      db8def43
    • Kirill Smelkov's avatar
      stack/nxdtest · 1b806a0d
      Kirill Smelkov authored
      Currently Nexedi takes mostly a copy-paste approach when it comes to
      organizing bin/runTestSuite and an instance to run this inside testnode:
      
          kirr@deco:~/src/wendelin/slapos/slapos-master$ git ls-files |grep runTestSuite
          software/build-rina/runTestSuite.in
          software/buildout-testing/runTestSuite.in
          software/cython-test/runTestSuite.in
          software/erp5testnode/testsuite/deploy-test/runTestSuite.py
          software/jstestnode/runTestSuite.in
          software/neoppod/runTestSuite.in
          software/neoppod/stress-testing/runTestSuite.in
          software/unstable/pyodide/runTestSuite.in
      
      and adding new tests to be run this way will only increase the entropy.
      
      Let's stop this, at least for new tests, and use a uniform approach without copying:
      
      1) I've created nxdtest tool[1] which allows a project to specify in
         declarative way how to test itself: given such declaration nxdtest
         takes on itself the responsibility to communicate with testnode
         master, to drive test commands spawning etc, and leaves to the
         project only semantic part that is specific to the particular
         project.
      
         Nxdtest is based on my go/neo/t/nxd/runTestSuite[2,3] and on the code
         I've seen elsewhere scattered in other runTestSuite.in files.
      
      2) Let's add stack/nxdtest.cfg to SlapOS that provides easy way for a
         software or component to organize testing of itself.
      
      This patch adds stack/nxdtest and migrates software/neotest to use it
      (because stack/nxdtest is based on it and this way it helps to track the
      changes).
      
      In the following patches we will add testing support for pygolang,
      zodbtools and wendelin.core .
      
      [1] https://lab.nexedi.com/kirr/nxdtest/blob/master/nxdtest
      [2] kirr/neo@51b18490
      [3] kirr/neo@f67c147d
      1b806a0d
    • Kirill Smelkov's avatar
      golang: Provide ${go:exe} · 4b72b606
      Kirill Smelkov authored
      ${go:exe} is standalone executable that runs go in activated gowork environment.
      It is handy to use in recipes where one cannot source ${gowork:env} -
      in particular parts with recipe=zc.recipe.egg
      
      Wendelin.core 2 will use `GO=${go:exe}` in its build environment.
      4b72b606
    • Kirill Smelkov's avatar
      49e63d0c
    • Kirill Smelkov's avatar
      wendelin.core: Add pygolang · fddd9237
      Kirill Smelkov authored
      Starting from 0.14 (aka 2) wendelin.core requires pygolang to be present
      both at runtime and at build time.
      fddd9237
    • Kirill Smelkov's avatar
      neotest: v↑ everything *.go · 48e7ef89
      Kirill Smelkov authored
      Update lab.nexedi.com/kirr/neo.git and lab.nexedi.com/kirr/go123 to latest.
      Update all other go packages.
      
      The update puls in the following new dependencies:
      
          github.com/shamaton/msgpack
          github.com/tinylib/msgp
            github.com/philhofer/fwd
            github.com/ttacon/chalk
            golang.org/x/mod
            golang.org/x/xerrors
      
          github.com/davecgh/go-spew
          github.com/pmezard/go-difflib
          gopkg.in/yaml.v3
      48e7ef89
    • Kirill Smelkov's avatar
    • Kirill Smelkov's avatar
      zodbtools: v↑ (0.0.0.dev4 -> 0.0.0.dev8) · a7071493
      Kirill Smelkov authored
      Going from 0.0.0.dev4 to -> 0.0.0.dev8 zodbtools:
      
      - Stabilized `zodb dump` format and layed ground for `zodb restore`;
      - Taught `zodb analyze` to work with any ZODB storage (instead of being
        FileStorage-only tool) and to analyze a particular range of history
        (instead of crunching data for days on a large database);
      - Added `zodb commit` tool that is handy in testing;
      - Added ability to specify tid ranges in human-readable format, as in
        e.g. `zodb analyze data.fs 2018-01-01T10:30:00Z..yesterday`.
      - Progressed on Python3 support.
      
      See https://pypi.org/project/zodbtools/#zodbtools-change-history
      for details.
      a7071493
    • Kirill Smelkov's avatar
      zodbtools: v↑ zodburi (2.3.0 -> 2.4.0) · 3d32576b
      Kirill Smelkov authored
      Close to non-functional change, but removes PendingDeprecationWarning
      about cgi.parse_qsl
      3d32576b
    • Kirill Smelkov's avatar
      pygolang: v↑ (0.0.0.dev4 -> 0.0.7.post1) · 56cb462c
      Kirill Smelkov authored
      0.0.0.dev4 to 0.0.7.post1 goes a long way. See
      https://pypi.org/project/pygolang/#pygolang-change-history for details.
      
      Recent pygolang is needed for wendelin.core 2.
      Zodbtools also uses it starting from v0.0.0.dev5.
      56cb462c
    • Kirill Smelkov's avatar
      f0c0b918
    • Kirill Smelkov's avatar
      98641c5c
    • Kirill Smelkov's avatar
      ZEO: Factor it to separate component · 2e20d7ba
      Kirill Smelkov authored
      We already patch ZEO4 with TCP_NODELAY patch (see 5cf4cf1f "ERP5:
      enable TCP_NODELAY for ZEO") and we will need to backport more patches
      to ZEO4 branch for wendelin.core 2 to work correctly.
      
      It's not only software/neoppod which uses ZEO, and it is not convenient for
      all other software-releases to inherit from neoppod to use correct
      version and build of ZEO egg. For this reason factor out details of ZEO
      egg building into component/ZEO and let users use ${ZEO:egg} where ZEO
      is needed. This way ZEO will be correctly installed for all users.
      
      This patch should be a non-functional change. We switch to
      nexedi/ZEO@5114f909 revision which corresponds to ZEO 4.3.1 +
      TCP_NODELAY.patch
      
      Adding other patches to ZEO4 needed by wendelin.core 2 will be done as a
      separate step.
      2e20d7ba
  2. 02 Nov, 2020 1 commit
  3. 30 Oct, 2020 1 commit
  4. 29 Oct, 2020 5 commits
  5. 28 Oct, 2020 3 commits
  6. 27 Oct, 2020 8 commits