1. 28 Dec, 2021 7 commits
  2. 27 Dec, 2021 10 commits
  3. 24 Dec, 2021 8 commits
  4. 23 Dec, 2021 5 commits
  5. 22 Dec, 2021 6 commits
  6. 21 Dec, 2021 3 commits
    • Thomas Gambier's avatar
    • Jérome Perrin's avatar
      pyprog: Wrap entry-point call with sys.exit() · b751603d
      Jérome Perrin authored
      Reading this spec, we probably want to change
      ```
        entry_run = 'from %s import %s; %s()' % (mod, func, func)
      ```
      to
      ```
        entry_run = 'import sys; from %s import %s; sys.exit(%s())' % (mod, func, func)
      ```
      to follow
      https://packaging.python.org/en/latest/specifications/entry-points/#use-for-scripts
      , this is also what `zc.recipe.egg` does.
      
      /reviewed-by @kirr
      /reviewed-on !1108
      b751603d
    • Kirill Smelkov's avatar
      Generalize how nxdtest python script is generated into pyprog recipe macro · 0ee52376
      Kirill Smelkov authored
      In e328aa49 (component/nxdtest: Prepare for nxdtest!13)
      I reworked how nxdtest script is generated and splitted it into nxdtest itself
      and .nxdtest.pyexe python interpreter, so that sys.executable could be used to
      correctly spawn other python scripts:
      
          3) rework how nxdtest script is generated and split it into .nxdtest.pyexe and
             nxdtest itself. .nxdtest.pyexe is python interpreter via which nxdtest is run.
             This interpreter has all eggs required by nxdtest in sys.path, so that
             nxdtest could spawn its trun.py via sys.executable. If we don't care to have
             properly setup sys.executable, trun.py will fail when importing any module that
             nxdtest.py could already successfully import.
      
             Initially I tried to workaround this issue via adjusting $PYTHONPATH <-
             sys.path in main nxdtest script, but @jerome points out that, $PYTHONPATH,
             if set, also affects processes that trun.py spawns, which is not good:
      
             !1095 (comment 146799)
      
             -> so fix this via running nxdtest via environment where sys.executable is
             properly setup python interpreter with path for all eggs that nxdtest has
             access to.
      
             Because we already have half-way workarounds for similar problem in several
             places, and because running a script with correctly setup sys.executable is
             generally better, I would say it should be a good idea to rework
             zc.recipe.egg:scripts to generate all scripts to work this way, but I do not
             want to fight about it.
      
             So let's leave this scheme nxdtest-specific for now.
      
      This patch addresses the last paragraph and provides a general pyprog buildout
      macro that could be used to generate python script for any entry point to run
      with correctly set sys.executable.
      
      /reviewed-by @jerome
      /reviewed-on !1108
      0ee52376
  7. 20 Dec, 2021 1 commit
    • Kirill Smelkov's avatar
      component/nxdtest: v↑ (namespaces, /tmp-on-tmpfs, cancellation) · e45dc8f0
      Kirill Smelkov authored
      This upgrade
      
      - teaches nxdtest to run each testcase with its own /tmp and /dev/shm to
        detect after each test run leaked temporary files, leaked mount
        entries, to isolate different test runs from each other, and to provide
        tmpfs on /tmp for every test.
      
        nexedi/nxdtest!13
      
      - teaches nxdtest to propagate cancellation to spawned test jobs, so
        that whenever user cancels corresponding test run in ERP5 UI, nxdtest
        stops promptly. This should be most useful for long-running tests like
        SlapOS.SoftwareReleases.IntegrationTest-* which before had to be
        waited for for hours to complete even after cancelling test run in ERP5.
      
        nexedi/nxdtest!14
      
      Pytest-mock is added because it becomes dependency to test nxdtest
      itself.
      e45dc8f0