Yes. If there is something clearly wrong with the code, I don't see the point of testing it until the code is revised.
When the problems I'm seeing are typo's or to do with coding standards and it would take me less time to just do the revisions myself then to play "ping pong" with the changes needing to be made, I do those revisions myself and commit them to the PR (unless it's clearly a developer who intentionally commits sloppy code and refuses to follow coding standards).