* test: Adapt `test_remove_orphaned` unlinks
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Relax test by only checking for at least two unlinks' presence.
Co-authored-by: Hind-M <70631848+Hind-M@users.noreply.github.com>
* Revert to the commented and previously used value
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* Revert "Revert to the commented and previously used value"
This reverts commit 009f982c54.
---------
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Hind-M <70631848+Hind-M@users.noreply.github.com>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* test: Non-regression test
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* fix: Use penultimate libsolv's log level
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Only run `test_env_spdlog_overhead_regression` on Linux
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Johan Mabille <johan.mabille@gmail.com>
* Add time-out on test and rename conda env
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* Decrease timout to 15 seconds and use dry-run
A dry run takes slightly less than 10 seconds.
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Use bounded value of `output_params.verbosity` as in 1.x
See: https://github.com/mamba-org/mamba/blob/1.x/libmamba/src/core/pool.cpp#L72
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Instead define and use and alternative `set_level`
I was hesitating between the previous solution and
this one (which is not really ideal either) but
which at least does not leak the `Context`.
Friend function could be used but we get this kind of
issue, but I am currently meeting this problem:
https://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#2174
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Revert "Instead define and use and alternative `set_level`"
This reverts commit f1f41b71d0.
* Simply hardcode the verbosity level to 3
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* Increase timeout from 15 to 30 seconds
15 seconds is not sufficient as shown on the CI.
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* From 30 sec to 60 sec
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* DEBUG No timeout
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* test: Remove edge-case for unlinks
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* test: Adapt number of unlinks on Linux
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Assert success
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* docs: Update comments
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* `const`-qualify `level`
* Use 100 seconds for the timeout
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* Use 200 seconds for the timeout
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Adapt according to `1.x`'s behavior
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* fixup! Adapt according to `1.x`'s behavior
* Revert changes to handle CI failures
This is handled by another PR.
See: https://github.com/mamba-org/mamba/pull/3417
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
---------
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
Co-authored-by: Johan Mabille <johan.mabille@gmail.com>
Co-authored-by: Hind Montassif <hind.montassif@gmail.com>
* build: Support fmt 11
A few other elements were required, as observed in:
https://github.com/mamba-org/mamba/pull/3352
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Unpin python on 3.9
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* ci: use libcxx<18 for macOS
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* Add TODO comment
Co-authored-by: Hind-M <Hind-M@users.noreply.github.com>
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
---------
Signed-off-by: Julien Jerphanion <git@jjerphan.xyz>
* All python singletons lifetime are bound to a unique `Context` instance lifetime
In `libmambapy`:
- bound singletons lifetime to the first `Context` instance created
- throw an error if more than one `Context` instance are created at any time
(this only applies to python and will be changed at another time)
- therefore the python user must create a `Context` before using any other functions
This specific change does not (yet) changes the other functions APIs to take
explicitly the `Context` object.
* simplify python expressions
* python API change, added requirement for a `Context` instance
affected functions:
- MultiPackageCache (constructor)
- SubdirData.create_repo
- SubdirIndex.create
- SubdirIndex.download
- clean
- transmute
- get_virtual_packages
- cancel_json_output
* libmamba loggers are now unregistered when Context instance is destroyed
* fixed: dont use `default` as a name
* remove quick-test file
* linter fixes
* Updated documentation
* temptative fix for potential data race in libmamba tests
* libmamba tests: added an assertion to be sure
* linter pass
* fixup libmambatests
* added log for helping understanding ci failure
* review fixes
* Map packages names starting with '_' to match OCI registries rules (and CEP 70)
* Use _go_select instead of _libgcc_mutex in tests
Remove dry-run and check result with umamba_list
* Add doc and micromamba python test
* Add some tests for mirrors
* Use another channel name to avoid interfering with conda-forge
* Add test parameter to use libsolv parser
* Remove dry-run from tests
Hind Montassif