-
Notifications
You must be signed in to change notification settings - Fork 2
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
Test build during the week #6
Comments
It seems there are 2 main errors:
|
It looks like SevaHub no longer has any of its public data accessible. I've emailed Angel, but for now let's just take those out of the set of devices that are being tested. With regards to the NCBI imports, have you checked what the difference is? If it's due to NCBI changing what its contents are, then we should just update the file contents to match the current contents. |
I just checked it, it seems that NCBI changed some metadata: https://www.ncbi.nlm.nih.gov/nuccore/JWYZ01000115.1 (I assumed this is the sequence that is being used in the test) |
Yes, looks like the metadata has changed, so please set up a pull request updating to the new metadata. |
Yes, I can see the SevaHub sequences back up again and passing the test! |
That URL isn't necessarily wrong - an SBOL I don't think that's actually where your error actually is, however, since the error you're getting is comparison of the .gb files, and that URL isn't in the .gb file anywhere anyway. You'll need to look at what the actual difference is that's causing the error report. |
Actions are still failing in the develop branch, so I don't think this is done until we get in a PR that fixes this. |
the script got 7 out of 10 parts.
The text was updated successfully, but these errors were encountered: