diff options
Diffstat (limited to '.github')
| -rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.md | 41 | ||||
| -rw-r--r-- | .github/ISSUE_TEMPLATE/build_error.md | 79 | ||||
| -rw-r--r-- | .github/ISSUE_TEMPLATE/feature_request.md | 21 | ||||
| -rw-r--r-- | .github/workflows/linux_build_tests.yaml | 5 | ||||
| -rw-r--r-- | .github/workflows/minimum_python_versions.yaml | 2 |
5 files changed, 57 insertions, 91 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index f647b52036..9a568285ea 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -1,14 +1,11 @@ --- -name: Bug report -about: Report a bug in the core of Spack (command not working as expected, etc.) -labels: bug +name: "\U0001F41E Bug report" +about: Report a bug in the core of Spack (command not working as expected, etc.) +labels: "bug,triage" --- - -*Explain, in a clear and concise way, the command you ran and the result you were trying to achieve. -Example: "I ran Spack find to list all the installed packages and..."* - - +<!-- Explain, in a clear and concise way, the command you ran and the result you were trying to achieve. +Example: "I ran `spack find` to list all the installed packages and ..." --> ### Steps to reproduce the issue @@ -20,30 +17,26 @@ $ spack <command2> <spec> ### Error Message -If Spack reported an error, provide the error message. If it did not report an error -but the output appears incorrect, provide the incorrect output. If there was no error -message and no output but the result is incorrect, describe how it does not match -what you expect. To provide more information you might re-run the commands with -the additional -d/--stacktrace flags: +<!-- If Spack reported an error, provide the error message. If it did not report an error but the output appears incorrect, provide the incorrect output. If there was no error message and no output but the result is incorrect, describe how it does not match what you expect. --> ```console -$ spack -d --stacktrace <command1> <spec> -$ spack -d --stacktrace <command2> <spec> -... +$ spack --debug --stacktrace <command> ``` -that activate the full debug output. - ### Information on your system -This includes: +<!-- Please include the output of `spack debug report` --> + +<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. --> - 1. which platform you are using - 2. any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) +### Additional information ------ +<!-- These boxes can be checked by replacing [ ] with [x] or by clicking them after submitting the issue. --> +- [ ] I have run `spack debug report` and reported the version of Spack/Python/Platform +- [ ] I have searched the issues of this repo and believe this is not a duplicate +- [ ] I have run the failing commands in debug mode and reported the output -We encourage you to try, as much as possible, to reduce your problem to the minimal example that still reproduces the issue. That would help us a lot in fixing it quickly and effectively! +<!-- We encourage you to try, as much as possible, to reduce your problem to the minimal example that still reproduces the issue. That would help us a lot in fixing it quickly and effectively! If you want to ask a question about the tool (how to use it, what it can currently do, etc.), try the `#general` channel on our Slack first. We have a welcoming community and chances are you'll get your reply faster and without opening an issue. -Other than that, thanks for taking the time to contribute to Spack! +Other than that, thanks for taking the time to contribute to Spack! --> diff --git a/.github/ISSUE_TEMPLATE/build_error.md b/.github/ISSUE_TEMPLATE/build_error.md index 3f36cf93cb..d26db233d3 100644 --- a/.github/ISSUE_TEMPLATE/build_error.md +++ b/.github/ISSUE_TEMPLATE/build_error.md @@ -1,78 +1,43 @@ --- -name: Build error -about: Some package in Spack didn't build correctly +name: "\U0001F4A5 Build error" +about: Some package in Spack didn't build correctly +title: "Installation issue: " labels: "build-error" --- -*Thanks for taking the time to report this build failure. To proceed with the -report please:* +<!-- Thanks for taking the time to report this build failure. To proceed with the report please: + 1. Title the issue "Installation issue: <name-of-the-package>". 2. Provide the information required below. -3. Remove the template instructions before posting the issue. - -We encourage you to try, as much as possible, to reduce your problem to the minimal example that still reproduces the issue. That would help us a lot in fixing it quickly and effectively! - ---- +We encourage you to try, as much as possible, to reduce your problem to the minimal example that still reproduces the issue. That would help us a lot in fixing it quickly and effectively! --> ### Steps to reproduce the issue +<!-- Fill in the exact spec you are trying to build and the relevant part of the error message --> ```console -$ spack install <spec> # Fill in the exact spec you are using -... # and the relevant part of the error message +$ spack install <spec> +... ``` -### Platform and user environment +### Information on your system -Please report your OS here: -```commandline -$ uname -a -Linux nuvolari 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -$ lsb_release -d -Description: Ubuntu 18.04.1 LTS -``` -and, if relevant, post or attach: +<!-- Please include the output of `spack debug report` --> -- `packages.yaml` -- `compilers.yaml` - -to the issue +<!-- If you have any relevant configuration detail (custom `packages.yaml` or `modules.yaml`, etc.) you can add that here as well. --> ### Additional information -Sometimes the issue benefits from additional details. In these cases there are -a few things we can suggest doing. First of all, you can post the full output of: -```console -$ spack spec --install-status <spec> -... -``` -to show people whether Spack installed a faulty software or if it was not able to -build it at all. +<!-- Please upload the following files. They should be present in the stage directory of the failing build. Also upload any config.log or similar file if one exists. --> +* [spack-build-out.txt]() +* [spack-build-env.txt]() -If your build didn't make it past the configure stage, Spack as also commands to parse -logs and report error and warning messages: -```console -$ spack log-parse --show=errors,warnings <file-to-parse> -``` -You might want to run this command on the `config.log` or any other similar file -found in the stage directory: -```console -$ spack location -s <spec> -``` -In case in `config.log` there are other settings that you think might be the cause -of the build failure, you can consider attaching the file to this issue. - -Rebuilding the package with the following options: -```console -$ spack -d install -j 1 <spec> -... -``` -will provide additional debug information. After the failure you will find two files in the current directory: +<!-- Some packages have maintainers who have volunteered to debug build failures. Run `spack maintainers <name-of-the-package>` and @mention them here if they exist. --> -1. `spack-cc-<spec>.in`, which contains details on the command given in input - to Spack's compiler wrapper -1. `spack-cc-<spec>.out`, which contains the command used to compile / link the - failed object after Spack's compiler wrapper did its processing +### General information -You can post or attach those files to provide maintainers with more information on what -is causing the failure. +<!-- These boxes can be checked by replacing [ ] with [x] or by clicking them after submitting the issue. --> +- [ ] I have run `spack debug report` and reported the version of Spack/Python/Platform +- [ ] I have run `spack maintainers <name-of-the-package>` and @mentioned any maintainers +- [ ] I have uploaded the build log and environment files +- [ ] I have searched the issues of this repo and believe this is not a duplicate diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 35481fecb7..b6e5e27e6f 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -1,28 +1,33 @@ --- -name: Feature request +name: "\U0001F38A Feature request" about: Suggest adding a feature that is not yet in Spack labels: feature --- -*Please add a concise summary of your suggestion here.* +<!--*Please add a concise summary of your suggestion here.*--> ### Rationale -*Is your feature request related to a problem? Please describe it!* +<!--*Is your feature request related to a problem? Please describe it!*--> ### Description -*Describe the solution you'd like and the alternatives you have considered.* +<!--*Describe the solution you'd like and the alternatives you have considered.*--> ### Additional information -*Add any other context about the feature request here.* +<!--*Add any other context about the feature request here.*--> ------ +### General information +- [ ] I have run `spack --version` and reported the version of Spack +- [ ] I have searched the issues of this repo and believe this is not a duplicate -If you want to ask a question about the tool (how to use it, what it can currently do, etc.), try the `#general` channel on our Slack first. We have a welcoming community and chances are you'll get your reply faster and without opening an issue. -Other than that, thanks for taking the time to contribute to Spack!
\ No newline at end of file + +<!--If you want to ask a question about the tool (how to use it, what it can currently do, etc.), try the `#general` channel on our Slack first. We have a welcoming community and chances are you'll get your reply faster and without opening an issue. + +Other than that, thanks for taking the time to contribute to Spack! +-->
\ No newline at end of file diff --git a/.github/workflows/linux_build_tests.yaml b/.github/workflows/linux_build_tests.yaml index 27be6c3c18..d6f98a1627 100644 --- a/.github/workflows/linux_build_tests.yaml +++ b/.github/workflows/linux_build_tests.yaml @@ -18,6 +18,8 @@ on: - '!var/spack/repos/builtin/packages/py-setuptools/**' - '!var/spack/repos/builtin/packages/openjpeg/**' - '!var/spack/repos/builtin/packages/r-rcpp/**' + # Don't run if we only modified documentation + - 'lib/spack/docs/**' jobs: build: @@ -28,7 +30,7 @@ jobs: matrix: package: [lz4, mpich, tut, py-setuptools, openjpeg, r-rcpp] steps: - - uses: actions/checkout@v1 + - uses: actions/checkout@v2 - name: Cache ccache's store uses: actions/cache@v1 with: @@ -42,6 +44,7 @@ jobs: python-version: 3.8 - name: Install System Packages run: | + sudo apt-get update sudo apt-get -yqq install ccache gfortran perl perl-base r-base r-base-core r-base-dev findutils openssl libssl-dev libpciaccess-dev R --version perl --version diff --git a/.github/workflows/minimum_python_versions.yaml b/.github/workflows/minimum_python_versions.yaml index c55042ffa1..95bc9af358 100644 --- a/.github/workflows/minimum_python_versions.yaml +++ b/.github/workflows/minimum_python_versions.yaml @@ -15,7 +15,7 @@ jobs: runs-on: ubuntu-latest steps: - - uses: actions/checkout@v1 + - uses: actions/checkout@v2 - name: Setup Python uses: actions/setup-python@v1 with: |