Caideyipi opened a new pull request, #19027:
URL: https://github.com/apache/iotdb/pull/19027

   Backport of #19016 (`788de1882cd21336b81ca4451b90f9289d9cfc25`) to 
`dev/1.3`, based on `1fdcb123ac9f045b014c52eabaa5c9d1707ad936`.
   
   `testDoubleLivingAutoConflictTemplate` can write to the receiver before its 
replicated template is usable. Wait for the template binding, then retry the 
first idempotent receiver insert while template publication completes. Later 
inserts retain their existing failure behavior, and both clusters must still 
return all 400 timestamps.
   
   The backport applies the same changes to the 1.3 test under 
`pipe/it/autocreate`, preserving its existing connection handling and test 
category. The target branch already provides the equivalent assertion and retry 
helpers; no production code or unrelated tests change. The commit retains the 
`cherry picked from` trailer.
   
   Validation:
   
   - Passed `mvn spotless:apply -P with-integration-tests -pl integration-test` 
and `git diff --check`.
   - Clean reactor compilation, test compilation, and node-template packaging 
completed on Windows/JDK 17 with `-pl integration-test -am`. Used 
`-Drat.skip=true` after the initial build was blocked by five existing Go 
submodule files flagged by RAT; those files are unchanged.
   - Targeted `IoTDBPipeAutoConflictIT#testDoubleLivingAutoConflictTemplate` 
with `MultiClusterIT2AutoCreateSchema` and 
`HighPerformanceMode,HighPerformanceMode`: 1 test selected, 1 failure in 
`setUp`. DataNode JVMs failed native memory allocation with Windows error 1455 
(paging file too small), so the changed test body remains unverified.
   - A fresh Linux attempt was blocked resolving the Maven extension because 
Maven Central was unreachable.


-- 
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]

Reply via email to