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

Failed testSBOL #132

Open
eyesmo opened this issue Nov 11, 2020 · 3 comments
Open

Failed testSBOL #132

eyesmo opened this issue Nov 11, 2020 · 3 comments

Comments

@eyesmo
Copy link

eyesmo commented Nov 11, 2020

Running in a Colab notebook, most tests worked, but one failed:

sbol.testSBOL()

======================================================================
ERROR: testCopyAndIncrementVersion (sbol.unit_tests.TestCopy)

Traceback (most recent call last):
File "/usr/local/lib/python3.6/dist-packages/sbol/unit_tests.py", line 727, in testCopyAndIncrementVersion
comp_copy = comp.copy()
File "/usr/local/lib/python3.6/dist-packages/sbol/libsbol.py", line 6816, in copy
return _libsbol.ComponentDefinition_copy(self, *args)
RuntimeError: Cannot add http://sbols.org/CRISPR_Example/foo/1.0.0 to Document. An object with this URI already exists. See validation rule sbol-10202.


Ran 52 tests in 0.434s

FAILED (errors=1)

@bbartley
Copy link
Contributor

Hi @eyesmo this is an expected failure on linux systems specifically. This test covers an edge case that you likely won't need to worry about. The library is still safe to use.

@eyesmo
Copy link
Author

eyesmo commented Nov 11, 2020

Good to know, thanks!

@jakebeal
Copy link
Contributor

@bbartley Is there a way that we can mark it as expected failure for linux?

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

3 participants