My errorstrings might be wrong?

Viewing 4 posts - 1 through 4 (of 4 total)
  • Back to forum
    Posted in: Muster usage
  • Christian Sjostedt
    19th March 2014 at 12:18 pm #14523

    Hi,

    I have a renderissue that Im trying to figure out.

    In my renderlog I get this line:

    00:03:44 6122MB | [driver_exr] writing file `W:/projects/XXXX/002/0400/3d/maya/renders/Holdout1_RL/Shot0400_Layout_v037_test1_Holdout1_RL_1920x720_exr.0098.exr’
    00:03:44 6123MB WARNING | [driver_exr] defaultArnoldDriver@driver_exr.RGBA: Failed OpenEXR write: Failed to write pixel data to image file “W:/projects/XXXX/002/0400/3d/maya/renders/Holdout1_RL/Shot0400_Layout_v037_test1_Holdout1_RL_1920x720_exr.0098.exr”. Invalid argument.

    So I’m trying to write an error line so muster will react to this.
    In my template I have this segment:

    DECLARE ERROR
    {
    ADD WARNING “WARNING”
    ADD ERROR “translator ” “*Failed to write pixel data to image file*” “*Failed OpenEXR write*” “Invalid argument.” “Error: line 1: Error reading file.” “Maya binary file parse error:” “error” “ERROR” “Error”
    ADD ERROR_RETCODE -1
    ADD WARNING_RETCODE 1
    ADD DEFAULT_RETCODE 0
    }

    as you can see I have a lot of patterns to react to but muster doesnt seem to pick it up?
    Am I doing something wrong? Do I need to enable something for these to be picked up better?

    cheers,
    /Chris

    Leonardo Bernardini
    19th March 2014 at 5:48 pm #15243

    The error string should be a simple string, or a regular expression. Regexp does not accept *string* , but should be .*STRING.*

    Cheers

    Christian Sjostedt
    19th March 2014 at 5:58 pm #15245

    I’m not sure I get it.

    If I’m trying to cause it to fail when this appears in the log: “Failed OpenEXR write” or this: “Invalid argument.”

    Shouldn’t this work then?

    ADD ERROR “translator ” “*Failed to write pixel data to image file*” “*Failed OpenEXR write*” “Invalid argument.” “Error: line 1: Error reading file.” “Maya binary file parse error:” “error” “ERROR” “Error”

    Christian Sjostedt
    20th March 2014 at 8:18 am #15246

    from support:

    You shoud use:

    “.*Failed OpenEXR write.*” instead of “*Failed OpenEXR write*”

    and that works:-)

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.