all devices regression report - 2017-11-02-22:56:54 - 1626f36c9b6ae68abad7818be7cfb2a95f4ecffe

[email protected] Thu, 2 Nov 2017 22:56:54 -0700 (PDT)

Newsgroups	gmane.comp.printing.ghostscript.regression
Message-ID	<20171103055654.A1A5520408B4@i7>

Differences in all devices errors using gs/examples files

Previous Revision: 30ba3e3a163f729f2d05561e688dc54df6afa2e1
 Current Revision: 1626f36c9b6ae68abad7818be7cfb2a95f4ecffe

commit 1626f36c9b6ae68abad7818be7cfb2a95f4ecffe
Author:     Robin Watts <[email protected]>
AuthorDate: Thu Nov 2 17:54:57 2017 +0000
CommitDate: Thu Nov 2 17:54:57 2017 +0000

    Bug 698713: Further graphicsAlphaBits + new scan converter fix.
    
    Previous I ensured that when using graphicsAlphaBits, the new scan
    converter would restrict its output rectangles/traps to fit
    within y % max_fill_band pixels at a time as required.
    
    I forgot that the base 'y' value taken for this was not necessarily
    aligned to a max_fill_band multiple. Fixed here.

base/gxscanc.c

new errors:

errors that went away:

errors that are not whitelisted:
=== ghostpdl/examples/transparency_example.ps === cp50 ===
=== ghostpdl/examples/transparency_example.ps === psdrgb ===