1. 22 May, 2019 1 commit
  2. 13 Jun, 2018 1 commit
  3. 22 Feb, 2018 4 commits
  4. 21 Feb, 2018 1 commit
  5. 16 Feb, 2018 1 commit
  6. 15 Feb, 2018 1 commit
  7. 14 Feb, 2018 1 commit
  8. 13 Feb, 2018 12 commits
  9. 12 Feb, 2018 6 commits
  10. 09 Feb, 2018 2 commits
  11. 08 Feb, 2018 3 commits
  12. 06 Feb, 2018 3 commits
  13. 05 Feb, 2018 4 commits
    • Kirill Smelkov's avatar
      neotest: Recent util-linux is also needed · 5685a461
      Kirill Smelkov authored
      Similarly to coreutils we need recent util-linux because if e.g. a testnode has
      old version of it its lsblk does not work to what neotest expects, e.g.:
      
      	lsblk: unknown column: REV,SIZE
      5685a461
    • Kirill Smelkov's avatar
      neotest: Recent coreutils are needed to run · c5d0d9fc
      Kirill Smelkov authored
      For example we need realpath and if base os provides only older coreutils there
      is no such utility and neotest fails:
      
      /srv/slapgrid/slappart8/srv/testnode/bct/soft/55158b6a5b027aa40954c3f974d5b3e9/go.work/src/lab.nexedi.com/kirr/neo/go/neo/t/neotest: line 589: realpath: command not found
      
      Fix it by building & hooking into $PATH coreutils by ourselves.
      c5d0d9fc
    • Kirill Smelkov's avatar
      neotest: Actually add instance and teach it to run `neotest bench-local` under... · 41597528
      Kirill Smelkov authored
      neotest: Actually add instance and teach it to run `neotest bench-local` under Nexedi testing infrastructure
      
      Commit 31fe231f (neotest: Draft software-release to run NEO/go & friends
      tests/benchmarks under webrunner) added "neotest" software release, but
      there it added only software supplying - not instantiation - this way
      allowing only manual play with neotest.
      
      Recently @rafael approached me saying that one of my webrunner is red on
      monitoring because "neotest" software inside fails to instantiate, and
      suggested to create a simple instance with bin/runTestSuite inside, so
      that this way neotest could be added to a testnode and run on regular
      basis by our testing infrastructure.
      
      So here it goes - simple instance with only bin/runTestSuite which tries
      to adhere to testnode protocol.
      
      For the actual runTestSuite program I followed the same approach as for
      bin/neotest itself - the main program is not processed via any templates
      and is used as it was pristinely downloaded, and all buildout
      integration is done via first sourcing $SR/neotest-env.sh .
      So bin/runTestSuite inside instance follows this approach.
      
      erp5.util is updated from 0.4.49 to latest 0.4.50 because there were
      backward-incompatible changes in 0.4.50 release (2 @luke: which btw will
      render neoppod and build-rina runTestSuite(s) broken when they try to
      upgrade) and for me it would be a waste of time to later go through
      updating for 0.4.49 -> 0.4.50 API change, so I used the latest release
      right from start.
      
      /cc @Tyagov
      /see also kirr/neo@526491d3
      41597528
    • Kirill Smelkov's avatar
      5b4d3cba