Test of num_regression user message failing
See original GitHub issuetests/test_num_regression.py:test_common_cases
currently fails when running from a virtual environment on Windows because it produces this message:
data1:
obtained_data1 ... diff
500 1.20000000000000018 ... 0.10000000000000009
While the expected was this one:
data1:
obtained_data1 expected_data1 diff
500 1.20000000000000018 1.10000000000000009 0.10000000000000009
It seems there’s some issue with how pandas
formats the tables.
The weird thing is that the same test passes when run inside our conda
environment.
The test has been marked as xfail
for now.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
doctest — Test interactive Python examples — Python 3.11.1 ...
To perform regression testing by verifying that interactive examples from a test ... This means examples can freely use any names defined at...
Read more >Data mining – Error messages reference - IBM
This error occurs if a stored procedure is called with incorrect values for the model locator or task locator. The column names in...
Read more >Regression tests for the marian-dev repository - GitHub
It can be used to display the differences that cause the test fails. Adding new tests. Use templates provided in tests/_template . Please...
Read more >How to Fix FutureWarning Messages in scikit-learn
You can check your scikit-learn version by running the following code: ... This warning message only affects the use of logistic regression ......
Read more >4. Debugging
particularly regression tests. This avoids (reduces) the introduction of new bugs when debugging. • Testing and debugging need not be done by the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems someone found a solution for a similar problem: https://github.com/pytest-dev/pytest/issues/4030#issuecomment-428705472
Oh that’s cool, wait up I will open the PR.