galaxyproject / galaxyproject/blend4j
Eliminate transient test errors.
- Dominant language
- Java
- Stars
- 16
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
It is becoming increasingly problematic to run Galaxy under sqlite - there are frequent database locking errors that cause failures quite easily. blend4j's travis test architecture should move to Postgres.
Even then there still may be transient errors caused by problems with eggs fetching for instance - it might make sense to move to Jenkins based testing and testing inside a very stable and repeatable Docker container for instance.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or tests. Start by reviewing blend4j's Travis test architecture and how SQLite is configured, then compare the proposed PostgreSQL, Jenkins, and Docker approaches. Done means the test environment is stable, repeatable, and no longer prone to transient database-locking failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, java, postgresql, sqlite
- Domain
- ci-cd, databases, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100