zhangyue19921010 edited a comment on pull request #4398: URL: https://github.com/apache/hudi/pull/4398#issuecomment-998363844
Hi @yihua and @nsivabalan https://dev.azure.com/apache-hudi-ci-org/apache-hudi-ci/_build/results?buildId=4580&view=results  As we can see, I set `timeoutInMinutes: 90` for job 4 and it works fine based on https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema%2Cparameter-schema and job2 is timeout for compartment. ``` jobs: - deployment: string # name of the deployment job, A-Z, a-z, 0-9, and underscore. The word "deploy" is a keyword and is unsupported as the deployment name. displayName: string # friendly name to display in the UI pool: # see pool schema name: string # Use only global level variables for defining a pool name. Stage/job level variables are not supported to define pool name. demands: string | [ string ] workspace: clean: outputs | resources | all # what to clean up before the job runs dependsOn: string condition: string continueOnError: boolean # 'true' if future jobs should run even if this job fails; defaults to 'false' container: containerReference # container to run this job inside services: { string: string | container } # container resources to run as a service container timeoutInMinutes: nonEmptyString # how long to run the job before automatically cancelling cancelTimeoutInMinutes: nonEmptyString # how much time to give 'run always even if cancelled tasks' before killing them variables: # several syntaxes, see specific section environment: string # target environment name and optionally a resource name to record the deployment history; format: <environment-name>.<resource-name> strategy: runOnce: #rolling, canary are the other strategies that are supported deploy: steps: [ script | bash | pwsh | powershell | checkout | task | templateReference ] ``` I will rerun this 4 jobs to see it works as expected, when set `timeoutInMinutes: '90' as string` -- 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]
