Document how to debug performance of Prow jobs in etcd

[ronaldngounou]

Overview

This PR documents how etcd contributors can navigate performance of prow jobs.
Contributes to issue #18707

[k8s-ci-robot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ronaldngounou
Once this PR has been reviewed and has the lgtm label, please assign ivanvc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.18%. Comparing base (8a4955b) to head (e6a773b).

Additional details and impacted files

see 21 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #20796      +/-   ##
==========================================
+ Coverage   69.12%   69.18%   +0.06%     
==========================================
  Files         422      422              
  Lines       34826    34826              
==========================================
+ Hits        24073    24095      +22     
+ Misses       9352     9333      -19     
+ Partials     1401     1398       -3     

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8a4955b...e6a773b. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ronaldngounou]

Hi @ivanvc , could you please review?
Is there anything I could do to resolve the failing tests ?

[serathius]

Is there anything I could do to resolve thr failing tests ?

Please rebase

[ivanvc]

Hi @ronaldngounou, there are a couple of broken links in the document you pushed. Refer to the Prow job failure: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/etcd-io_etcd/20796/pull-etcd-verify/1979810317445632000#

Found broken reference (Prow -> ) at /home/prow/go/src/github.com/etcd-io/etcd/Documentation/contributor-guide/prow_jobs.md:5
Found broken path (dashboards -> monitoring-gke.prow.k8s.io/d/96Q8oOOZk/builds?orgId=1&refresh=30s&var-org=etcd-io&var-repo=etcd&var-build=All&from=now-7d&to=now) at /home/prow/go/src/github.com/etcd-io/etcd/Documentation/contributor-guide/prow_jobs.md:41

[ronaldngounou]

I have rebased and fixed the broken links.
cc @ivanvc @serathius

[ivanvc]

Thanks, @ronaldngounou. This is a great start. I left some comments. Please take a look at them.

[ronaldngounou]

Feedback is addressed

[jberkus]

/assign

[ronaldngounou]

/retest

[ivanvc]

Thanks for the updates, @ronaldngounou. I left some comments after the update.

[ronaldngounou]

Feedback is addressed @ivanvc