1. 04 Jun, 2018 1 commit
    • Jérome Perrin's avatar
      test: Do not check presence of lockfile in /tmp/ to assume Xvfb is running for this display · 056ec4ca
      Jérome Perrin authored
      This caused two problems:
       - If Xfvb was killed and left a stale lock file, we don't reuse this
         display. After some time we end up having "All display locked"
         exception but no Xvfb process running.
       - Xvfb's slapos is patched to store control sockets and lockfiles in
         $TMPDIR ( nexedi/slapos@58462c24 ).
         We don't have $TMPDIR set in testnodes, but this would be a problem
         if we ever set it.
      
      Because Xvfb can detect a stale lock file upon startup and start anyway,
      the easy way running Xvfb for each display and see if it's still running
      after a few seconds.
      056ec4ca
  2. 16 Mar, 2017 1 commit
  3. 07 Mar, 2017 1 commit
  4. 21 Feb, 2017 15 commits
  5. 20 Feb, 2017 3 commits
  6. 18 Feb, 2017 3 commits
  7. 17 Feb, 2017 2 commits
  8. 16 Feb, 2017 3 commits
  9. 15 Feb, 2017 11 commits