TCK ChangeTokenTest doesn't work well about setContentStream because of an CmisVersioningException

ChangeTokenTest#runContentTest executes tests of setContentStream.
I found LINE132, the second call of setContentStream failed because of a CmisVersioningException error, which is implemented in my CMIS server.
The test intends to check whether the second call causes correctly an update conflict error, not a versioning error.

According to the specs 2.2.4.18, setContentStream service
-MAY automatically create new document versions as part of this service operations. Therefore, the objectId output NEED NOT be identical to the objectId input.
-MAY throw versioning error if the object is a non-current document version.

Unfortunately, my server implements both feature, say, in the first call of setContentStream a new document version is created(like version1.1) and the old document(version1.0) changed to be non-current version. And then, in the second call, setContentStream is called for the old document and raise the versioning error.

So I suppose that any care should be taken for this situation.