Thanks Aaron, that's helpful.

Glad the duplicate module issue is resolved, and that makes sense as it's a frequently used 'test' module name.

That new error is unrelated, but one we know about and have fixed in our next maintenance release (23.3.3). Learn more in the internal issue here.

As mentioned there, this is only an issue when your upgrade of the compliance module skips the 22.11 release. You may be able to work around this one by first upgrading to 22.11.9 and then 23.3.2.

--Molly