An error occurred fetching the project authors.
- 13 Dec, 2022 5 commits
-
-
Xavier Thompson authored
-
Xavier Thompson authored
Introduce macro.pythonpath.egg to compute during install the PYTHONPATH of setup eggs required to install other eggs, and insert the PYTHONPATH into the environment section such as used by zc.recipe.egg:custom. Both numpy and scipy use a Python subprocess to call Cython in their setup.py, therefore the setup-eggs option of zc.recipe.egg:custom does not work because sys.path is not propagated to the subprocess.
-
Xavier Thompson authored
-
Ophélie Gagnard authored
-
Ivan Tyagov authored
See merge request nexedi/slapos!1301
-
- 12 Dec, 2022 3 commits
-
-
Martin Manchev authored
-
Romain Courteaud authored
See nexedi/slapos@22cc8e7e
-
Romain Courteaud authored
-
- 08 Dec, 2022 6 commits
-
-
Romain Courteaud authored
See merge request nexedi/slapos!1251
-
Boxiang Sun authored
-
Boxiang Sun authored
-
Boxiang Sun authored
Includes buildout, configuration, test, and resiliency support
-
Ivan Tyagov authored
See merge request nexedi/slapos!1298
-
Martin Manchev authored
-
- 07 Dec, 2022 4 commits
-
-
Boxiang Sun authored
-
Boxiang Sun authored
-
Boxiang Sun authored
Allow ffmpeg to get the correct libvpx path
-
Jérome Perrin authored
Using "Sort Lines Ascending" from Theia or `:'<,'>!sort -f` from vim produce this diff.
-
- 06 Dec, 2022 5 commits
-
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Thomas Gambier authored
See merge request nexedi/slapos!1279
-
Ivan Tyagov authored
See merge request nexedi/slapos!1295
-
Martin Manchev authored
-
- 05 Dec, 2022 5 commits
-
-
Joanne Hugé authored
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Thomas Gambier authored
-
Thomas Gambier authored
-
- 30 Nov, 2022 3 commits
-
-
Joanne Hugé authored
-
Thomas Gambier authored
-
Thomas Gambier authored
This is more coherent with other SR. At some point, we hsould get this file from nginx installation.
-
- 28 Nov, 2022 5 commits
-
-
Joanne Hugé authored
-
Ivan Tyagov authored
See merge request nexedi/slapos!1294
-
Martin Manchev authored
-
Léo-Paul Géneau authored
-
Jérome Perrin authored
depends on nexedi/erp5!1695 See merge request nexedi/slapos!1290
-
- 25 Nov, 2022 2 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 21 Nov, 2022 2 commits
-
-
Jérome Perrin authored
The coverage of an individual test is after all not useful, only the coverage of all tests combined is significant.
-
Jérome Perrin authored
This replaces the broken --coverage argument from runUnitTest, coverage needs to be started earlier and also introduces a coverage plugin to collect coverage data for code in ZODB; python scripts and components are supported. To use on test nodes, set up a web dav server somewhere, configure the instance parameters of the test suite on ERP5 to enable coverage and upload individual results to this webdav server and then combine the coverage data and produce a report, using the bin/coverage script from the software release. For the steps below, it is necessary to change working directory to the root of the software folder. Step 1: combine the coverage data: ./bin/coverage combine \ --keep \ /path/to/all/coverage/files/*coverage.sqlite3 ( using --keep is optional, but it helps in case of mistakes ) Step 2: build an html report: ./bin/coverage html \ --skip-covered \ --omit parts/erp5/product/ERP5/Document/UnitTest.py \ --directory /path/for/html/report/ Note that we want to omit UnitTest.py that is created during test (see testBusinessTemplate.TestDocumentTemplateItem) and get coverage result because it is executed in the test, but it does not exist as a source file in the repository, so we skip it. Of course, to produce a correct html report from a test that have been running on test nodes, it's necessary that the software release used to produce the html report has exactly the same version ans the one that has been running on test nodes. Another simpler, but slower approach is to run all the tests on the same machine, then only running step 2 is necessary.
-