Skip to content

A suggestion, not an issue (anymore). #15

@stevenjblair

Description

@stevenjblair

I kept getting these endpoint failures and could not get any of the software I really needed installed. I'm new to spack, so it was really frustrating.

I have these files building up in the /tmp/user/spack-stage and I just assumed they were just text logs.

Anyhow, I suggest you mention somewhere that if you are getting errors like this:
`==> Error: BrokenPipeError: [Errno 108] Cannot send after transport endpoint shutdown: '/n/holylabs/LABS/jharvard_lab/Lab/software/spack'
See build log for details:
/tmp/sjblair/spack-stage/spack-stage-automake-1.16.5-h2oi3k5nk3pivmgggizheq2lzqvrdyzi/spack-build-out.txt

==> Error: [Errno 108] Cannot send after transport endpoint shutdown: '/n/holylabs/LABS'`

That you can simply fix it with:
spack clean --all

I was getting a lot of different errors all week, "clearing the cache" is always a go-to but for those of us who have not used spack before it would be good to have how to clear all of it out in the fasrc documentation. spack clean -m was not enough to put an end to all these errors.

Anyhow, I hope this helps someone else. Took me an embarrassing amount of time to figure it out on my own.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions