1. 18 Jan, 2019 2 commits
  2. 17 Jan, 2019 2 commits
  3. 16 Jan, 2019 4 commits
    • Łukasz Nowak's avatar
      seleniumserver: Be catch-all on the frontend · 00fa1f6c
      Łukasz Nowak authored
      The IP used by frontend can be different than the real endpoint, and unknown
      for the frontend itself, so make it catch-all to allow access.
      
      /reviewed-on !497
      00fa1f6c
    • Łukasz Nowak's avatar
      caddy-frontend: Correctly fix prefer-gzip-encoding-to-backend · c1595bae
      Łukasz Nowak authored
      Because of misleading tests (Accept-Encoding with gzip was always set by
      requests, fixed in "caddy-frontend/test: Workaround requests issue with
      Accept-Encoding") the original commit "Fix/caddy frontend prefer gzip type
      zope" did not really fixed the issue for type:zope backend.
      c1595bae
    • Łukasz Nowak's avatar
      caddy-frontend/test: Workaround requests issue with Accept-Encoding · 28b1abe9
      Łukasz Nowak authored
      requests set Accept-Encoding header, but in the testr environment we
      want to have full control over its behaviour, thus not setting any header if
      not really wanted.
      
      As there is not known way to avoid setting the header (skip_accept_encoding is
      internal to httplib) set dummy Accept-Encoding header, which is enough for our
      environment.
      28b1abe9
    • Jérome Perrin's avatar
      Updates on Selenium Server · 9d0de6e9
      Jérome Perrin authored
      Hopefully fix the random failure with:
      
      ```
      test_connect (test.TestSSHServer) ... /srv/slapgrid/slappart3/srv/testnode/byx/soft/a452c8ac557f7eaea3c20f6cc373c390/eggs/paramiko-2.4.2-py2.7.egg/paramiko/client.py:822: UserWarning: Unknown ecdsa-sha2-nistp521 host key for [2001:67c:1254:e:4a::7bd5]:22222: 22c41f5090433152d1e5395a85d6cb4f
        key.get_name(), hostname, hexlify(key.get_fingerprint())
      FAIL
      
      ======================================================================
      FAIL: test_connect (test.TestSSHServer)
      ----------------------------------------------------------------------
      Traceback (most recent call last):
        File "/srv/slapgrid/slappart3/srv/testnode/byx/soft/a452c8ac557f7eaea3c20f6cc373c390/parts/slapos-repository/software/seleniumserver/test/test.py", line 357, in test_connect
          self.assertIn("Welcome to SlapOS Selenium Server.", channel.recv(100))
      AssertionError: 'Welcome to SlapOS Selenium Server.' not found in 'Attempt to write login records by non-root user (aborting)\r\r\n'
      
      ----------------------------------------------------------------------
      ```
      
      Also publish the fingerprint of the server ssh key, which addresses this warning in the correct way (I feel) and since we can publish the fingerprint, why not.
      
      /reviewed-on !492
      9d0de6e9
  4. 14 Jan, 2019 2 commits
  5. 11 Jan, 2019 7 commits
  6. 10 Jan, 2019 7 commits
  7. 09 Jan, 2019 3 commits
  8. 08 Jan, 2019 2 commits
    • Jérome Perrin's avatar
      seleniumserver: try to fix intermitent test failure · 381f49e3
      Jérome Perrin authored
      This seem to be needed "sometimes", apparently on the first connection
      after server is started, but this was not investigated much.
      381f49e3
    • Jérome Perrin's avatar
      component/apache: increase Timeout for direct access case · fce3c74a
      Jérome Perrin authored
      In "direct zope access" ports, the shared frontend is not used, so
      the argument that long timeout consume resources on shared server does
      not apply here.
      
      A timeout of one hour was choosen arbitrarily, a value that should be
      large enough for normal requests and more than the default 60s timeout
      that we hit in the "wait for activities" step when running zelenium
      tests.
      fce3c74a
  9. 07 Jan, 2019 2 commits
    • Jérome Perrin's avatar
      Make BUILDOUT-NEXT test suite use same setuptools version as master again · b2dcbd2f
      Jérome Perrin authored
      In 51740961 we "started testing new version of setuptools" and `BUILDOUT-NEXT` test suite was set to use this `software/buildout-testing/software-next.cfg`.
      
      In !425 we started to depend on very recent setuptools and updated to 40.4.3 .
      
      This `software/buildout-testing/software-next.cfg` kept using this old setuptools and `BUILDOUT-NEXT` test suite failed to build in a loop.
      
      The test suite was already changed to use `software/buildout-testing/software.cfg` (ie. it's same as `BUILDOUT` but testing slapos.buildout's  `next` branch instead of `master` ), so I think this profile is not needed currently.
      
      /reviewed-on !488
      b2dcbd2f
    • Jérome Perrin's avatar
      slaprunner: dynamically guess table names in slapproxy database · 6bae8d66
      Jérome Perrin authored
      Using `software11` breaks now that the version of the database was
      increased in slapos.core!76
      
      /reviewed-on !483
      6bae8d66
  10. 04 Jan, 2019 1 commit
  11. 03 Jan, 2019 1 commit
  12. 02 Jan, 2019 3 commits
  13. 30 Dec, 2018 2 commits
  14. 28 Dec, 2018 2 commits