Bug 989902 - Compatibility with sqlalchemy 0.8
Summary: Compatibility with sqlalchemy 0.8
Alias: None
Product: Beaker
Classification: Community
Component: general
Version: develop
Hardware: Unspecified
OS: Unspecified
unspecified vote
Target Milestone: 0.14.2
Assignee: Dan Callaghan
QA Contact: Amit Saha
Keywords: Reopened
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-30 07:02 UTC by Amit Saha
Modified: 2018-02-06 00:41 UTC (History)
7 users (show)

Clone Of:
Last Closed: 2013-11-07 01:46:40 UTC

Attachments (Terms of Use)

Description Amit Saha 2013-07-30 07:02:19 UTC
Description of problem:

With sqlalchemy 0.8, number of current database queries break resulting in a large number of errors when the test suite is run: http://ur1.ca/etlrt 

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. Run the test suite on Fedora 19.


Actual results:

Large number of test errors.

Expected results:

All tests pass and the code is also compatible with sqlalchemy 0.7

Additional info:

Comment 2 Dan Callaghan 2013-07-30 07:26:04 UTC
The relevant SQLAlchemy migration guide will be of use too:


Comment 3 Amit Saha 2013-09-17 07:16:52 UTC
Distro import fails too: https://lists.fedorahosted.org/pipermail/beaker-devel/2013-September/000737.html

Comment 4 Dan Callaghan 2013-09-27 03:10:58 UTC

Comment 5 Amit Saha 2013-09-27 04:58:07 UTC
From the release-0.15 branch, ran the tests in bkr.inttest.server.test_model with  python-sqlalchemy-0.8.2-1.fc20.x86_64 and I don't see the failures that was originally reported.

Also, can import a distro successfully on Beaker server 0.15-rc1 running on Fedora.

Comment 6 Nick Coghlan 2013-10-03 02:27:21 UTC
Beaker 0.15 has been released.

Comment 7 Raymond Mancy 2013-10-23 07:02:28 UTC
This change has been nominated to be back ported to the 0.14 branch, to be released as part of the next maintenance release 0.14.2.

Comment 8 Nick Coghlan 2013-10-25 06:35:45 UTC
Adjusting target milestone to make the changes backported to 0.14.2 easier to identify. 0.15.0 has enough significant regressions that it shouldn't be used, so the change means that 0.15.1 can be effectively reidentified as the union of that tag and the 0.14.2 target milestone.

Comment 10 Amit Saha 2013-10-28 14:54:19 UTC
Verified following the same steps as https://bugzilla.redhat.com/show_bug.cgi?id=989902#c5

Comment 11 Nick Coghlan 2013-11-07 01:46:40 UTC
Closing as addressed in Beaker 0.14.2.

Note You need to log in before you can comment on or make changes to this bug.