Remove dependency on alembic from testsuite (needed for RHEL)
AbandonedPublic

Authored by jskladan on Nov 4 2016, 7:36 AM.

Details

Summary

It turns out that while they can consume
epel7 builds internally, they can't use epel7 builds while building
rpms. This causes a problem because the resultsdb test suite requires
python-alembic which is epel7 but not rhel7.

Test Plan

Ran testsuite without alembic present. Worked.
Did not try to build the package though - could anyone please try it? Thanks!

Diff Detail

Repository
rRSDB resultsdb
Branch
feature/remove_alembic_dep_from_tests
Lint
Lint ErrorsExcuse: The tables need to be imported so db.create_all() works. No way around it that I know of :(
Unit
No Unit Test Coverage
Build Status
Buildable 901
Build 901: arc lint + arc unit
jskladan retitled this revision from to Remove dependency on alembic from testsuite (needed for RHEL).Nov 4 2016, 7:36 AM
jskladan updated this object.
jskladan edited the test plan for this revision. (Show Details)
jskladan added reviewers: tflink, mkrizek, ralph, ralph2.
mkrizek accepted this revision.Nov 4 2016, 8:29 AM

Builds fine in mock on my machine. LGTM

This revision is now accepted and ready to land.Nov 4 2016, 8:29 AM
tflink added a comment.Nov 4 2016, 1:47 PM

if we ever end up with database upgrade tests, that could be an issue but that's not really something that's going to happen tomorrow.

Unfortunately, we have other epel-exclusive BuildRequires that I'm not sure would be so easy to patch out:

  • python-flask-restful
  • python-flask-sqlalchemy
  • python-iso8601

I keep coming back to the question of whether it would make more sense to just keep an epel7 branch with the fedora packages. I'm not a huge fan of doing that because of the level of responsibility which comes with epel but it might end up being a better choice.

Another option would be to have @ralph2 or @mprahl maintain the epel7 branch of resultsdb if they're willing/interested in taking on that responsibility.

In D1044#19573, @tflink wrote:

Unfortunately, we have other epel-exclusive BuildRequires that I'm not sure would be so easy to patch out:

  • python-flask-restful
  • python-flask-sqlalchemy
  • python-iso8601

*sigh* them epels...

I keep coming back to the question of whether it would make more sense to just keep an epel7 branch with the fedora packages...

What exactly does it mean? In general, and for us specifically?

jskladan abandoned this revision.Nov 22 2016, 8:46 AM