we need the patch to be able to build with gcc 10 (used on Archlinux for example).
See https://bugs.gentoo.org/705898
patch is coming from https://705898.bugs.gentoo.org/attachment.cgi?id=603950

Otherwise setup_requires in python-dateutil trying to install
the latest version of setuptools_scm and it does not support python2.7.
As the result, fails to install it.

---

INFO networkcache: Downloading pypi-index-96af89cdde216340df5aec1e9a1392e0-python-dateutil==2.7.3...
INFO networkcache: ignored unhandled exception at /srv/slapgrid/slappart6/srv/testnode/dcj/soft/beff23aad53b201b191f995a667eb5f9/eggs/slapos.libnetworkcache-0.15-py2.7.egg/slapos/networkcachehelper.py:106
INFO HTTPError: HTTP Error 404: Not Found
INFO networkcache: Downloading pypi-index-99e2b3234a294248d07c2bb8e6698302-python-dateutil==2.7.3...
INFO networkcache: ignored unhandled exception at /srv/slapgrid/slappart6/srv/testnode/dcj/soft/beff23aad53b201b191f995a667eb5f9/eggs/slapos.libnetworkcache-0.15-py2.7.egg/slapos/networkcachehelper.py:106
INFO HTTPError: HTTP Error 404: Not Found
INFO networkcache: Downloading pypi-index-a46be9bd3756ada5c303353adbb6407f-python-dateutil==2.7.3...
INFO Downloaded http://www.nexedi.org/static/packages/source/slapos.buildout/ from network cache.
INFO networkcache: Downloading pypi-index-23ce7712b6e6cbc7d09787f73e5c3dc5-python-dateutil==2.7.3...
INFO Downloaded https://pypi.org/simple/python-dateutil/ from network cache.
INFO networkcache: Downloading slapos-buildout-a35382ef8370ced1c46d97632a2ec508...
INFO Downloaded https://files.pythonhosted.org/packages/a0/b0/a4e3241d2dee665fea11baec21389aec6886655cd4db7647ddf96c3fad15/python-dateutil-2.7.3.tar.gz#sha256=e27001de32f627c22380a688bcc43ce83504a7bc5da472209b4c70f02829f0b8 from network cache.
INFO Couldn't find index page for 'setuptools_scm' (maybe misspelled?)
INFO No local packages or working download links found for setuptools_scm
INFO error: Could not find suitable distribution for Requirement.parse('setuptools_scm')
INFO An error occurred when trying to install python-dateutil 2.7.3. Look above this message for any errors that were output by easy_install.
INFO While:
INFO   Installing neoppod.
INFO Error: Couldn't install: python-dateutil 2.7.3
ERROR Failed to run buildout profile in directory '/srv/slapgrid/slappart6/srv/testnode/dcj/soft/beff23aad53b201b191f995a667eb5f9'
INFO Finished software releases.

Latest zc.buildout 2.7.1+slapos013 does not need this customisation but old
rojects still need this patch.

See
nexedi/slapos@6e491a6b
nexedi/slapos@f1e7230e

Recent setuptools found a way to install by downloading wheels from PyPI.
But we want to control the versions of all components.

with minimal tests to reproduce the issue that instanciation is broken
when no test runner.

note that we don't put tests in "one big test.py", but from the
beginning we separate so that we can put test for each software type in
test/test_$(software type).py and test for default software type in
test/test_erp5.py

The case where test runner is not enabled got broken in
2a457867

This should fix resiliency tests

/reviewed-on !439

So that we can use
nexedi/slapos.core!51

/reviewed-on nexedi/slapos!438

Golang needs a recent enough version of ld (>2.2) and of gcc ( > 5.5 )

This also introduces multiple gcc versions in gcc component, to have finer control over which component uses which version of gcc.

/reviewed-on nexedi/slapos!436

kumofs does not build with gcc 6

When ld version is too old (Debian 7 comes with version 2.2 which is too
old), golang testsuite fail with:

binutils_test.go:237: SourceLine for main: expect [{main /tmp/hello.c 3}]; got [{main  0}]

see also https://github.com/golang/go/issues/26584

We explicitly use gcc 8.2, but what we need is gcc > 5.5 because of
https://github.com/golang/go/issues/24046
When 8.2 (or newer) becomes the default SlapOS gcc, there should be no
problem in dropping the explicit version and using ${gcc:location} here.

This version is compatible with the default firefox (52)

geckodriver is also required

New software release, selenium server, which expose a http server to which clients can connect using [`webdriver.Remote`](https://selenium-python.readthedocs.io/getting-started.html#using-selenium-with-remote-webdriver) and then use standard webdriver API to control the browser.

The server is made of :
 * the "hub" to which webdriver connects
 * a Xvfb server
 * some nodes, for different browsers:
   * Firefox 52
   * Firefox 60
   * Chrome 69
 * an IPv6 https frontend, exposing the admin interface and the hub. Note that python's webdriver binding before 3.14.0 refuse to connect to a hub with a non verified SSL certificate, so for now clients must either use the published `backend-url` (which is IPv4) or use a version of selenium eggs >= 3.14. In the future we'll see how [caucase](https://lab.nexedi.com/nexedi/caucase/) can solve this. Also, this behavior might also change with future version of selenium, because it's wrong that it does not verify SSL certificates.
 * a ssh server, to which you can connect to establish a ssh tunnel with port forward and register more nodes to the hub. This can be used to connect a browser running on your desktop and see the test running, run unsupported browsers, maybe also [appium](http://appium.io/docs/en/advanced-concepts/grid/) to run tests on mobile. This is a kind of "extra feature" that seems working, but I'm not sure we can support it.

To achieve this, we had to :
  * update Xorg components and build gtk with a X11 gdk backend  to be able to run firefox 60. Updating xorg/gdk also fixed a bug in firefox 52, before this, firefox 52 was not able to get the screen size and ` window.screen.width` was 0. Now firefox 52 can get the screen size properly but resizing window does not work.
  * update chrome 69 and fix a few missing `$LD_LIBRARY_PATH` in the wrapper.

Everything seems working, including taking screenshots, uploading files and resizing window - except resizing window does not work on firefox 52.

See the included test suite for some example usage. Basically it's same as what we're doing today, but instead of:

```python
driver = webdriver.Firefox(path_to_firefox)
```

we use:

```python
driver = webdriver.Remote(
   command_executor='http://127.0.0.1:4444/wd/hub', # the url or backend-url parameter published by the instance.
   desired_capabilities={
      'browserName': 'firefox', # or chrome
      'version': '60', # or don't set a version if you want any version (browserName, on the other hand, is required)
   })
```


/reviewed-on !420

Change jstestnode arguments to accept the [desired capabilities](https://github.com/SeleniumHQ/selenium/wiki/DesiredCapabilities) as a JSON object, so that we can run jstestnode tests on any selenium server ( the target being !420 ), not only saucelabs.

This MR also introduces some JSON schema for instance parameter.

/reviewed-on !429

https://www.theia-ide.org/

/reviewed-on !417

@tomo @rafael if you have any review on this (should be ok as its kind of same commit than last update one, but well)

/reviewed-on nexedi/slapos!433

Improves 57bdf689 by having stored and
expected values stable across runs.

Also assertion is done with {hash} instead its real value, as it has no
meaning to test user.

this is a followup of nexedi/slapos!427

/reviewed-on nexedi/slapos!431

Cloud & Desktop IDE https://www.theia-ide.org/

This version is inspired from "theia-full-docker" from
https://github.com/theia-ide/theia-apps so it includes all extensions.
Many language servers are missing in this version (basically only go,
typescript and python language servers are installed).
PHP extension is not even installed.

Previously it was required to put \ into multi-entry gowork.install,
because the way it was processed was to directly pass it into bash
command, and if \n were there the command was cut by bash and the
trailing was considered as another command.

We can avoid that by explicitly processing \n in gowork.install and
translate it to just ' '. This helps people because now gowork.install
becomes just a regular multiline buildout entry, similar e.g. to
gowork.cpkgpath et all.

Here is one example where it helps:

jerome/slapos@95c45fe0 (comment 68408)

/reviewed-by @jerome
/reviewed-on !430