all devices regression report - 2017-11-02-19:14:43 - 1ab17bc53362ea34b61050429c51c575539bf2b9

[email protected]
Newsgroups gmane.comp.printing.ghostscript.regression
Message-ID <20171103021443.2621B20408B4@i7>
Differences in all devices errors using gs/examples files

Previous Revision: b3c0fafa490932cc43009c53c7f8a17598fe78d7
 Current Revision: 1ab17bc53362ea34b61050429c51c575539bf2b9

commit 1ab17bc53362ea34b61050429c51c575539bf2b9
Author:     Robin Watts <[email protected]>
AuthorDate: Tue Oct 31 19:37:10 2017 +0000
CommitDate: Wed Nov 1 14:58:22 2017 +0000

    Avoid clearing cm_comps arrays in cmap functions.
    
    This goes against commit 99c48263b9 by Ray (dating from Nov 1 2009)
    to fix Bug 690713 and solve some indeterminisms.
    
    My belief is that this SHOULD be fixed in the devices, not in the
    callers. Accordingly I have backed that out, and changed the
    cmyk_cs_to_psdcmyk_cm function (the only one I can find that does
    not set everything to be 0).
    
    The cluster now shows this running with no diffs.

base/gxcmap.c
devices/gdevpsd.c

new errors:

errors that went away:

errors that are not whitelisted:
=== ghostpdl/examples/transparency_example.ps === cp50 ===
=== ghostpdl/examples/transparency_example.ps === psdrgb ===
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.