Description
This bug was reported in 3.0.0, can be reproduced there. It is fixed already in 3.1.0 as of hash 5289f596f327f12477db29f0f3d5ca9db55db39f (I believe. This is the only related change to that part of the runtime code since 3.0.0)
This ticket is because tests need to be added which capture this precise failure behavior to prevent future regression.