gaoyunhaii opened a new pull request #13629:
URL: https://github.com/apache/flink/pull/13629


   ## What is the purpose of the change
   
   Currently Flink on Azure test first pre-compile the project, and then 
download the pre-compile projects to run each part of tests separately. For 
protobuf related tests, it would download protoc executable automatically. 
However, the protoc executable would lost execution permission after 
downloading, so previously we enable `checkstableness` for this maven plugin. 
Since we would always touch all the java files after downloading, the 
re-generation should be avoided. 
   
   However, since the modification time of the downloaded file might be large 
than the current timestamp, the mechanism might fail. To fix this issue, we 
should also need to touch the proto files explicitly to make it 'younger' than 
the generated java files. 
   
   
   ## Brief change log
   
     - 548abe1c2b61698e8f8faf397b65864b5e367ed0 touches the proto files before 
the java files. 
   
   
   ## Verifying this change
   
   This change is a trivial bugfix without any test coverage.
   
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **no**
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **no**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: **no**
     - The S3 file system connector: **no**
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no**
     - If yes, how is the feature documented? **not applicable**
   


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

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


Reply via email to