Skip to content

DAOS-18710 test: Update weekly provider test to use dc_x for UCX.#17978

Open
jgmoore-or wants to merge 1 commit intoprovider-testingfrom
jgm/DAOS-18710-2
Open

DAOS-18710 test: Update weekly provider test to use dc_x for UCX.#17978
jgmoore-or wants to merge 1 commit intoprovider-testingfrom
jgm/DAOS-18710-2

Conversation

@jgmoore-or
Copy link
Copy Markdown
Contributor

Test-provider: ucx+dc_x
Test-provider-hw-large: ucx+dc_x
Test-provider-hw-medium: ucx+dc_x
Test-provider-ucx: ucx+dc_x
Skip-func-hw-test-medium-verbs-provider: true
Skip-func-test-vm: true
Allow-unstable-test: true

Steps for the author:

  • Commit message follows the guidelines.
  • Appropriate Features or Test-tag pragmas were used.
  • Appropriate Functional Test Stages were run.
  • At least two positive code reviews including at least one code owner from each category referenced in the PR.
  • Testing is complete. If necessary, forced-landing label added and a reason added in a comment.

After all prior steps are complete:

  • Gatekeeper requested (daos-gatekeeper added as a reviewer).

Test-provider: ucx+dc_x
Test-provider-hw-large: ucx+dc_x
Test-provider-hw-medium: ucx+dc_x
Test-provider-ucx: ucx+dc_x
Skip-func-hw-test-medium-verbs-provider: true
Skip-func-test-vm: true
Allow-unstable-test: true

Signed-off-by: Joseph Moore <joseph.moore@hpe.com>
@github-actions
Copy link
Copy Markdown

Ticket title is 'Change to using ucx+dc_x as the provider string for daily test run with UCX and for the weekly provider tests.'
Status is 'In Review'
Labels: 'request_for_2.6.5,scrubbed_2.8'
Job should run at elevated priority (1)
https://daosio.atlassian.net/browse/DAOS-18710

@github-actions github-actions bot added the priority Ticket has high priority (automatically managed) label Apr 10, 2026
@daosbuild3
Copy link
Copy Markdown
Collaborator

Test stage Functional Hardware Medium UCX completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17978/2/execution/node/179/log

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

Labels

priority Ticket has high priority (automatically managed)

Development

Successfully merging this pull request may close these issues.

2 participants