This frequently happens when two reverts of the same original CL are created concurrently, causing confusion and wasted time for at least tandrii@.

I recall reviewing a contribution of handling IdenticalTreeException in Rebase Always strategy which for lack of understanding I deemed as a feature. Now I think it's more like a bug, or at least should be configurable.