Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Batching: Fixes finding maximum bash arguments #564

Closed
wants to merge 1 commit into from

Conversation

trozet
Copy link
Contributor

@trozet trozet commented Jun 4, 2021

It turns out what the system reports for maximum arguments may not be
the real amount of arguments that are usable in a shell. Different
kernels calculate it differently, but the gist is that the only reliable
way to know is to test for it. This patch does an initial search based
on the given max args in the kernel to find the actual usable amount.

The search is only done one time during initialization, so it shouldn't
impact performance.

Signed-off-by: Tim Rozet trozet@redhat.com

It turns out what the system reports for maximum arguments may not be
the real amount of arguments that are usable in a shell. Different
kernels calculate it differently, but the gist is that the only reliable
way to know is to test for it. This patch does an initial search based
on the given max args in the kernel to find the actual usable amount.

The search is only done one time during initialization, so it shouldn't
impact performance.

Signed-off-by: Tim Rozet <trozet@redhat.com>
@trozet trozet changed the title Batching: Fixes finding maximum bash arguments [WIP] Batching: Fixes finding maximum bash arguments Jun 4, 2021
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 4, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: trozet

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

The pull request process is described here

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

@trozet
Copy link
Contributor Author

trozet commented Jun 4, 2021

/hold

@openshift-ci openshift-ci bot requested review from abhat and danwinship June 4, 2021 14:16
@openshift-ci openshift-ci bot added approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Jun 4, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 4, 2021

@trozet: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/e2e-vsphere-windows d4bf2c3 link /test e2e-vsphere-windows
ci/prow/e2e-vsphere-ovn d4bf2c3 link /test e2e-vsphere-ovn
ci/prow/okd-e2e-gcp-ovn d4bf2c3 link /test okd-e2e-gcp-ovn
ci/prow/e2e-gcp-ovn d4bf2c3 link /test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-ipv6 d4bf2c3 link /test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-ipi-ovn-dualstack d4bf2c3 link /test e2e-metal-ipi-ovn-dualstack
ci/prow/4.8-upgrade-from-stable-4.7-e2e-aws-ovn-upgrade d4bf2c3 link /test 4.8-upgrade-from-stable-4.7-e2e-aws-ovn-upgrade
ci/prow/e2e-gcp-ovn-upgrade d4bf2c3 link /test e2e-gcp-ovn-upgrade
ci/prow/e2e-openstack-ovn d4bf2c3 link /test e2e-openstack-ovn
ci/prow/e2e-ovn-hybrid-step-registry d4bf2c3 link /test e2e-ovn-hybrid-step-registry

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

@trozet trozet closed this Jun 10, 2021
@trozet trozet deleted the debug_txn_batching branch June 10, 2021 13:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant