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

Benchpark output build params #550

Open
4 tasks
pearce8 opened this issue Jan 17, 2025 · 2 comments
Open
4 tasks

Benchpark output build params #550

pearce8 opened this issue Jan 17, 2025 · 2 comments
Assignees
Labels
ci CI, unit tests, GitHub actions feature New feature or request
Milestone

Comments

@pearce8
Copy link
Collaborator

pearce8 commented Jan 17, 2025

For those unable/unwilling to use Spack, we need to generate the equivalent of Building instructions

  • Check if the benchmark uses auto tools or cmake @scheibelp
  • Build the benchmark in CI @slabasan
  • Output appropriate params to a file @scheibelp
  • If the run passed, add the new instructions to the Sphinx page like this one @slabasan
@pearce8 pearce8 added the feature New feature or request label Jan 17, 2025
@pearce8 pearce8 changed the title Benchpark output cmake params Benchpark output cmake params, runtime params Jan 18, 2025
@pearce8 pearce8 assigned becker33 and unassigned rfhaque Jan 22, 2025
@pearce8 pearce8 changed the title Benchpark output cmake params, runtime params Benchpark output build params Jan 24, 2025
@becker33
Copy link
Collaborator

Here's my idea of approximately what that looks like when put into a documentation page

AMG build section

LLNL will be building AMG with Spack through benchpark. The Spack package is available at … and benchpark is available at …

On El Capitan, Spack uses the following commands to build:

./configure .………..       <——this can be extracted by echo “./configure $(cat $(spack location -i amg)/.spack/spack-configure-args.txt)"
make
make install

For explanations of the AMG build options, run …

@becker33
Copy link
Collaborator

Spack extracts this information for both autotools and cmake, but it looks like there's a bug with the cmake extraction. @scheibelp have you looked at this code on the Spack side recently?

@pearce8 pearce8 assigned scheibelp and slabasan and unassigned becker33 Jan 24, 2025
@pearce8 pearce8 added help wanted ci CI, unit tests, GitHub actions and removed help wanted labels Jan 24, 2025
@pearce8 pearce8 added this to the Urgent v0.1.1 milestone Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci CI, unit tests, GitHub actions feature New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants