Hi,

these tests write out vtk files and read them in using python3-vtk9.
If parsing of the file succeeds then the test was successful.

How the files are written did not change between Debian stable and Debian sid.
I have verified that the files are the same.

Attached is a small test case in python3-vtk9-test.tar.gz that mimics the
problems. The script test/vtkcheckcomb.py will read the file vtktest-1D-leafview-nonconforming-appendedbase64.vtp using different
relative paths with vtkXMLPolyDataReader.

On Debian stable all those cases succeed (see log file 
tests/stable/vtkcheckcomb.log.

On Debian sid all of the fail with this error of vtk xml parser:

2024-03-11 14:31:34.098 (   0.123s) [        A51E0740]       
vtkXMLParser.cxx:375    ERR| vtkXMLDataParser (0x1659c80): Error parsing XML in 
stream at line 27, column 9, byte index 1562: not well-formed (invalid token)
2024-03-11 14:31:34.099 (   0.123s) [        A51E0740]       
vtkXMLReader.cxx:521    ERR| vtkXMLPolyDataReader (0x15f4e90): Error parsing 
input file.  ReadXMLInformation aborting.
2024-03-11 14:31:34.099 (   0.123s) [        A51E0740]       
vtkExecutive.cxx:752    ERR| vtkCompositeDataPipeline (0x1631800): Algorithm 
vtkXMLPolyDataReader(0x15f4e90) returned failure for request: vtkInformation 
(0x166e920)
  Debug: Off
  Modified Time: 775
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0

I have no clue why this is the case. To me it is more likely that the problem
is due a change in vtk9. Hence I am reassinging to vtk9 in the hope
that the maintainers there have more clues than me.

Best,

Markus


Attachment: python3-vtk9-test.tar.gz
Description: application/gzip

Reply via email to