Open kloczek opened 1 year ago
I'm not really following all the details of what you're doing here, but our current test suite does run pretty well in CI. If you can suggest changes to our setup that make it also work in your context, I'd happily accept a PR but I don't think we can spend any cycles on making this particular setup work right now, I'm sorry.
In ticket you have list of modules installed in build env with version. You know the best what could be possible cause that exact unit is failing. I'm asking only to have look on the list of modules, compare that with what you are using and provide kind of expertise what could be worng and/or some advices aboutpossible steps which I can try to perform to expose caue that exacly this unit is failing. Only this and nothing more 😋 To solve the issue you need to know cause ..
If you try running the tests using the requirements.txt
file provided in this repo e.g. here https://github.com/plotly/plotly.py/tree/master/packages/python/plotly/test_requirements you might be able to narrow down the source of the discrepancy.
Just tested 5.14.0. Looks like test suite is ntoot ready for lated numpy
.
Here is pytest output:
Here is list of installed modules in build env
gentle ping .. 🤔
Just tested 5.14.1 and here is update pytest output
After add _plotly_utils/tests/validators/test_integer_validator.py to --ignore list more units are failing
Full pytest log in attachment python-plotly.FAIL.txt
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulescut off from access to the public network
(pytest is executed with-m "not network"
)Looks like something is wring when bumoy 1.24.2 is used. In melow outpu there are as well some deprecation warnings Here is pytest output:
Here is list of installed modules in build env