Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-hive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • 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
  • ensembl-hive
  • Merge requests
  • !139

[GuestLanguage/java] Don't run the tests in the before_install section as they are run by scripts/dev/travis_run_tests.sh

  • Review changes

  • Download
  • Patches
  • Plain diff
Open Marek Szuba requested to merge experimental/maven_test into master Aug 21, 2019
  • Overview 2
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: muffato

Use case

The Java tests are currently run twice: in before_install and in scripts/dev/travis_run_tests.sh. This causes two issues:

  • extra Travis time, which is really precious and should not be wasted
  • The test build will immediately fail and only report the Java error. There could be other errors worth being reported part of the build

Description

Only run the tests in scripts/dev/travis_run_tests.sh (like all the other tests).

Possible Drawbacks

Extra Travis time when the only issue is that the Java wrapper doesn't pass its own tests. But the same could be said of any components. It would make sense to test (and fail early) the critical components, but I don't think the Java wrapper is currently critical.

Testing

Have you added/modified unit tests to test the changes?

N/A

Have you run the entire test suite and no regression was detected?

N/A

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: experimental/maven_test