shard tests are triggering a bus error on sqlite
Issue #1099
resolved
Reproduces regularly on my macbook pro. The actual "Bus error" occurs on line 149 of the shard.py test, this line of code:
t = sess.query(WeatherLocation).get(tokyo.id)
and within that, specifically in query.py on line 1094, when it hits the "asia" shard:
fetch = cursor.fetchall()
a bunch of previous queries in the test work fine. So something is happening to the sqlite connection on the "asia" engine.
Comments (4)
-
reporter -
reporter - changed milestone to 0.5.xx
-
reporter - changed status to resolved
just a double
iter(iter())
call due to a change in the query API, 181424b743ba59ec2b6631b4d914df136757d2fd. -
reporter - removed milestone
Removing milestone: 0.5.xx (automated comment)
- Log in to comment
also, as is frequently my observation with these errors, it's related to "yield". We had a recent change that changed
instances()
to iterate directly instead of calling fromiterate_instances()
. This patch "repairs" the issue (but of course breaks the iterative behavior ofinstances()
):