Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • B Bio-DB-HTS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • Bio-DB-HTS
  • Issues
  • #28

Closed
Open
Created Jul 18, 2016 by Marek Szuba@mks

Does Bio-HTS use ENA for CRAM tests?

Created by: andrewyatz

I've seen some odd behaviour running tests on the Ensembl REST API. It seems that travis build failed because of issues with accessing ENA (I've been told this but have not verified the problem). Do we go to ENA for any entries in the CRAM registry or do we always use the locally available FASTA file?

If we do then we should either make it an optional test pending if CRAM registry is available or switch to using a local file system or mock HTTP server using Test::Fake::HTTPD. There's a good example of how to configure it in the Ensembl core test suite for network downloads. Happy to lend a hand

Assignee
Assign to
Time tracking