-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Spack build failures do not output a path to the spack-build.out log file #150
Labels
bug
Something isn't working
Comments
tgamblin
added a commit
that referenced
this issue
Nov 5, 2015
- `remove_prefix` was modified to remove from the DB, but the package may not have been added to the DB yet when `remove_prefix` is called from `cleanup`. - Made `remove_prefix` a pure utility function (it just removes the prefix) - Added `installed_db.remove()` call only after the `remove_prefix` in `uninstall`.
@PaulDapolito: this should be fixed by 0d99394. Can you verify? |
I've seen this work just fine since then.
|
matz-e
pushed a commit
to matz-e/spack
that referenced
this issue
Jan 28, 2019
* Neuron package update: - use multisend if mpi is enabled - python is also run depndency for extensions * Update Piz Daint configurations
climbfuji
added a commit
to climbfuji/spack
that referenced
this issue
Aug 5, 2022
…netcdf_fortran Bug fix for crtm: JEDI release depends on netCDF-Fortran
vitodb
pushed a commit
to vitodb/spack
that referenced
this issue
Jul 10, 2023
…#150) Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 4.0.0 to 4.1.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@3b5e802...44ea916) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a spack build fails, it no longer shows a path to the spack-build.out log file. For example:
The text was updated successfully, but these errors were encountered: