mikes-lunarg
commented
6 years ago The spec style guide does say that semantic VU changes should remove the VUID so that a new one can be assigned. A gentle reminder to spec editors might be necessary if this continues to happen.
Changes to core spec between 1.0.68 and .71 modified two existing VUIDs (VUID-VkImageCopy-srcImage-01785 & 01786) by splitting them each into two, one new and one that re-uses the existing VUID text. This is a fix to update the existing checks and add the newly created ones, and update the tests to match.
This points out a problem with specification changes that re-use VUIDs. The existing checks/tests for the previous VUID language remain consistent with each other (though both wrong according to the updated spec), and there is no automated way to notice they are now broken. The database records them as implemented and the existing test continues to pass. (The newly-created VUIDs are not a problem because they show up in the database as new and unimplemented.)