Rendering stops before reaching the desired noise level

[dj_buckley]

So I left a huge render going over night.

Just came in this morning and it looks pretty noisy but it's stopped rendering.

I set it rendering with a noise limit of 3%.  And rendered with Corona 2 through DR.  One host, one node.

I've checked the stats tab and it reads 4.21% (3%).  So it appears the render has stopped once the node has reach 3%?

Seems odd?  Is this correct behaviour?

[maru]

We've had some similar reports already and we are trying to hunt down this bug, but no luck so far. Could you upload this problematic scene to https://corona-renderer.com/upload and contact us about it at https://coronarenderer.freshdesk.com/support/tickets/new ?
Thanks in advance!

[dj_buckley]

All uploading now

[dj_buckley]

Having to upload using the Dropbox method now as the file kept bombing during the normal upload

[maru]

We have managed to reproduce this issue and we are investigating it. It is high priority for us, but unfortunately the fix won't be included in V3.
It seems that generally the noise level is reported correctly, and the rendering stops when the given noise level is reached, but the issue is that the reported noise level changes after the rendering is stopped. So for example, if noise limit is set to 3, the rendering will stop at 2,8, but then it will incorrectly change itself to 4.

(note to self id=267607823)

[maru]

According to our tests, this seems to be fixed in the newest daily (27.08.2019 V5), so I am moving it to resolved. If something similar ever happens to you again, please do report it.