Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TestCase.shortDescription returns inconsistent output during the execution of a test #826

Open
parautenbach opened this issue Jul 16, 2014 · 4 comments

Comments

@parautenbach
Copy link

I am using Python 2.7.7 as part of the Anaconda 2.0.1 distribution, together with nosetests and the teamcity-messages plugin to execute tests.

As noted in #30 of the teamcity-messages project, different values are returned by shortDescription when invoked in startTest and stopTest respectively via the getTestName helper in the teamcity-messages project, during the execution of a single test.

I've checked the Python project's source code and it seems unlikely to be the cause of this problem.

I'm running nosetests with verbosity set to 2.

@jszakmeister
Copy link
Contributor

I believe this is probably a dupe of #777. Does my cache-short-description fix the issue for you?

@parautenbach
Copy link
Author

Thanks for the feedback. I wasn't aware of that issue (I couldn't find it when searching). Yes, it seems like a duplicate. I will test your code locally. For now, I've made a change to the teamcity-messages project as a workaround. Have you created a pull request that can be integrated into a future release?

As I'm using this in an automated environment, I need to pull from PyPI, and rather avoid patching code manually.

@jszakmeister
Copy link
Contributor

@parautenbach No, I have not yet. In the commit message you can see I was contemplating another approach to the issue, but I haven't had enough "roundtuits" to get to examining the alternate approach.

@jszakmeister
Copy link
Contributor

@parautenbach One option, if you're using pip, might be to make use of pip's Git support--just to help test the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants