I think the message that nix prints when something is blocking the build could be a bit more descriptive. "waiting for locks or build slots" does not indicate whether there is a resource problem that the user needs to go fix (let alone what the resource problem is), or whether the same build is already underway by another process. Even turning the logging up to vomit doens't yield anything particularly insightful.