ID 239139 - Aborted Bakes still turn green despite not being updated

Problem summary
When aborting a bake, the bake point node will still update to green despite containing no data.

Customer reported version

3.2v1 

Customer reported platform
CentOS 7

Steps to reproduce

1) Create a Bake Point node with a cloud node before it

2) Bake the Bake Point node, which will turn green

3) Modify the Cloud node somewhat

4) The Bake Point should turn red as it is out of date

5) Bake again and before the bake finishes, abort the process 

6) The Bake Point still turns green but does not update. 

Note: In cases where there is an 'Error Baking Stack', the Bake will abort but the Bake Points will also turn green. 

Workaround
Unknown. 

Reproduced by support
3.2v1
Win 7, Linux CentOS 6

Expected behaviour
The abort function should be written into the mip-map generation and the bake point node should acknowledge that the bake has been cancelled by staying red. Mari should throw out an 'Error Baking Stack' dialog for Bake points when this happens as it would during export.

Actual behaviour
Bake Point node turns green and is marked as being up-to-date.