Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Test failure fudging subdir in `master`

See original GitHub issue

Appears we are running into a test failure in master as evidenced by build. Would be great if we could sort it out.

======================================================================
ERROR: test_metadata_reading (conda_smithy.tests.test_configure_feedstock.Test_fudge_subdir)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/conda-forge/conda-smithy/conda_smithy/tests/test_configure_feedstock.py", line 31, in test_metadata_reading
    meta.parse_again()
  File "/home/travis/conda/lib/python2.7/site-packages/conda_build/metadata.py", line 387, in parse_again
    self.meta = parse(self._get_contents(permit_undefined_jinja), path=self.meta_path)
  File "/home/travis/conda/lib/python2.7/site-packages/conda_build/metadata.py", line 689, in _get_contents
    env.globals.update(context_processor(self, path))
  File "/home/travis/conda/lib/python2.7/site-packages/conda_build/jinja_context.py", line 157, in context_processor
    ctx = get_environ(m=initial_metadata)
  File "/home/travis/conda/lib/python2.7/site-packages/conda_build/environ.py", line 174, in get_dict
    d.update(meta_vars(m))
  File "/home/travis/conda/lib/python2.7/site-packages/conda_build/environ.py", line 274, in meta_vars
    d['PKG_NAME'] = meta.name()
  File "/home/travis/conda/lib/python2.7/site-packages/conda_build/metadata.py", line 453, in name
    sys.exit('Error: package/name missing in: %r' % self.meta_path)
SystemExit: Error: package/name missing in: '/tmp/tmpp_ZDSdrecipe_/meta.yaml'
----------------------------------------------------------------------
Ran 19 tests in 2.768s
FAILED (errors=1)

cc @pelson @msarahan

Issue Analytics

State:
Created 7 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

pelsoncommented, Aug 29, 2016

Woops. That was an easy one 😄 - it is just because the name isn’t defined on a Linux system…

0reactions

pelsoncommented, Aug 31, 2016

All I’m saying is I’d be comfortable with that explanation if it actually failed on that line

Ah, I see. Yes, that is unusual. I don’t have a good mental model for why that would be the case… presumably the multi-parse pass needs the name to be defined from the get-go. 😕

Top Results From Across the Web

Execute all tests in subdirs even if some fail - Stack Overflow

We have found that once one of the subdirectories fails in any test, the subsequent tests in forthcoming subdirectories are not executed and ......

Failing when tests in subfolders - Laracasts

Failing when tests in subfolders. Hello guys,. I have this simple test NewsletterTest.php : Copy Code <?php namespace Tests\Acceptance; use Tests\TestCase; ...

ini configuration are not found in subdirectories when ... - GitHub

When a pytest.ini exists in a subdirectory (i.e. subdir/pytest.ini), it gets picked parsed and used when invoking pytest with pytest subdir ...

run unit tests in subfolder containing the test files - MathWorks

Hello, I have a bunch of test files in a folder and another file that I indicate the runtest command in (the file...