mikepapadim commented on a change in pull request #9031:
URL: https://github.com/apache/tvm/pull/9031#discussion_r711248257
##########
File path: Jenkinsfile
##########
@@ -201,192 +205,240 @@ def unpack_lib(name, libs) {
}
stage('Build') {
- parallel 'BUILD: GPU': {
- node('GPUBUILD') {
- ws(per_exec_ws("tvm/build-gpu")) {
- init_git()
- sh "${docker_run} ${ci_gpu} ./tests/scripts/task_config_build_gpu.sh"
- make(ci_gpu, 'build', '-j2')
- pack_lib('gpu', tvm_multilib)
- // compiler test
- sh "${docker_run} ${ci_gpu}
./tests/scripts/task_config_build_gpu_vulkan.sh"
- make(ci_gpu, 'build2', '-j2')
+ parallel 'BUILD: GPU': {
+ node('GPUBUILD') {
+ ws(per_exec_ws('tvm/build-gpu')) {
+ init_git()
+ sh "${docker_run} ${ci_gpu} ./tests/scripts/task_config_build_gpu.sh"
+ make(ci_gpu, 'build', '-j2')
+ pack_lib('gpu', tvm_multilib)
+ // compiler test
+ sh "${docker_run} ${ci_gpu}
./tests/scripts/task_config_build_gpu_vulkan.sh"
+ make(ci_gpu, 'build2', '-j2')
+ }
}
- }
},
'BUILD: CPU': {
- node('CPU') {
- ws(per_exec_ws("tvm/build-cpu")) {
- init_git()
- sh "${docker_run} ${ci_cpu} ./tests/scripts/task_config_build_cpu.sh"
- make(ci_cpu, 'build', '-j2')
- pack_lib('cpu', tvm_multilib_tsim)
- timeout(time: max_time, unit: 'MINUTES') {
- sh "${docker_run} ${ci_cpu} ./tests/scripts/task_ci_setup.sh"
- sh "${docker_run} ${ci_cpu} ./tests/scripts/task_python_unittest.sh"
- sh "${docker_run} ${ci_cpu}
./tests/scripts/task_python_integration.sh"
- sh "${docker_run} ${ci_cpu} ./tests/scripts/task_python_vta_fsim.sh"
- sh "${docker_run} ${ci_cpu} ./tests/scripts/task_python_vta_tsim.sh"
- // sh "${docker_run} ${ci_cpu} ./tests/scripts/task_golang.sh"
- // TODO(@jroesch): need to resolve CI issue will turn back on in
follow up patch
- sh "${docker_run} ${ci_cpu} ./tests/scripts/task_rust.sh"
- junit "build/pytest-results/*.xml"
+ if (docs == 1) {
Review comment:
well, I am afraid we cant do it with a more elegant way atm. We need to
migrate the whole script to Declarative Jenkins.
--
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]
