-
Notifications
You must be signed in to change notification settings - Fork 307
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
DAOS-16621 build: Fix Go versions in rpm/deb packaging (#15174) #15255
DAOS-16621 build: Fix Go versions in rpm/deb packaging (#15174) #15255
Conversation
- Set Go minimum version to 1.21 in rpm and debian packaging spec files. - Update scons Go version check to use version in go.mod. - Add a reminder in go.mod file so we remember the packaging files when bumping the minimum Go version in the future. - Update Ubuntu 22.04 Dockerfile to get an appropriate version of Go. Required-githooks: true Signed-off-by: Kris Jacque <[email protected]>
No need for Features tags, as this affects only builds. Both conflicts in the cherry-pick were in the changelog section of the RPM specfile and the Debian changelog. |
Ticket title is 'Fix Go version checks in scons and packaging specfiles' |
@@ -81,7 +81,7 @@ BuildRequires: libyaml-devel | |||
BuildRequires: libcmocka-devel | |||
BuildRequires: valgrind-devel | |||
BuildRequires: systemd | |||
BuildRequires: go >= 1.17 | |||
BuildRequires: go >= 1.21 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A bit late now I suppose since the master PR for this has already landed, but you could add a new %global go_version 1.21
after
Line 7 in b227b4a
%global libfabric_version 1.15.1-1 |
BuildRequires: go >= 1.21 | |
BuildRequires: go >= %{go_version} |
and the same for
Line 221 in b227b4a
Requires: go >= 1.21 |
Maybe next time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the tip, Brian. Yeah, we should probably make that fix at the master level first.
NLT failures appear to be unrelated to this PR. I've added the |
Allow-unstable-test: true
Dug deeper into the NLT instability and created a ticket: https://daosio.atlassian.net/browse/DAOS-16716 This affects any 2.6 PR, not just this one. |
Required-githooks: true
Test stage Functional Hardware Medium completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15255/7/execution/node/1430/log |
FYI release/2.6 currently closed until we cut a test build for Aurora acceptance |
@kjacque There are conflicts again. And FYI 2.6 is open now |
Required-githooks: true
Required-githooks: true Signed-off-by: Kris Jacque <[email protected]>
Test stage Build RPM on EL 8 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15255/9/execution/node/352/log |
Test stage Build DEB on Ubuntu 20.04 completed with status FAILURE. https://build.hpdd.intel.com//job/daos-stack/job/daos/view/change-requests/job/PR-15255/9/execution/node/357/log |
Test stage NLT on EL 8.8 completed with status UNSTABLE. https://build.hpdd.intel.com/job/daos-stack/job/daos//view/change-requests/job/PR-15255/11/testReport/ |
Required-githooks: true
Before requesting gatekeeper:
Features:
(orTest-tag*
) commit pragma was used or there is a reason documented that there are no appropriate tags for this PR.Gatekeeper: