get_lock doesn't exist, so test depending on it won't work - needs new test system

Bug #315676 reported by Monty Taylor
2
Affects Status Importance Assigned to Milestone
Drizzle
Invalid
Medium
Unassigned

Bug Description

Test concurrent_innodb.test fails because there is no get_lock() to use for synchronization. Until we have either a get_lock replacement or a new test system, the test is unfixable.

Changed in drizzle:
importance: Undecided → Medium
milestone: none → aloha
Revision history for this message
Jay Pipes (jaypipes) wrote :

Monty, setting to Incomplete...is this still a valid bug?

Changed in drizzle:
status: New → Incomplete
Revision history for this message
Jay Pipes (jaypipes) wrote :

This is no longer valid.

Changed in drizzle:
status: Incomplete → Invalid
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.