Can we remove the hardcoded clusterloader2 folder name appended to $ARTIFACTS in --report-dir ? #151
Labels
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/testing
Categorizes an issue or PR as relevant to SIG Testing.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Current situation -
kubetest2-tester-clusterloader2
via a prow job, the results of the test are created in $artifacts/clusterloader2 which cannot be read by perfdash (perfdash looks for results inside the artifacts folder only)--report-dir
is not longer a valid argument for the clusterloader2 tester.Refer -
kubetest2/pkg/testers/clusterloader2/cl2.go
Line 81 in f4c453f
Why is this required?
We are trying to execute these perf tests on ppc64le arch Cloud VMs and have perfdash read the test result data.
With the mandatory clusterloader2 folder being created inside the $arifatcs folder, perfdash is no longer able to read test data.
I understand this may have been done originally with a purpose but wanted to check if we can make this concatenation optional so that someone can bypass the clusterloader folder creation inside $ARTIFACTS folder if and when required?
Note: I could not find a way to bypass this but please let me know if there is any way to do so in the existing code.
The text was updated successfully, but these errors were encountered: