State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:241718|
Problem summary
negative values in the performance metrics xml output <timeTakenCPU>
requirement reference:
http://help.thefoundry.co.uk/nuke/#comp_environment/configuring_nuke/command_line_operations.html?Highlight=command line operations
-Pf <filename> Measure your nodes’ performance metrics and write them to an XML file at render time. See Using Script Profiling for more information.
Customer reported version
nuke.9.0v9
Customer reported platform
centos6
Steps to reproduce
A sample script is attached. It is cpu-intensive and scales the final image down to 1/10 scale before writing it out.
1.
Open the script, re-point the Write file knob and save it.
2.
execute a command line render of 2 frames with the command
./Nuke9.0 -x -F 1-2 -Pf <path/file for .xml metrics> <path/nukescript>
It will render 2 frames. Search the .xml after for negative values between these tags, as in this example
<timeTakenCPU>-12839505870</timeTakenCPU>
Workaround
Unknown.
Reproduced by support
Support has been unable to reproduce the problem on Nuke9.0v9 or 10.0v4, probably due to machine configs (tried OS 10.10.5 and CentOS6.8), however, Engineering has seen the problem on Windows but not yet on Linux, where this was reported.
Expected behaviour
<timeTakenCPU>
will contain no negative values
Actual behaviour
<timeTakenCPU>
shows negative values
We're sorry to hear that
Please tell us why