You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Perlmutter, desiutil unit tests fail with the traceback below. Although this looks harmless, it is odd that the loglevel numbers appear to have changed (actually it is odd that is shows up at "2" on Cori, while logging.INFO=20 on both Cori and Perlmutter...). This could potentially mask other real failures if we get used to the idea that desiutil unit tests fail. This particular test will be moot after #190 is merged, but I don't have the cycles to track optional breaking changes at this point so I'm holding off on merging that. Is there a lightweight way we can work around this test failure, e.g. running the test but being agnostic to 2 vs. 20?
=================================== FAILURES ===================================
____________________________ TestSetup.test_version ____________________________
self = <desiutil.test.test_setup.TestSetup testMethod=test_version>
def test_version(self):
"""Test python setup.py version.
"""
path_index = int(sys.path[0] == '')
sys.path.insert(path_index, os.path.abspath('./py'))
package_dir = os.path.join(self.setup_dir, self.fake_name)
os.mkdir(package_dir)
os.mkdir(os.path.join(package_dir, self.fake_name))
os.mkdir(os.path.join(package_dir, '.git'))
setup = """#!/usr/bin/env python
from setuptools import setup
from desiutil.setup import DesiModule, DesiTest, DesiVersion, get_version
CMDCLASS = {{'version': DesiVersion}}
VERSION = get_version("{0.fake_name}")
setup(name="{0.fake_name}",
version=VERSION,
packages=["{0.fake_name}"],
cmdclass=CMDCLASS,
zip_safe=False)
""".format(self)
with open(os.path.join(package_dir, 'setup.py'), 'w') as s:
s.write(setup)
init = """from ._version import __version__
"""
with open(os.path.join(package_dir, self.fake_name,
'__init__.py'), 'w') as i:
i.write(init)
os.chdir(package_dir)
v_file = os.path.join(package_dir, self.fake_name, '_version.py')
with patch('distutils.cmd.Command.announce') as mock_announce:
with patch('distutils.log.info') as mock_info:
self.run_setup('setup.py', ['version'])
self.assertTrue(os.path.exists(v_file))
> self.assertListEqual(mock_announce.mock_calls,
[call('Version is now 0.0.1.dev0.', level=2)])
E AssertionError: Lists differ: [call('Version is now 0.0.1.dev0.', level=20)] != [call('Version is now 0.0.1.dev0.', level=2)]
E
E First differing element 0:
E call('Version is now 0.0.1.dev0.', level=20)
E call('Version is now 0.0.1.dev0.', level=2)
E
E - [call('Version is now 0.0.1.dev0.', level=20)]
E ? -
E
E + [call('Version is now 0.0.1.dev0.', level=2)]
py/desiutil/test/test_setup.py:97: AssertionError
The text was updated successfully, but these errors were encountered:
On Perlmutter, desiutil unit tests fail with the traceback below. Although this looks harmless, it is odd that the loglevel numbers appear to have changed (actually it is odd that is shows up at "2" on Cori, while logging.INFO=20 on both Cori and Perlmutter...). This could potentially mask other real failures if we get used to the idea that desiutil unit tests fail. This particular test will be moot after #190 is merged, but I don't have the cycles to track optional breaking changes at this point so I'm holding off on merging that. Is there a lightweight way we can work around this test failure, e.g. running the test but being agnostic to 2 vs. 20?
The text was updated successfully, but these errors were encountered: