ORM fixes broke opportunistic testing on py36

Bug #1940460 reported by Dan Smith
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Glance
In Progress
Undecided
Dan Smith

Bug Description

The patch 9e002a77f2131d3594a2a4029a147beaf37f5b17 which is aimed at fixing things in advance of SQLAlchemy 2.0 seems to have broken our opportunistic testing of DB migrations on py36 only. This manifests as a total lockup of one worker during functional tests, which fails to report anything and eventually times out the job.

Revision history for this message
Dan Smith (danms) wrote :

See the rechecks on this patch and the subsequent testing where we first noticed:

https://review.opendev.org/c/openstack/glance/+/804463

The logs aren't very interesting, since they're just a hang and kill by zuul after the timeout.

Dan Smith (danms)
Changed in glance:
status: New → In Progress
assignee: nobody → Dan Smith (danms)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on glance (master)

Change abandoned by "Abhishek Kekane <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/glance/+/805035
Reason: No longer required

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.