-
Notifications
You must be signed in to change notification settings - Fork 242
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
Moving the SRA tests to a separate env #1272
Conversation
This comment has been minimized.
This comment has been minimized.
This should fix the breakage of the master branch. |
@@ -7,6 +7,8 @@ | |||
|
|||
import java.io.IOException; | |||
|
|||
//calling this an FTP test so that it could fail in travis | |||
@Test(groups="ftp") | |||
public class EnaRefServiceTest extends HtsjdkTest { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't like labelling this as an FTP test. Maybe instead of a new SRA block we can have an EXTERNAL_APIS test type that covers SRA and ENA.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yfarjoun I think it's a good idea to group the ENA and SRA tests together if they're likely to fail together. Gross to have the ENA server test in FTP since that's just broken forever and has to be removed while the ENA test is potentially valuable.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@yfarjoun One typo and then 👍 Thanks for doing this while I was incommunicado.
Co-Authored-By: yfarjoun <[email protected]>
Description
Please explain the changes you made here.
Explain the motivation for making this change. What existing problem does the pull request solve?
Checklist