A little idea of a for loop in Oracle ____oracle

Today, when you execute the following anonymous block, I forced the execution off because it was too long, but when I checked the Src.test table, it was strange to see that there was some data in the table, but think about it, my understanding is as follows:
in fact, execution is an INSERT statement that forces an anonymous block to stop, Instead of simply stopping the INSERT statement, the statement after the INSERT statement is not ignored, but continues to execute the--commit,
so the Src.test table has the data. That is, forcing the stop, not stopping the execution of the anonymous block, but stopping the execution of the statement in the anonymous block.

begin
  for I in 1.1000000 loop
    inserts into src.test values (i, I | | ' Test ', i);
    commit;
  End Loop;
End;

So what about stored procedures.
Create or Replace procedure test as
begin for
i-1.100000 loop
insert into src.test values (I, I | |    ' Test ', i);
commit;
End Loop;
End;

Found the result to be the same.