Add Navi3x/Navi4x hardware to the weekly run #1768
Conversation
mlir/utils/jenkins/Jenkinsfile
Outdated
| @@ -685,7 +688,7 @@ pipeline { | |||
| axes { | |||
| axis { | |||
| name 'ARCH' | |||
| values 'gfx908', 'gfx90a', 'gfx1030' | |||
| values 'gfx908', 'gfx90a', 'gfx1030', 'gfx1100', 'gfx1101', 'gfx1201' | |||
There was a problem hiding this comment.
gfx1100 and gfx1101 both are Navi3x based cards. I don't think we need to run on both of them.
There was a problem hiding this comment.
You would need to use same label later in this stage for Navi3x:
rocMLIR/mlir/utils/jenkins/Jenkinsfile
Line 815 in a8ac1fb
There was a problem hiding this comment.
@umangyadav regarding gfx1100 and gfx1101, I talked with Stefan so we thought that it would be good to do it on both and see which is more stable.
But if you think it's better, we can run it only on one of them.
There was a problem hiding this comment.
it would be good to do it on both and see which is more stable.
To me it seems we are not correctly making use of the Jenkins Tuning and Nightly Runs as of today. i.e. we are not really analyzing perf results on daily basis.
Therefore it seems to me we are better off keeping just one of the Navi3x on the CI right now. otherwise we increase likelihood of failing weekly CI due to random errors and it will cause more problems.
|
Can you also add Navi3x to parameterSweeps stage ? rocMLIR/mlir/utils/jenkins/Jenkinsfile Line 626 in a8ac1fb |
| @@ -812,7 +814,7 @@ pipeline { | |||
| axes { | |||
| axis { | |||
| name 'CHIP' | |||
| values 'gfx908', 'gfx90a', 'gfx1030', 'gfx1101' | |||
| values 'gfx908', 'gfx90a', 'gfx1030', 'gfx1100', 'gfx1201' | |||
There was a problem hiding this comment.
can you trigger nightly and weekly tuning runs manually on this branch and see if it is tuning and generating perf reports ?
Do weekly tuning on Navi3x/Navi4x and use those perfDBs for nightly performance runs
Resolves #1727