Skip to content

push-test-metrics: hard coded periodic names #4802

@dhiller

Description

@dhiller

What happened:
Periodic names that are looked at are hard coded:

jobNamesToScan = jobNames{

This generates test times from old job runs and ridicules the values.

What you expected to happen:
Job names should be deferred from the kubevirt-periodics.yaml
Use

func ReadJobConfig(jobConfig string, yamlOpts ...yaml.JSONOpt) (JobConfig, error) {
func to read the config.

How to reproduce it (as minimally and precisely as possible):
See link, see k8s lane names in grafana panel: https://grafana.ci.kubevirt.io/d/gY4hNc5Iz/kubevirt-kubevirt-e2e-test-runtimes?orgId=1&editPanel=6

Additional context:
n/a

/help
/good-first-issue

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueIdentifies an issue that has been specifically created or selected for first-time contributors.help wantedIdentifies an issue that has been specifically created or selected for new contributors.kind/bugpriority/backlogIndicate that the issue or PR is a lower priority and can be worked on in the futuretriage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions