Starting with r8727 the cluster regression reports an error with the file 18-02F.PS: % _Pg checksums collected from GPL Ghostscript SVN PRE-RELEASE version 3010 18-2f GSTATE 18-2f GSTATE = 0 Graphic 10 ms /18-2f__Pg01 0 def %matching 0 18-2f Special Test A 18-2f Special Test A = 29185 Graphic 10 ms 18-2f Special Test B 18-2f Special Test B typecheck imagemask * Error: /typecheck in --setgstate-- Operand stack: Disclose (>>) --dict:7/8(L)-- (<<) 239.0 297.5 (<<) --nostringval-- --nostringval-- Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nos tringval-- --nostringval-- false 1 %stopped_push 1905 1 3 %oparray_pop 1904 1 3 %oparray_pop 1888 1 3 %oparray_pop 1771 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostring val-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- --nostringval-- --nostrin gval-- --nostringval-- %array_continue --nostringval-- --nostringval-- --nostringval-- --nostringval-- stringwidt h (pattern accumulator) 7 %pattern_paint_finish --nostringval-- Dictionary stack: --dict:1153/1684(ro)(G)-- --dict:14/20(G)-- --dict:191/200(L)-- --dict:0/55(L)-- Current allocation mode is local GPL Ghostscript SVN PRE-RELEASE 8.63: Unrecoverable error, exit code 1 The command line I'm using for testing (not the same as the cluster regression, but the error is the same): bin/gs -I./lib:/home/marcos/Desktop/artifex/fonts -q -sDEVICE=pbmraw -sOutputFile=test.pbm -r72 -K1000000 -dMaxBitmap=30000000 -dNOOUTERSAVE -dJOBSERVER -dBATCH -dNOPAUSE - < ./18-02F.PS
Created attachment 4183 [details] 18-02F.PS
gstate is an expensive operation on Ghostscript. Rev. 8727 ceased to insert gstate into an implementation array of the pattern dictionary by default - just to please 18-02f.ps. CET requires execution of lib/gs_cet.ps file before the test cases. Among other things, gs_cet.ps selects CPSI compatibility mode. Rev. 8727 works as designed.
I'm reopening this as a reminder to either a) remove the offending file from the cluster regression or b) change the command line options so that it stops reporting an error. Having the cluster regressions report an error for this file every time it is run is annoying.
*** This bug has been marked as a duplicate of 689946 ***