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

Pin jemalloc to v5.2.0 for install package #37405

Merged
merged 4 commits into from
May 22, 2024

Conversation

peterfpeterson
Copy link
Member

@peterfpeterson peterfpeterson commented May 20, 2024

This makes the mantid package installer match the version of jemalloc that the developers are using.

Refs #36220 .

Further detail of work

The main change is to pin the version of jemalloc for the package to v5.2.0. It is unclear what is wrong with the newer versions, but comparing the recipe from v5.2.0 and recipe from v5.3.0 one will immediately discover that v5.3.0 reworked the packages so there is now a jemalloc package libjemalloc package where v5.2.0 only has jemalloc package. More investigation will need to be done to figure out how to move forward from v5.2.0.

The oddity is that both v5.2.0 and v5.3.0 work on rhel7, but only v5.2.0 works on rocky8 and rhel9.

There is some extra cleanup of the developer dependencies so they can more easily be compared using diff (sorting), removing duplicate dependencies (conda-wrappers twice in windows), removing unused osx dependency (jemalloc is not runtime for mac).

Bonus information: The abi compatibility chart for jemalloc doesn't go all the way to v5.3.0.

To test:

Install the built linux package on newer rhel and see that it can start and show the instrument view with opengl.

This does not require release notes because it is fixing a bug within the release cycle discovered when moving from rhel7.


Reviewer

Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

  • Is the code of an acceptable quality?
  • Does the code conform to the coding standards?
  • Are the unit tests small and test the class in isolation?
  • If there is GUI work does it follow the GUI standards?
  • If there are changes in the release notes then do they describe the changes appropriately?
  • Do the release notes conform to the release notes guide?

Functional Tests

  • Do changes function as described? Add comments below that describe the tests performed?
  • Do the changes handle unexpected situations, e.g. bad input?
  • Has the relevant (user and developer) documentation been added/updated?

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.

It is not included in the package dependencies. This also sorts the
dependencies so diff shows more meaningful information when comparing
the platforms.
v5.2.1 has an issue for some tests, v5.3.0 doesn't want to work
on rhel9
@peterfpeterson peterfpeterson added the Bug Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing) label May 20, 2024
@peterfpeterson peterfpeterson added this to the Release 6.10 milestone May 20, 2024
@sf1919
Copy link
Contributor

sf1919 commented May 21, 2024

Can we point this at release-next?

@peterfpeterson peterfpeterson changed the base branch from main to release-next May 21, 2024 12:54
@peterfpeterson
Copy link
Member Author

peterfpeterson commented May 21, 2024

Linux package build 1860 is resubmitted against release-next

@thomashampson thomashampson self-assigned this May 21, 2024
Copy link
Contributor

@thomashampson thomashampson left a comment

Choose a reason for hiding this comment

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

There's a small typo that will probably affect macOS packaging

conda/recipes/mantid/meta.yaml Outdated Show resolved Hide resolved
Co-authored-by: thomashampson <thomas.hampson@stfc.ac.uk>
Copy link
Contributor

@thomashampson thomashampson left a comment

Choose a reason for hiding this comment

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

I'm happy for this go in to resolve issues on rhel9, and work on a rocky8 fix separately

@jmborr jmborr enabled auto-merge May 22, 2024 17:04
@jmborr jmborr merged commit abf94c6 into mantidproject:release-next May 22, 2024
10 checks passed
@jmborr jmborr deleted the jemalloc_pin branch May 22, 2024 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues and pull requests that are regressions or would be considered a bug by users (e.g. crashing)
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants