DO NOT MERGE: OCPBUGS-103516: Fixed perfscale re-run (matched baseline)

[hasbro17]

DO NOT MERGE — throwaway PR for perfscale data gathering only.

No code changes (empty commit). This branch builds identically to main,
i.e. the bbolt fork with MADV_RANDOM removed (#395). It exists purely so
a control-plane-fips-24nodes perfscale payload job can run against the
fixed etcd, matched in the same nightly/infra window against the
broken baseline in #397.

Together they give a clean same-infra fixed-vs-broken pair for the
upstream removal argument in etcd-io/bbolt#939.

Do not merge or review — this branch will be deleted once the data is
collected.

Ref: etcd-io/bbolt#939
Ref: https://redhat.atlassian.net/browse/OCPBUGS-103516

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@hasbro17: This pull request references Jira Issue OCPBUGS-103516, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

DO NOT MERGE — throwaway PR for perfscale data gathering only.

No code changes (empty commit). This branch builds identically to main,
i.e. the bbolt fork with MADV_RANDOM removed (#395). It exists purely so
a control-plane-fips-24nodes perfscale payload job can run against the
fixed etcd, matched in the same nightly/infra window against the
broken baseline in #397.

Together they give a clean same-infra fixed-vs-broken pair for the
upstream removal argument in etcd-io/bbolt#939.

Do not merge or review — this branch will be deleted once the data is
collected.

Ref: etcd-io/bbolt#939
Ref: https://redhat.atlassian.net/browse/OCPBUGS-103516

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hasbro17

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

Details

Needs approval from an approver in each of these files:

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

[hasbro17]

/payload-job periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.0-nightly-x86-control-plane-fips-24nodes

[openshift-ci]

@hasbro17: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-eng-ocp-perfscale-main-aws-5.0-nightly-x86-control-plane-fips-24nodes

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/2eaf58b0-95c7-11f1-91cb-f858c0190018-0

[hasbro17]

/test perfscale-control-plane-6nodes

[openshift-ci]

@hasbro17: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/perfscale-control-plane-6nodes	0fb0fd4	link	false	/test perfscale-control-plane-6nodes

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.