Some tests in io.votable failing on numpy-dev build
See original GitHub issue@mhvk , are there some changes in Numpy dev that could somehow trigger these? Any advice would be appreciated. Thank you.
Example: https://travis-ci.org/astropy/astropy/jobs/301866406
This one is due to some unexpected change in float precision:
_________________________ test_float_default_precision _________________________
def test_float_default_precision():
config = {'pedantic': True}
field = tree.Field(
None, name='c', datatype='float', arraysize="4",
config=config)
c = converters.get_converter(field, config=config)
> assert (c.output([1, 2, 3, 8.999999], [False, False, False, False]) ==
'1 2 3 8.9999990000000007')
E AssertionError: assert '1 2 3 8.999999' == '1 2 3 8.9999990000000007'
E - 1 2 3 8.999999
E + 1 2 3 8.9999990000000007
astropy/io/votable/tests/converter_test.py:237: AssertionError
These are marked as xfail
on certain condition but that condition did not apply here; However, could these also be a side effect of the same problem that caused the failure above?
_______________________________ test_regression ________________________________
tmpdir = local('/tmp/pytest-of-travis/pytest-0/test_regression0')
@pytest.mark.xfail(str('legacy_float_repr'))
def test_regression(tmpdir):
> _test_regression(tmpdir, False)
astropy/io/votable/tests/vo_test.py:186:
...
# If the lines happen to be different, print a diff
# This is convenient for debugging
for line in difflib.unified_diff(truth, output):
sys.stdout.write(
line.
encode('unicode_escape').
> replace('\\n', '\n'))
E TypeError: a bytes-like object is required, not 'str'
astropy/io/votable/tests/vo_test.py:166: TypeError
_____________________ test_regression_python_based_parser ______________________
tmpdir = local('/tmp/pytest-of-travis/pytest-0/test_regression_python_based_p0')
@pytest.mark.xfail(str('legacy_float_repr'))
def test_regression_python_based_parser(tmpdir):
> _test_regression(tmpdir, True)
astropy/io/votable/tests/vo_test.py:191:
...
astropy/io/votable/tests/vo_test.py:166: TypeError
___________________________ test_regression_binary2 ____________________________
tmpdir = local('/tmp/pytest-of-travis/pytest-0/test_regression_binary20')
@pytest.mark.xfail(str('legacy_float_repr'))
def test_regression_binary2(tmpdir):
> _test_regression(tmpdir, False, 2)
astropy/io/votable/tests/vo_test.py:196:
...
astropy/io/votable/tests/vo_test.py:166: TypeError
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
VOTable XML Handling (astropy.io.votable) — Astropy v5.2
The astropy.io.votable sub-package converts VOTable XML files to and from numpy ... It is also possible to build a new table, define some...
Read more >Installation — Astropy v4.1.dev1654+g499195018 - Read the Docs
The tests should run and print out any failures, which you can report at the Astropy issue tracker. This way of running the...
Read more >(PDF) SunPy—Python for solar physics - ResearchGate
Statistics, The University of Sheffield, Hicks Building, ... test fails, the community is alerted before the code is accepted.
Read more >https://gitweb.gentoo.org/proj/hardened-dev.git/pl...
app-admin/collectd:collectd_plugins_ascent - Build the ascent input ... has some compatibility problems dev-lang/perl:perlsuid - Enable Perl SUID install.
Read more >notags.cgi - UDD - Debian
... libcurator-test-java apache-directory-api libapache-directory-api-java ... badger badger golang-github-dgraph-io-badger-dev bagel bagel baitfisher ...
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
All fixed in #6959, so closing!
The first one is definitely numpy-dev related; see #6824. The bytes vs string thing seems a genuine mistake in the text (and I do think numpy became stricter here). The other two I’d have to look at in more detail; with numpy one can now pass a ‘legacy’ option to
np.set_printoptions
which may be needed…p.s. numpy 1.14 is due fairly soon; I’ll try to get to this later in the week.