Skip to content

Add new survey package to spack. #25518

Merged
adamjstewart merged 14 commits intospack:developfrom
OpenSpeedShop:add_survey
Jan 14, 2022
Merged

Add new survey package to spack. #25518
adamjstewart merged 14 commits intospack:developfrom
OpenSpeedShop:add_survey

Conversation

@jgalarowicz
Copy link
Copy Markdown
Contributor

Add new package to spack. survey is a lightweight application performance tool that also gathers system information and stores it as metadata.

…ance tool that also gathers system information and stores it as metadata.
@spackbot-app
Copy link
Copy Markdown

spackbot-app bot commented Aug 19, 2021

Hi @jgalarowicz! I noticed that the following package(s) don't yet have maintainers:

  • survey

Are you interested in adopting any of these package(s)? If so, simply add the following to the package class:

    maintainers = ['jgalarowicz']

If not, could you contact the developers of this package and see if they are interested? You can quickly see who has worked on a package with spack blame:

$ spack blame survey

Thank you for your help! Please don't add maintainers without their consent.

You don't have to be a Spack expert or package developer in order to be a "maintainer," it just gives us a list of users willing to review PRs or debug issues relating to this package. A package can have multiple maintainers; just add a list of GitHub handles of anyone who wants to volunteer.

@alalazo alalazo assigned alalazo and unassigned alalazo Aug 20, 2021
@jgalarowicz jgalarowicz removed the request for review from mplegendre September 2, 2021 00:34
@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@alalazo @adamjstewart Hi - anything else you would like me to do for this new package? Thanks much!

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@haampie @adamjstewart @becker33 I think I have all the changes in that I can do. The mpi changes won't work because we support multiple mpi collectors, so we need to have the multiple variants and support for using multiple MPI collectors.

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@haampie @becker33 @adamjstewart I guess there is a problem with the multiple MPI builds. Jennifer Green @lanl said she was discussing with Greg and the way it is now won't work for the production builds. So, our survey group will have to discuss. More to come...

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@haampie @becker33 @adamjstewart I have checked in the code to move to the +mpi variant approach where only one MPI collector is built. I tested it on my laptop and it works when I build using this line:

spack install --keep-stage [email protected]  %[email protected] +mpi ^[email protected]

So, I believe I have changed the survey package.py file to meet everyone's comments and suggestions. Let me know if more changes are required. Thanks for all the help!

adamjstewart
adamjstewart previously approved these changes Oct 21, 2021
Copy link
Copy Markdown
Member

@adamjstewart adamjstewart left a comment

Choose a reason for hiding this comment

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

Looks good enough to me. I don't have access to this software so I have no way to see if the deps are correct or not.

@adamjstewart adamjstewart requested a review from becker33 October 21, 2021 21:09
@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@becker33 - Hi Greg, I hope SC21 went well! Will you have time to review this PR sometime soon? Thanks - Jim G

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@becker33 Just checking again on this one. It would be good for our team if this could get merged. Thanks again!

Copy link
Copy Markdown
Contributor Author

@jgalarowicz jgalarowicz left a comment

Choose a reason for hiding this comment

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

I believe this is resolved, but not marked as such.

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart Hi Adam - Is there anything I need to do for this to get approved? Just checking to see if I'm missing something and if I need to do something to move it along. Thanks.

Copy link
Copy Markdown
Member

@adamjstewart adamjstewart left a comment

Choose a reason for hiding this comment

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

Some suggested changes to Python deptypes. Again, I don't have access to the source code, so I have no idea if these deps are correct or what their types should actually be. If you can share the following files with me (if they exist) that would be really helpful:

  • pyproject.toml
  • setup.py
  • setup.cfg
  • requirements.txt

@adamjstewart
Copy link
Copy Markdown
Member

Tests are failing due to a syntax error. Since it seems to only affect Python 2, I'm guessing there's some unicode somewhere in the file, likely in the docstring. I would replace things like dashes with manually-typed dashes to make sure they are ASCII.

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart We only support Python 3 and above. Would that make the tests fail?

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart I will check the docstring and replace. Thanks for the tip!

@adamjstewart
Copy link
Copy Markdown
Member

That wouldn't make the tests fail, most of Spack's Python packages only support Python 3.

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart I did find one dash that didn't look quite like a normal dash. Hopefully, it will work now. Thanks again!

@adamjstewart adamjstewart enabled auto-merge (squash) December 31, 2021 02:29
@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart @becker33 Does Greg still have to review the changes or is this set to merge when the next auto-merge happens? Thanks for your time!

@adamjstewart
Copy link
Copy Markdown
Member

I'll give @becker33 a few more days to review, if you don't hear anything let me know and I'll merge.

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart -- Ok. Thanks for the reply!

@jgalarowicz
Copy link
Copy Markdown
Contributor Author

@adamjstewart If you can merge this, please do. It looks like Greg isn't getting to it. Thank you!

@adamjstewart adamjstewart dismissed becker33’s stale review January 14, 2022 01:59

Request changes have been implemented

@adamjstewart adamjstewart merged commit b7accb6 into spack:develop Jan 14, 2022
RikkiButler20 pushed a commit to RikkiButler20/spack that referenced this pull request Feb 1, 2022
* Add new package to spack.  survey is a lightweight application performance tool that also gathers system information and stores it as metadata.

* Add maintainer and note about source access.

* Update the man path per spack reviewer suggestion.

* Remove redundant settings for PYTHONPATH, PATH, and MANPATH.

* Move to a one mpi collector approach for cce/tce integration.

* Add pyyaml dependency

* Make further spack reviewer changes to python type specs, mpi args, build type variant.

* Add reviewer requested changes.

* Add reviewer docstring requested changes.

* Add more updates from spack reviewer comments.

* Update the versions to use tags, not branches

* Redo dashes to fix issue with spack testing.

Co-authored-by: Jim Galarowicz <[email protected]>
RikkiButler20 pushed a commit to RikkiButler20/spack that referenced this pull request Feb 1, 2022
* Add new package to spack.  survey is a lightweight application performance tool that also gathers system information and stores it as metadata.

* Add maintainer and note about source access.

* Update the man path per spack reviewer suggestion.

* Remove redundant settings for PYTHONPATH, PATH, and MANPATH.

* Move to a one mpi collector approach for cce/tce integration.

* Add pyyaml dependency

* Make further spack reviewer changes to python type specs, mpi args, build type variant.

* Add reviewer requested changes.

* Add reviewer docstring requested changes.

* Add more updates from spack reviewer comments.

* Update the versions to use tags, not branches

* Redo dashes to fix issue with spack testing.

Co-authored-by: Jim Galarowicz <[email protected]>
RikkiButler20 pushed a commit to RikkiButler20/spack that referenced this pull request Feb 8, 2022
* Add new package to spack.  survey is a lightweight application performance tool that also gathers system information and stores it as metadata.

* Add maintainer and note about source access.

* Update the man path per spack reviewer suggestion.

* Remove redundant settings for PYTHONPATH, PATH, and MANPATH.

* Move to a one mpi collector approach for cce/tce integration.

* Add pyyaml dependency

* Make further spack reviewer changes to python type specs, mpi args, build type variant.

* Add reviewer requested changes.

* Add reviewer docstring requested changes.

* Add more updates from spack reviewer comments.

* Update the versions to use tags, not branches

* Redo dashes to fix issue with spack testing.

Co-authored-by: Jim Galarowicz <[email protected]>
EthanS94 pushed a commit to EthanS94/spack that referenced this pull request Feb 17, 2022
* Add new package to spack.  survey is a lightweight application performance tool that also gathers system information and stores it as metadata.

* Add maintainer and note about source access.

* Update the man path per spack reviewer suggestion.

* Remove redundant settings for PYTHONPATH, PATH, and MANPATH.

* Move to a one mpi collector approach for cce/tce integration.

* Add pyyaml dependency

* Make further spack reviewer changes to python type specs, mpi args, build type variant.

* Add reviewer requested changes.

* Add reviewer docstring requested changes.

* Add more updates from spack reviewer comments.

* Update the versions to use tags, not branches

* Redo dashes to fix issue with spack testing.

Co-authored-by: Jim Galarowicz <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants