Unexpected behaviour when got error in the middle of mysqldump backup file import
The behaviour is correct and it is incorrectly observed as per update from the questioner.
This got verified by further debugging the dumpload adding a debugging select syntax after the erroneous SQL in the dump.