An error occurred fetching the project authors.
- 07 Oct, 2024 1 commit
-
-
Kazuhiko Shiozaki authored
-
- 23 Sep, 2024 1 commit
-
-
Nicolas Wavrant authored
-
- 06 Sep, 2024 1 commit
-
-
Carlos Ramos Carreño authored
- Each class now correspond to an instance with different configuration, and possibly several test methods. - Upgraded to more recent pypdf version. - The code has been reviewed to reduce complexity and repetition. - Adds documentation to all public functions, in Google style. - Some other cosmetic changes have been made for consistency (consistent parentheses indentation, consistent string literal quotes), courtesy of ruff. See merge request nexedi/slapos!1628
-
- 16 Aug, 2024 1 commit
-
-
Xavier Thompson authored
Test that slapos-testing compiles and instantiates for each Python version (software.cfg, software-py2.cfg, software-py3next.cfg).
-
- 15 Jul, 2024 1 commit
-
-
Jérome Perrin authored
-
- 27 Jun, 2024 1 commit
-
-
Léo-Paul Géneau authored
See !1601
-
- 14 Jun, 2024 1 commit
-
-
Joanne Hugé authored
-
- 12 Jun, 2024 1 commit
-
-
Alain Takoudjou authored
-
- 11 Jun, 2024 2 commits
-
-
Jérome Perrin authored
This brings updates of many dependencies on python3, while mostly keeping the same versions for python2. This enables a new `erp5-py3` test in software/slapos-sr-testing, which should pass already, but with NEO and WCFS being marked as expected failure or skipped for now. This also brings pylint support on python3, which we will be able to reuse in software/slapos-testing. Co-authored-by: Kazuhiko SHIOZAKI <kazuhiko@nexedi.com> Co-authored-by: Arnaud Fontaine <arnaud.fontaine@nexedi.com> Co-authored-by: Bryton Lacquement <bryton.lacquement@nexedi.com>
-
Jérome Perrin authored
-
- 04 Jun, 2024 1 commit
-
-
Xavier Thompson authored
ptyprocess=0.6.0 uses flit as build backend
-
- 03 Jun, 2024 1 commit
-
-
Xavier Thompson authored
-
- 31 May, 2024 1 commit
-
-
Joanne Hugé authored
Some phones with Android 12+ disconnects from 5G networks which don't support IMS. Therefore we add minimal IMS support in this commit (even though we don't actually need it's features). Only Amarisoft >= 2024-05-02 support launching lteims without root privilege, so if Amarisoft version is older IMS is disabled and we inform the user so in the connection parameters. For this to work, SIM cards config needs to be modified, impu and impi must be for instance: impu: 001010000001312, impi: 001010000001312@ims.mnc001.mcc001.3gppnetwork.org
-
- 13 Feb, 2024 1 commit
-
-
Kirill Smelkov authored
As promised add tests for generic enb that exercise enb instantiation with multiple Radio Units and cells in all kind of combinations: FDD|TDD x LTE|NR x SDR|Lopcomm|Sunwave and not only one particular case, but verifying instantiation with many combinations at the same time - verifying how cells of different kinds are handled and how radio units of different kinds are handled too. Using multiple cells on top of several radio units of the same type is verified too. For Lopcomm we also exercise generated cu_config.xml a bit. See added tests for details. Enb/generic tests are bootstrapped now. From now one every fix to enb/generic and every semantic change will go on only if it is accompanied test change or enhancement.
-
- 08 Feb, 2024 1 commit
-
-
Thomas Gambier authored
(cherry picked from commit d1ec306a575f4dd0702aec64873794b4f822cfee)
-
- 01 Feb, 2024 1 commit
-
-
Jérome Perrin authored
-
- 30 Jan, 2024 1 commit
-
-
Kirill Smelkov authored
Current enb config is already quite complex and with MultiRU it will be growing more - both with added features and with more sections emitted because there will be multiple radio units, multiple cells and cross cell interactions. So for clarity we will want to annotate with a comment to which cell or ru object a section belongs, or to which cell-cell pair a particular interaction belongs. Amarisoft supports C-style comments and preprocessor directives out of the box, but if we use them in the configuration files, yaml.load, that we use in the test to load generated configs, will break, because // and /* ... */ is not valid YAML. It looks like Amarisoft does preprocessing as a separate step before further loading given configuration via yaml. So to be able to use the comments and still have tests working we need to do the same - in the tests preprocess the files before feeding them to yaml loader. -> Do that with the help of https://pypi.org/project/pcpp/ In my view that library has good quality and in my experience it worked flawlessly. Anyway we need it to only handle comments, not sophisticated CPP features, and for that it works just ok. Add some comments to existing enb.cfg and ue.cfg to make sure it really works. Those are simple comments, and in current state it they might seem as not 100% necessary, but with more upcoming config changes it would be good to have those descriptionary anchors present in the generated configs, so I suggest we add them. Anyway they should not do any harm at all. /cc @jhuge, @lu.xu, @tomo, @xavier_thompson, @Daetalus /proposed-for-review-on nexedi/slapos!1526 /reviewed-by TrustMe
-
- 13 Dec, 2023 1 commit
-
-
Jérome Perrin authored
on python3 we use lzma directly
-
- 19 Oct, 2023 1 commit
-
-
Jérome Perrin authored
Some configure scripts, such as cmake's FindPython3, use explicit python version such as python3.9 and can find system python, although using python3 would be catched by the disabled python. With this change we also catch attempt of using python3.9 We also print the executed command, it helps guessing what executed python
-
- 16 Oct, 2023 1 commit
-
-
Jérome Perrin authored
previous patch - 24f5a96c (software/slapos-sr-testing: disallow usage of system python3, 2023-10-02) - was incorrect, an `entry-point` is required for a script to be generated.
-
- 02 Oct, 2023 1 commit
-
-
Jérome Perrin authored
We had a mechanism to catch usage of system python2, but using not for system python3, which cause the same kind of problems.
-
- 17 May, 2023 2 commits
-
-
Joanne Hugé authored
-
Joanne Hugé authored
-
- 17 Apr, 2023 2 commits
-
-
Łukasz Nowak authored
It's fetched from the upstream repository with well known working revision.
-
Łukasz Nowak authored
-
- 01 Feb, 2023 1 commit
-
-
Thomas Gambier authored
-
- 31 Jan, 2023 1 commit
-
-
Léo-Paul Géneau authored
-
- 24 Jan, 2023 2 commits
-
-
Boxiang Sun authored
-
Thomas Gambier authored
See merge request nexedi/slapos!1329
-
- 18 Jan, 2023 1 commit
-
-
Justin authored
-
- 10 Jan, 2023 1 commit
-
-
Thomas Gambier authored
-
- 09 Jan, 2023 1 commit
-
-
Łukasz Nowak authored
It's based on phased out caddy-frontend, especially as next step is to drop Caddy software from the software release.
-
- 02 Jan, 2023 1 commit
-
-
Martin Manchev authored
-
- 08 Dec, 2022 1 commit
-
-
Boxiang Sun authored
-
- 10 Nov, 2022 1 commit
-
-
Jérome Perrin authored
Put broken python interpreters in path so that fail if they try to use system python
-
- 17 Oct, 2022 1 commit
-
-
Jérome Perrin authored
-
- 12 Sep, 2022 1 commit
-
-
Jérome Perrin authored
mostly packages with known vulnerabilities or causing failures/warnings in the tests. This also cleanup duplicates version definitions, sometimes the test profiles overloaded some versions from stack/slapos.cfg
-
- 07 Sep, 2022 1 commit
-
-
Jérome Perrin authored
Now that all the problems of running a different version of python in slapos-node and within the software and now that slapos-node always run on python3, we no longer need to have two separate test softwares and two separate suites for python2 and python3 - we have one test suite for all our softwares, regardless of the python version used by these softwares and this test suite use python3 to run the tests code and to run slapos-node
-
- 06 Sep, 2022 1 commit
-
-
Jérome Perrin authored
-
- 02 Sep, 2022 1 commit
-
-
Boxiang Sun authored
-