Skip to content

Conversation

@grom72
Copy link
Contributor

@grom72 grom72 commented Jan 14, 2026

This PR upgrades the majority of the CI test stages so that they are run on EL9.7.

  • Build on 9.7
  • Unit Test on EL 9.7
  • Unit Test bdev on EL 9.7
  • NLT on EL 9.7 - several tests failed
  • Unit Test with memcheck on EL 9.7 - partially failed
  • Unit Test bdev with memcheck on EL 9.7 - partially failed
  • Functional on EL 9.7 with Valgrind - failed
  • Functional on EL 9.7
  • Fault injection testing on EL 9.7
  • Test RPMs on EL 9.6
  • Functional Hardware - IN PROGRESS
    • Functional Hardware Medium
    • Functional Hardware Medium MD on SSD
    • Functional Hardware Medium VMD
    • Functional Hardware Medium Verbs Provider
    • Functional Hardware Medium Verbs Provider MD on SSD
    • Functional Hardware Medium UCX Provider
    • Functional Hardware Large
    • Functional Hardware Large MD on SSD

Requires:

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).

Cancel-prev-build: false
Priority: 2

Skip-build-leap15-gcc: true

Allow-unstable-test: true

Skip-func-hw-test-medium: false

Skip-func-hw-test-medium-md-on-ssd: false

Skip-func-hw-test-large: false
Skip-func-hw-test-large-md-on-ssd: false

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
@github-actions
Copy link

github-actions bot commented Jan 14, 2026

Errors are Unable to load ticket data
https://daosio.atlassian.net/browse/SRE-3534

Priority: 2

Skip-unit-tests:true

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
Cancel-prev-build: false
Priority: 2

Allow-unstable-test: true

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
@daosbuild3
Copy link
Collaborator

Test stage Unit Test bdev with memcheck on EL 9.7 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17376/3/display/redirect

@daosbuild3
Copy link
Collaborator

Test stage Unit Test on EL 9.7 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17376/3/display/redirect

@daosbuild3
Copy link
Collaborator

Test stage Unit Test bdev on EL 9.7 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17376/3/display/redirect

@daosbuild3
Copy link
Collaborator

Test stage Unit Test with memcheck on EL 9.7 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17376/3/display/redirect

@daosbuild3
Copy link
Collaborator

Test stage NLT on EL 9.7 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17376/3/display/redirect

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Cancel-prev-build: false
Priority: 2

Skip-unit-tests:true

Allow-unstable-test: true

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
@daosbuild3
Copy link
Collaborator

Test stage Unit Test with memcheck on EL 9.7 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17376/4/testReport/

@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Test stage Unit Test bdev with memcheck on EL 9.7 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17376/4/testReport/

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
Cancel-prev-build: false
Priority: 2

Skip-build-leap15-gcc: true

Skip-unit-tests:true
Skip-unit-test: true
Skip-NLT: false
Skip-unit-test-memcheck: true

Allow-unstable-test: true

Skip-func-vm: true

Skip-func-hw-test-medium: false
Skip-func-hw-test-medium-md-on-ssd: false
Skip-func-hw-test-medium-vmd: false
Skip-func-hw-test-medium-verbs-provider: false
Skip-func-hw-test-medium-verbs-provider-md-on-ssd: false
Skip-func-hw-test-medium-ucx-provider: false
Skip-func-hw-test-large: false
Skip-func-hw-test-large-md-on-ssd: false

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
Cancel-prev-build: false
Priority: 2

Skip-build-leap15-gcc: true

Allow-unstable-test: true

Skip-func-vm: true

Skip-func-hw-test: true

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
@daosbuild3
Copy link
Collaborator

Test stage Unit Test with memcheck on EL 9.7 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17376/8/testReport/

@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Test stage Unit Test bdev with memcheck on EL 9.7 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17376/8/testReport/

Cancel-prev-build: false
Priority: 2

Skip-build-leap15-gcc: true

Skip-unit-tests:true
Skip-unit-test: true
Skip-NLT: true
Skip-unit-test-memcheck: true

Skip-func-vm: true
Skip-func-test-vm-valgrind: true
Skip-func-test-el8: true
Skip-func-test-el9: true
Skip-func-test-leap15: true
Skip-fault-injection-test: true
Skip-test-el-9.6-rpms: false
Skip-test-leap-15-rpms: true

Skip-func-hw-test-medium: false
Skip-func-hw-test-medium-md-on-ssd: false
Skip-func-hw-test-medium-vmd: false
Skip-func-hw-test-medium-verbs-provider: false
Skip-func-hw-test-medium-verbs-provider-md-on-ssd: false
Skip-func-hw-test-medium-ucx-provider: false
Skip-func-hw-test-large: false
Skip-func-hw-test-large-md-on-ssd: false

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
Cancel-prev-build: false
Priority: 2

Skip-build-leap15-gcc: true

Skip-unit-tests:true
Skip-unit-test: true
Skip-NLT: false
Skip-unit-test-memcheck: true

Allow-unstable-test: true

Skip-func-vm: true
Skip-func-test-vm-valgrind: true
Skip-func-test-el8: true
Skip-func-test-el9: true
Skip-func-test-leap15: true
Skip-fault-injection-test: true
Skip-test-el-9.6-rpms: true
Skip-test-leap-15-rpms: true

Skip-func-hw-test: false
Skip-func-hw-test-medium: false
Skip-func-hw-test-medium-md-on-ssd: false
Skip-func-hw-test-medium-vmd: false
Skip-func-hw-test-medium-verbs-provider: false
Skip-func-hw-test-medium-verbs-provider-md-on-ssd: false
Skip-func-hw-test-medium-ucx-provider: false
Skip-func-hw-test-large: false
Skip-func-hw-test-large-md-on-ssd: false

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>
@daosbuild3
Copy link
Collaborator

Test stage Functional on EL 9.7 completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos/job/PR-17376/10/display/redirect

@grom72 grom72 changed the title SRE-3522 ci: test CI with el9.7 SRE-3534 ci: test CI with el9.7 Jan 16, 2026
Copy link
Contributor

@JohnMalmberg JohnMalmberg left a comment

Choose a reason for hiding this comment

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

Some general comments for potentially future cleanup.

}
}
stage('Build on EL 9.6') {
stage('Build on EL 9.7') {
Copy link
Contributor

Choose a reason for hiding this comment

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

For EL distros we generally intentionally build on el-X.Y older than current. Sometimes even numbered releases can have longer term support, and code built for el-9 of any older release in general should work on any older release.

}
parallel {
stage('Unit Test on EL 8.8') {
stage('Unit Test on EL 9.7') {
Copy link
Contributor

Choose a reason for hiding this comment

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

We should not be specifying the point release for tests, we should always test on the current point release.

We should also have the ability of a PR to test on a beta release of a point release. Currently our testing infrastructure is not setup to provide beta releases.

Copy link
Contributor

Choose a reason for hiding this comment

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

Just FYI that changing the names of these stages means the landing requirements need to be updated. I'll handle that when landing

testResults: 'nlt-junit.xml',
always_script: 'ci/unit/test_nlt_post.sh',
valgrind_stash: 'el8-gcc-nlt-memcheck'
valgrind_stash: 'el9-gcc-nlt-memcheck'
Copy link
Contributor

Choose a reason for hiding this comment

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

The pipeline-lib routine parseStageInfo should be providing the default value for the valgrind stash to make sure that it is correct and consistent instead of having to maintain this edit.

Copy link
Contributor

Choose a reason for hiding this comment

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

IMO we should not rely on such a function to parse the stage name to determine the stash name. Functions of that nature have proven to be notorious to debug, modify, or even understand the flow.
It might be redundant here but I think this approach is actually better.

}
} // stage('Functional on EL 8.8')
stage('Functional on EL 9') {
stage('Functional on EL 9.7') {
Copy link
Contributor

Choose a reason for hiding this comment

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

We control what el-9 point release is used for outside of Jenkins for these tests. The only time we don't want to test the current version is if we need to fix a problem with using the current point release, and the usual problem is that we are waiting for a custom driver from the high speed network adapter vendor, and that only affects hardware tests.

Copy link
Contributor

Choose a reason for hiding this comment

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

+1. I think this should stay as Functional on EL 9. It also means we won't have to change the landing requirements for this one

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The intention of this change is to clearly indicate which version of OS we actually fully support.
This stems from release requirements, e.g., for 2.8, support for el9.7, and it is not clear anywhere whether this is maintained.

The alternative solution is to keep the original name, but start using the distro parameter in the getFunctionalTestStage function in Jenkinsfile
https://github.com/daos-stack/pipeline-lib/blob/cb2788756bc1179cda14db3c21650b05e400b175/vars/getFunctionalTestStage.groovy#L20

Copy link
Contributor

Choose a reason for hiding this comment

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

I do think it's better to specify the distro explicitly. Putting 9.7 in the name of the stage does not necessarily mean we are running on 9.7. It's just a name.
Also, variables like CI_FUNCTIONAL_el9_TEST do not have the point release in them so omitting the point release in the name keeps them consistent.

@grom72 grom72 changed the title SRE-3534 ci: test CI with el9.7 SRE-3534 ci: CI to use el9.7 (quick solution) Jan 16, 2026
@daosbuild3
Copy link
Collaborator

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

@daosbuild3
Copy link
Collaborator

// To use a test branch (i.e. PR) until it lands to master
// I.e. for testing library changes
//@Library(value='pipeline-lib@your_branch') _
@Library(value='pipeline-lib@grom72/SRE-3522') _
Copy link
Contributor

Choose a reason for hiding this comment

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

Note to selves: we need to remove before landing

}
parallel {
stage('Unit Test on EL 8.8') {
stage('Unit Test on EL 9.7') {
Copy link
Contributor

Choose a reason for hiding this comment

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

Just FYI that changing the names of these stages means the landing requirements need to be updated. I'll handle that when landing

testResults: 'nlt-junit.xml',
always_script: 'ci/unit/test_nlt_post.sh',
valgrind_stash: 'el8-gcc-nlt-memcheck'
valgrind_stash: 'el9-gcc-nlt-memcheck'
Copy link
Contributor

Choose a reason for hiding this comment

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

IMO we should not rely on such a function to parse the stage name to determine the stash name. Functions of that nature have proven to be notorious to debug, modify, or even understand the flow.
It might be redundant here but I think this approach is actually better.

}
} // stage('Functional on EL 8.8')
stage('Functional on EL 9') {
stage('Functional on EL 9.7') {
Copy link
Contributor

Choose a reason for hiding this comment

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

+1. I think this should stay as Functional on EL 9. It also means we won't have to change the landing requirements for this one

@daosbuild3
Copy link
Collaborator

Test stage Functional Hardware Large MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17376/11/execution/node/922/log

@grom72 grom72 changed the title SRE-3534 ci: CI to use el9.7 (quick solution) SRE-3534 ci: adapt CI to use el9.7 Jan 19, 2026
@daosbuild3
Copy link
Collaborator

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

@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Test stage Functional Hardware Large MD on SSD completed with status FAILURE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net//job/daos-stack/job/daos/view/change-requests/job/PR-17376/16/execution/node/757/log

Signed-off-by: Tomasz Gromadzki <tomasz.gromadzki@hpe.com>

Cancel-prev-build: false
Priority: 2

Allow-unstable-test: true

Skip-func-test-vm-valgrind: false
Skip-func-test-el8: false
Skip-func-test-el9: false

Skip-func-hw-test-medium: false
Skip-func-hw-test-medium-md-on-ssd: false
Skip-func-hw-test-medium-vmd: false
Skip-func-hw-test-medium-verbs-provider: false
Skip-func-hw-test-medium-verbs-provider-md-on-ssd: false
Skip-func-hw-test-medium-ucx-provider: false
Skip-func-hw-test-large: false
Skip-func-hw-test-large-md-on-ssd: false
@daosbuild3
Copy link
Collaborator

@daosbuild3
Copy link
Collaborator

Test stage Unit Test with memcheck on EL 9.7 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17376/19/testReport/

@daosbuild3
Copy link
Collaborator

Test stage Unit Test bdev with memcheck on EL 9.7 completed with status UNSTABLE. https://jenkins-3.daos.hpc.amslabs.hpecorp.net/job/daos-stack/job/daos//view/change-requests/job/PR-17376/19/testReport/

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

5 participants