An error occurred fetching the project authors.
- 02 Dec, 2020 2 commits
-
-
Jérome Perrin authored
in ceb063a4 (software/repman: tests python3 compliance, 2020-10-23), test profile was changed to run on python3 only but this was accidentally reverted in 3a1e5628 (software/slapos-sr-testing: use nxdtest, 2020-10-28), by running repman also on python2. Restore the situation where we run repman only on python3
-
Jérome Perrin authored
The initial intent was to use an interpreter named `python_for_test` and not `python`, so that software do not accidentally pick up this python during compilation. 6033e4fa (software/slapos-sr-testing: fix python3 profile, 2020-12-01) was a quick fix for some python3 compatibility issues discovered after merge, but it was not correct, because by using ${python-interpreter:eggs}, it was installing the default python-interpreter section, which has an interpreter named `python`. This caused issues while building proxysql, which assumes /usr/bin/env python is python2. The fix is to override python-interpreter directly, we don't need another section eggs here.
-
- 01 Dec, 2020 1 commit
-
-
Jérome Perrin authored
It got broken in 3a1e5628 (software/slapos-sr-testing: use nxdtest, 2020-10-28)
-
- 27 Nov, 2020 1 commit
-
-
Jérome Perrin authored
Change to run all tests with python -m unittest, which will allow us to remove workaround for the $PYTHONPATH set by setup.py test. For this we use `[python-interpreter]` which uses pygolang.main to behave like a "normal" python interpreter with eggs available, but without the usual problems of interpreters generated by zc.recipe.eggs - it supports all command line flags and have current directory in sys.path. Tests now have an explicit name, that we set to the software name as before, and the special test dynamically checking all profiles json schemas (part of slapos.cookbook egg, at the root of slapos repository),is named json-schemas. It is also changed to run as default tests in python2 and python3, not only in extras for python2.
-
- 02 Nov, 2020 1 commit
-
-
Léo-Paul Géneau authored
-
- 30 Oct, 2020 1 commit
-
-
Léo-Paul Géneau authored
The only change to support python3 in software/plantuml is the move from hexagonit to slapos download recipe in component/tomcat. We also move the test to python3 by using plantuml egg v0.3.0. As this egg doesn't support python2, the test is not done anymore in Python2.
-
- 26 Oct, 2020 1 commit
-
-
Léo-Paul Géneau authored
Changes configuration files to run repman tests in python3.
-
- 23 Oct, 2020 1 commit
-
-
Jérome Perrin authored
-
- 16 Oct, 2020 1 commit
-
-
Léo-Paul Géneau authored
-
- 28 Sep, 2020 1 commit
-
-
Łukasz Nowak authored
It's useful for some tests to use.
-
- 25 Aug, 2020 1 commit
-
-
Jérome Perrin authored
Since this version introduces a dependency on backports.lzma we had to explicitly install backports.lzma in a slapos compliant way before installing slapos.toolbox, because installing the egg needs xz-utils. For slapos-sr-testing it's also a version up of backports.lzma to 0.14.0
-
- 21 Aug, 2020 1 commit
-
-
Jérome Perrin authored
so that we can simulate running at a later time, to check backups, crontabs etc
-
- 05 Aug, 2020 1 commit
-
-
Jérome Perrin authored
Using an script to set the environment is easier to use, but the main reason is that if we want to be able to use shared part from outer slapos (like when using in theia or slaprunner), the working directory for test must be contained in the instance directory of the outer slapos, so that when we run slapos node prune in the outer slapos this command can see that shared parts are used.
-
- 08 Jul, 2020 1 commit
-
-
Bryton Lacquement authored
-
- 22 Jun, 2020 1 commit
-
-
Łukasz Nowak authored
QUIC is not used at all, and became superseded by HTTP/3
-
- 11 Jun, 2020 1 commit
-
-
Alain Takoudjou authored
-
- 12 May, 2020 1 commit
-
-
Jérome Perrin authored
-
- 07 May, 2020 3 commits
-
-
Gabriel Monnerat authored
PyPDF2 must not overwrite showwarning because it breaks ERP5. ERP5 already overwrites it properly https://github.com/mstamy2/PyPDF2/issues/67#issuecomment-34387142
-
Jérome Perrin authored
fixes 794185d0
-
Jérome Perrin authored
Otherwise it's installed by python setup.py outside of buildout
-
- 28 Apr, 2020 1 commit
-
-
Jérome Perrin authored
-
- 07 Apr, 2020 1 commit
-
-
Jérome Perrin authored
-
- 31 Mar, 2020 1 commit
-
-
Jérome Perrin authored
-
- 24 Mar, 2020 1 commit
-
-
Jérome Perrin authored
-
- 23 Mar, 2020 1 commit
-
-
Jérome Perrin authored
-
- 13 Mar, 2020 1 commit
-
-
Bryton Lacquement authored
-
- 12 Mar, 2020 1 commit
-
-
Romain Courteaud authored
See nexedi/slapos@ea8be7ce
-
- 11 Mar, 2020 1 commit
-
-
Romain Courteaud authored
-
- 10 Mar, 2020 1 commit
-
-
Bryton Lacquement authored
-
- 05 Mar, 2020 1 commit
-
-
Alain Takoudjou authored
-
- 17 Feb, 2020 1 commit
-
-
Bryton Lacquement authored
-
- 05 Feb, 2020 1 commit
-
-
Jérome Perrin authored
/reviewed-on nexedi/slapos!695
-
- 03 Feb, 2020 1 commit
-
-
Jérome Perrin authored
-
- 02 Feb, 2020 1 commit
-
-
Jérome Perrin authored
Because we run egg tests with setup.py test, which installs missing eggs, if an egg was not installed by buildout, then it installed before running test. This was the case for mock, which is now python3 only ( https://pypi.org/project/mock/4.0.0b1/ ) and we started to see test failures. To solve this issue, refactor the setup definition to use extra_requires, which seems to work fine in buildout now. Keep test_requires because it's the what `python setup.py test` uses. Clean buildout profiles to install slapos.cookbook[test] for test instead of duplicating the content of test_requires. /reviewed-on nexedi/slapos!690
-
- 05 Dec, 2019 1 commit
-
-
Jérome Perrin authored
-
- 06 Nov, 2019 2 commits
-
-
Łukasz Nowak authored
-
Łukasz Nowak authored
The test system requires to adapt to changes in slapos.core rapidly, and so it has use the most recent version.
-
- 07 Oct, 2019 1 commit
-
-
Jérome Perrin authored
needed for slapos.testing
-
- 30 Aug, 2019 1 commit
-
-
Alain Takoudjou authored
-
- 28 Aug, 2019 1 commit
-
-
Jérome Perrin authored
-