Bug 691873 - Regression: indeterminism with r12005
Summary: Regression: indeterminism with r12005
Status: RESOLVED FIXED
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Color (show other bugs)
Version: master
Hardware: PC All
: P2 normal
Assignee: Michael Vrhel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-08 21:52 UTC by Marcos H. Woehrmann
Modified: 2011-01-11 00:51 UTC (History)
0 users

See Also:
Customer:
Word Size: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos H. Woehrmann 2011-01-08 21:52:56 UTC 
Starting with r12005 a new indeterminism was produced in psdcmyk and cups output.

This affects at least the following files:

tests/pdf/Bug6901014_Fourth_crash_signature_testcase.pdf.psdcmyk.72.0 
tests_private/comparefiles/405-01.ps.cups.300.1 
tests_private/comparefiles/477-05.ps.psdcmyk.72.0 
tests_private/comparefiles/Bug688308.ps.psdcmyk.72.0 
tests_private/comparefiles/Bug690161a.pdf.psdcmyk.72.0 
tests_private/comparefiles/Bug690237.pdf.cups.300.1 
tests_private/comparefiles/Bug691115.pdf.psdcmyk.72.0 
tests_private/comparefiles/Bug691783.pdf.psdcmyk.72.0 
tests_private/comparefiles/H00216q.pdf.psdcmyk.72.0 
tests_private/comparefiles/ai2.pdf.psdcmyk.72.0 
tests_private/comparefiles/jpx-johnny1.pdf.cups.300.1 
tests_private/comparefiles/kazmir.pdf.psdcmyk.72.0 
tests_private/comparefiles/mspro.pdf.psdcmyk.72.0 
tests_private/comparefiles/p2b-100.pdf.cups.300.1 
tests_private/comparefiles/z400454b01d4-1.pdf.psdcmyk.72.0 
tests_private/pdf/PDFIA1.7_SUBSET/CATX0249.pdf.cups.300.1 
tests_private/pdf/PDFIA1.7_SUBSET/CATX2071.pdf.psdcmyk.72.0 
tests_private/pdf/PDFIA1.7_SUBSET/CATX5233.pdf.psdcmyk.72.0 
tests_private/pdf/PDFIA1.7_SUBSET/IA3Z3298.pdf.cups.300.1 
tests_private/pdf/PDF_1.7_FTS/fts_17_1705.pdf.psdcmyk.72.0 
tests_private/pdf/PDF_1.7_FTS/fts_18_1806.pdf.psdcmyk.72.0 
tests_private/pdf/PDF_1.7_FTS/fts_25_2502.pdf.psdcmyk.72.0 
tests_private/pdf/PDF_1.7_FTS/fts_25_2509.pdf.psdcmyk.72.0 
tests_private/pdf/PDF_1.7_FTS/fts_25_2512.pdf.psdcmyk.72.0 
tests_private/pdf/PDF_1.7_FTS/fts_25_2514.pdf.psdcmyk.72.0 
tests_private/ps/ps3cet/09-34.PS.cups.300.1 
tests_private/ps/ps3cet/09-35.PS.cups.300.1 
tests_private/ps/ps3cet/09-39.PS.cups.300.1 
tests_private/ps/ps3cet/09-42.PS.cups.300.1 
tests_private/ps/ps3cet/29-07H.PS.cups.300.1 
tests_private/ps/ps3cet/29-07K.PS.cups.300.1
Comment 1 Marcos H. Woehrmann 2011-01-08 22:03:19 UTC 
The indeterminisms are system dependent; here are the md5sums for the file tests_private__comparefiles__405-01.ps.cups.300.1 for the last batch of cluster regression runs (this file is okay on all machines but macpro, where it has a different md5sum every time):

a5508e3f052e48430467b2d53d3d03c0        x6      
276a613f6b3dccecb02228872ff615ba        macpro  
a5508e3f052e48430467b2d53d3d03c0        i7      
a5508e3f052e48430467b2d53d3d03c0        peeves  
d1de688b3dd47e796ac07a4a1ba5ffd3        macpro  
a5508e3f052e48430467b2d53d3d03c0        peeves  
a5508e3f052e48430467b2d53d3d03c0        miles   
a5508e3f052e48430467b2d53d3d03c0        x6      
f02c5e08b9bdff88587ec45d7e48bda6        macpro  
4b8ffafb3cbe402c9f7cd5c306528cac        macpro  



Other file behave differently.  The file tests_private__comparefiles__Altona_Visual_bb_1v1_x3.pdf.psdcmyk.72.0 is different on every machine:


370893965ba7138d4165c48018a8b7eb        macpro  
11f5f620754968f54fb38810a5e8d1a7        x6      
d9db37c4fe959dc57e6d9f01bc5bcf82        i7b     
d9db37c4fe959dc57e6d9f01bc5bcf82        miles   
11f5f620754968f54fb38810a5e8d1a7        henrysx6
d9db37c4fe959dc57e6d9f01bc5bcf82        i7      
370893965ba7138d4165c48018a8b7eb        macpro  
d9db37c4fe959dc57e6d9f01bc5bcf82        i7a     
11f5f620754968f54fb38810a5e8d1a7        henrysx6
d9db37c4fe959dc57e6d9f01bc5bcf82        i7
Comment 2 Michael Vrhel 2011-01-09 02:21:40 UTC 
OK.  There seem to be a pile of these.   I will try to get this resolved quickly
Comment 3 Michael Vrhel 2011-01-11 00:51:48 UTC 
I think this should be fixed with rev 12018.