Misleading error message in lock tests
Bug #1915018 reported by
Karel Pičman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
litmus (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I think that in the error message of getlock method are swapped got and wanted lock types.
if (scope != reslock.scope) {
return FAIL;
}
I'd patch it as follows:
line 86 -- t_context(
line 86 ++ t_context(
To post a comment you must log in.
The attachment "A patch fixing the reported problem." seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]