Fridolin Glatter

On my system and on the windows-py3.12 platform here, there is this test failure in `test_base.py`: ```python FAILED ixmp/tests/backend/test_base.py::TestCachingBackend::test_del_ts - AssertionError: assert 0 == 1 E AssertionError: assert 0 ==...

Thanks for the explanation, so I'll revert/drop that commit and try to figure out how `del s` can call `Scenario.__del__` again. One other note: I've searched for other `flaky` markers...

I'm not sure I completely agree with your analysis. The flaky function is called `test_del_ts` and its docstring is `"""Test CachingBackend.del_ts()."""`. However, we don't explicitly call `CachingBackend.del_ts()` in the test...

I'm not sure why `build` couldn't be installed for macos-py3.8, but I don't think that's on us. The error in windows-py3.12 is indeed still flaky and appears to be almost...

The tests seem to be doing okay this time around, but I'm not sure we want to keep the solution. In essence, the problem was that the `JDBCBackend` has a...

Possibly related to #467.

Here's a list of flaky tests I recorded since 11.01.2024: - [ ] `test_py_transport` ```python FAILED ixmp/tests/test_tutorials.py::test_py_transport - nbclient.exceptions.CellExecutionError: An error occurred while executing the following cell: ------------------ # launch...

Since the main branch of this repo hasn't seen an update in two years, I've been looking for an alternative. In my case, I was using something like this: ```python...

@harsanyidani, @agronholm: without knowing more about your error messages, I still found some possibly related issues. Please check: - https://github.com/pytest-dev/pytest/issues/11075 for a possible solution - https://stackoverflow.com/questions/58319619/pytest-request-param-of-fixture-to-be-used-in-tests for another possible solution...

While @harsanyidani provided a crucial part of the error they are getting, it's by no means a full traceback (as is provided in the first related issue I linked above)....