Since we valgrind only the server by default, failures aren't reported to the user (except in the form of every test timing out). This takes a while, and is also somewhat confusing because the actual error shows up in gssproxy.log; there isn't much useful in the tests themselves.
Check for the presence of valgrind in path before doing environment setup.
Metadata Update from @rharwood: - Issue assigned to rharwood
Opened https://pagure.io/gssproxy/pull-request/234 for this.
Fixed by f59040a
Metadata Update from @rharwood: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.