Skip to content

OCPBUGS-83865: Revert stalld backend to sched_debug#1515

Open
bartwensley wants to merge 1 commit into
openshift:mainfrom
bartwensley:stalld-backend
Open

OCPBUGS-83865: Revert stalld backend to sched_debug#1515
bartwensley wants to merge 1 commit into
openshift:mainfrom
bartwensley:stalld-backend

Conversation

@bartwensley
Copy link
Copy Markdown
Contributor

@bartwensley bartwensley commented May 13, 2026

Updating the MC to revert the stalld backend to sched_debug. This is necessary because the new default queue_task backend causes an unacceptable latency penalty (see RHEL-175242).

Summary by CodeRabbit

  • New Features

    • stalld is now automatically configured to use the sched_debug backend via a provisioned backend config and a corresponding systemd override.
  • Tests

    • Added unit and end-to-end tests that verify the stalld backend configuration is generated and applied in rendered system configurations.

@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels May 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 13, 2026

@bartwensley: This pull request references Jira Issue OCPBUGS-83865, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @dgonyier

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

Details

In response to this:

Updating the MC to revert the stalld backend to sched_debug. This is necessary because the new default queue_task backend causes an unacceptable latency penalty (see RHEL-175242).

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 13, 2026

Warning

Rate limit exceeded

@bartwensley has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 42 minutes and 8 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 340397b1-a041-4f40-9d08-82ad15f2216e

📥 Commits

Reviewing files that changed from the base of the PR and between e3ed733 and a1e094a.

📒 Files selected for processing (13)
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig_test.go
  • test/e2e/performanceprofile/functests/1_performance/performance.go
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/arm/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/cpuFrequency/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/no-ref/manual_machineconfig.yaml

Walkthrough

The MachineConfig generator now injects two files into generated Ignition MachineConfigs: /etc/sysconfig/stalld-backend containing BE="-b sched_debug", and a systemd drop-in /etc/systemd/system/stalld.service.d/stalld-backend.conf that loads that EnvironmentFile. Tests and rendered fixtures were updated.

Changes

Stalld sched_debug Backend Configuration

Layer / File(s) Summary
Ignition content: add stalld sysconfig & systemd drop-in
pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go
getIgnitionConfig now unconditionally injects two storage files into Ignition: /etc/sysconfig/stalld-backend with BE="-b sched_debug" and /etc/systemd/system/stalld.service.d/stalld-backend.conf containing EnvironmentFile=/etc/sysconfig/stalld-backend; both are added via addContent with mode 0644.
Unit test: verify Ignition file contents
pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig_test.go
New Ginkgo Context("stalld backend configuration") builds a MachineConfig, unmarshals the Ignition payload, decodes file contents from base64, and asserts the sysconfig file contains the expected BE=... line and the systemd drop-in references the sysconfig via EnvironmentFile.
E2E check: systemd property assertions
test/e2e/performanceprofile/functests/1_performance/performance.go
Added an It block that queries stalld.service systemd properties on worker nodes and asserts DropInPaths includes /etc/systemd/system/stalld.service.d/stalld-backend.conf and EnvironmentFiles includes /etc/sysconfig/stalld-backend.
Rendered fixtures: expected MachineConfig updates
test/e2e/performanceprofile/testdata/render-expected-output/**/manual_machineconfig.yaml, test/e2e/performanceprofile/testdata/render-expected-output/**/openshift-*_machineconfig.yaml, test/e2e/performanceprofile/testdata/render-expected-output/**/manual_machineconfig.yaml
Updated multiple expected-output MachineConfig YAML fixtures (bootstrap, default, no-mcp, variants) to include the two new spec.config.storage.files entries (the sysconfig and the systemd drop-in) with base64-encoded contents and file metadata.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 9 | ❌ 3

❌ Failed checks (3 warnings)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Test Structure And Quality ⚠️ Warning Unit test dereferences *f.Contents.Source without nil check. First error checks lack meaningful messages. E2e test has By() calls but missing assertion message on first error check. Add Expect(f.Contents.Source).ToNot(BeNil()) guard before dereferencing at line 273. Add messages to Expect(err).ToNot(HaveOccurred()) calls in e2e test.
Microshift Test Compatibility ⚠️ Warning New e2e test uses PerformanceProfile API (performance.openshift.io), unavailable on MicroShift. Only Route and SecurityContextConstraints OpenShift APIs are supported. Add [apigroup:performance.openshift.io] tag, [Skipped:MicroShift] label, or exutil.IsMicroShiftCluster() check with g.Skip() to protect test from running on MicroShift.
✅ Passed checks (9 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title clearly describes the main change: reverting stalld backend configuration to sched_debug, which directly aligns with the code changes adding stalld-backend configuration files across multiple MachineConfig files.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed All test names are stable and deterministic. Test titles use static descriptive strings without dynamic values, node names, timestamps, UUIDs, or generated identifiers.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The test checks systemd properties on worker nodes without multi-node assumptions. It would work correctly on SNO where the single node has both master and worker roles.
Topology-Aware Scheduling Compatibility ✅ Passed No pod scheduling constraints introduced. Changes configure stalld service at node level via MachineConfig—topology-agnostic and safe across all OpenShift topologies.
Ote Binary Stdout Contract ✅ Passed No violations found. Added code is in regular functions or test case blocks where stdout is intercepted. No process-level code writes to stdout.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed No IPv4 assumptions or external connectivity requirements. Test queries local systemd properties on cluster nodes only, compatible with IPv6-only and disconnected CI jobs.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: dgonyier.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

@bartwensley: This pull request references Jira Issue OCPBUGS-83865, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @dgonyier

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

In response to this:

Updating the MC to revert the stalld backend to sched_debug. This is necessary because the new default queue_task backend causes an unacceptable latency penalty (see RHEL-175242).

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.

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.

@openshift-ci openshift-ci Bot requested review from ffromani and jmencak May 13, 2026 20:04
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@bartwensley
Copy link
Copy Markdown
Contributor Author

/cc @MarSik

@openshift-ci openshift-ci Bot requested a review from MarSik May 13, 2026 20:08
@bartwensley bartwensley marked this pull request as draft May 13, 2026 20:22
@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 May 13, 2026
@bartwensley
Copy link
Copy Markdown
Contributor Author

Looks like I need to update some e2e tests...

@bartwensley bartwensley marked this pull request as ready for review May 13, 2026 22:19
@openshift-ci openshift-ci Bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label May 13, 2026
@bartwensley
Copy link
Copy Markdown
Contributor Author

/retest

@bartwensley
Copy link
Copy Markdown
Contributor Author

/cc @browsell

@openshift-ci openshift-ci Bot requested a review from browsell May 14, 2026 11:47
})

Context("stalld backend configuration", func() {
It("should include stalld sysconfig and systemd dropin files", func() {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is checking the files, but not whether systemd consumed them. You should probably add an e2e test too that makes sure systemd noticed the files. See https://github.com/openshift/cluster-node-tuning-operator/blob/main/test/e2e/performanceprofile/functests/utils/systemd/systemd.go#L17 for helper functions. And probably place the test somewhere here https://github.com/openshift/cluster-node-tuning-operator/blob/main/test/e2e/performanceprofile/functests/1_performance/performance.go

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a new e2e test as you requested.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
test/e2e/performanceprofile/functests/1_performance/performance.go (1)

346-353: ⚡ Quick win

Assert the drop-in path directly to avoid false positives.

This test currently proves EnvironmentFiles contains /etc/sysconfig/stalld-backend, but that does not guarantee stalld-backend.conf is the source. Please also assert DropInPaths contains /etc/systemd/system/stalld.service.d/stalld-backend.conf (or equivalent merged unit output) so the test matches its stated intent.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@test/e2e/performanceprofile/functests/1_performance/performance.go` around
lines 346 - 353, The test "Should have the stalld service configured with the
stalld-backend drop-in" only checks EnvironmentFiles and can yield false
positives; update the test to also assert the systemd "DropInPaths" property
contains the actual drop-in file path
"/etc/systemd/system/stalld.service.d/stalld-backend.conf" (or the merged unit
equivalent) for each node by calling systemd.ShowProperty(context.TODO(),
"stalld.service", "DropInPaths", &node) and Expect the output to
ContainSubstring that full drop-in path alongside the existing EnvironmentFiles
check.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@test/e2e/performanceprofile/functests/1_performance/performance.go`:
- Around line 346-353: The test "Should have the stalld service configured with
the stalld-backend drop-in" only checks EnvironmentFiles and can yield false
positives; update the test to also assert the systemd "DropInPaths" property
contains the actual drop-in file path
"/etc/systemd/system/stalld.service.d/stalld-backend.conf" (or the merged unit
equivalent) for each node by calling systemd.ShowProperty(context.TODO(),
"stalld.service", "DropInPaths", &node) and Expect the output to
ContainSubstring that full drop-in path alongside the existing EnvironmentFiles
check.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0da1eb5e-b8ec-4d5f-90e1-2c9c39764110

📥 Commits

Reviewing files that changed from the base of the PR and between 4f402e3 and c2837d5.

📒 Files selected for processing (13)
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig_test.go
  • test/e2e/performanceprofile/functests/1_performance/performance.go
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/arm/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/cpuFrequency/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/no-ref/manual_machineconfig.yaml
✅ Files skipped from review due to trivial changes (2)
  • test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/manual_machineconfig.yaml
🚧 Files skipped from review as they are similar to previous changes (10)
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/arm/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/cpuFrequency/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/no-ref/manual_machineconfig.yaml
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig_test.go

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig_test.go`:
- Around line 273-275: The test dereferences f.Contents.Source directly which
can panic; before using it (where base64Data :=
strings.TrimPrefix(*f.Contents.Source, ...), decoded, err :=
base64.StdEncoding.DecodeString(...), Expect(err).ToNot(HaveOccurred())), add a
guard such as Expect(f.Contents).ToNot(BeNil()) and
Expect(f.Contents.Source).ToNot(BeNil()) (or an if f.Contents == nil ||
f.Contents.Source == nil { Fail("file source is nil") } ) so the test fails with
a clear assertion instead of panicking, then proceed to TrimPrefix/DecodeString
as before.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: ec84fbcd-de3c-4439-98bc-ea346bb87c36

📥 Commits

Reviewing files that changed from the base of the PR and between c2837d5 and e3ed733.

📒 Files selected for processing (13)
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig_test.go
  • test/e2e/performanceprofile/functests/1_performance/performance.go
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/arm/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/cpuFrequency/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/no-ref/manual_machineconfig.yaml
✅ Files skipped from review due to trivial changes (3)
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/no-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/manual_machineconfig.yaml
🚧 Files skipped from review as they are similar to previous changes (9)
  • test/e2e/performanceprofile/functests/1_performance/performance.go
  • test/e2e/performanceprofile/testdata/render-expected-output/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/pp-norps/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/arm/manual_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/no-ref/manual_machineconfig.yaml
  • pkg/performanceprofile/controller/performanceprofile/components/machineconfig/machineconfig.go
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-master_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/bootstrap/extra-mcp/openshift-bootstrap-worker_machineconfig.yaml
  • test/e2e/performanceprofile/testdata/render-expected-output/default/cpuFrequency/manual_machineconfig.yaml

Updating the MC to revert the stalld backend to sched_debug. This
is necessary because the new default queue_task backend causes an
unacceptable latency penalty (see RHEL-175242).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Bart Wensley <bwensley@redhat.com>
@bartwensley
Copy link
Copy Markdown
Contributor Author

/retest

@MarSik
Copy link
Copy Markdown
Contributor

MarSik commented May 15, 2026

/lgtm
/approved

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 15, 2026
@MarSik
Copy link
Copy Markdown
Contributor

MarSik commented May 15, 2026

/retest-required

@bartwensley
Copy link
Copy Markdown
Contributor Author

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 15, 2026

@bartwensley: all tests passed!

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants