org.hibernate.validator.internal.metadata.aggregated.ExecutableMetaData.Builder.add(ConstrainedElement)

			// keep the "lowest" executable in hierarchy to make sure any type parameters declared on super-types (and
			// used in overridden methods) are resolved for the specific sub-type we are interested in
			if ( executable != null && overrides(
					constrainedExecutable.getExecutable(),
					executable
			) ) {
				executable = constrainedExecutable.getExecutable();
			}

Correct comment but incorrect if() expression. It is necessary to change the parameters of the function overrides() in places.

			if ( executable != null && overrides(
					executable,
					constrainedExecutable.getExecutable()
			) ) {
				executable = constrainedExecutable.getExecutable();
			}

As a result, there are cases when the meta data collected from the class does not contain all the specified constaints. And the situation can change from run to run and depends on in which order the BeanMetaDataImpl<T>.BeanMetaDataBuilder.build() iterates Set <BuilderDelegate> builders and adds to Set<ConstraintMetaData> aggregatedElements.

Attachment contains example of the hierarchy on which this issue occurs.