luis4a0 commented on PR #13282:
URL: https://github.com/apache/gluten/pull/13282#issuecomment-6467117559

   @rui-mo, the current head 9371fa2f0fc901dbd72c81fe3c36707e07e3a976 has one 
remaining failed job:
   https://github.com/apache/gluten/actions/runs/40514668449/job/122238679526
   
   The failure is GlutenTransformWithStateAvroSuite's "test that introducing 
TTL after restart fails query (encoding = Avro) (with changelog 
checkpointing)", reporting STATE_STORE_INVALID_VALUE_SCHEMA_EVOLUTION. The 
suite wrapper and streaming fallback trait are unchanged from the merged public 
base, and this path explicitly uses vanilla Spark operators.
   
   The identical test executed and passed in the OneRow comparison run on the 
same merged public base:
   https://github.com/apache/gluten/actions/runs/40514673099/job/122230938413
   
   That comparison is not a same-head reproduction and does not prove a flake. 
Could a maintainer rerun the failed shard once to distinguish a transient test 
failure from a reproducible Spark streaming issue? I attempted the failed-job 
rerun once, but GitHub returned HTTP 403. I have not changed the streaming 
code, added a skip, or bypassed a check.
   
   The separate native dependency gate is unchanged: the temporary upstream-PR 
hook must be replaced by a qualified normal Velox dependency before this 
companion merges.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to