According to the description in
It is assumed that one DML command will not generate history rows more
than specified LIMIT. Otherwise history would overflow generated
partition, a warning would be printed, and user action would be
required to rebuild partitions
There is no warning.
In the test case below, the limit is 1000, and each DELETE moves 1200 rows into a historical partition. It is done twice in case of the first DELETE doesn't produce a warning due to
MDEV-25475; but the second one does not do it either, neither in the client nor in the error log.