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

spack test leaves behind config.yaml file #13009

Closed
adamjstewart opened this issue Oct 2, 2019 · 5 comments · Fixed by #12857
Closed

spack test leaves behind config.yaml file #13009

adamjstewart opened this issue Oct 2, 2019 · 5 comments · Fixed by #12857
Assignees
Labels
bug configuration tests General test capability(ies)

Comments

@adamjstewart
Copy link
Member

When I run spack test, it leaves behind a config.yaml that shouldn't be there.

Steps to reproduce the issue

$ cat ~/.spack/config.yaml
cat: /Users/Adam/.spack/config.yaml: No such file or directory
$ spack test
...
$ cat ~/.spack/config.yaml 
config:
  build_stage: /private/var/folders/21/hwq39zyj4g36x6zjfyl5l8080000gn/T/pytest-of-Adam/pytest-1/mock-stage0

Information on your system

  • macOS 10.14.6
  • Python 3.7.3

This may also be related to #12647

@adamjstewart adamjstewart added bug configuration tests General test capability(ies) labels Oct 2, 2019
@adamjstewart
Copy link
Member Author

adamjstewart commented Oct 2, 2019

Confirmed that this function is responsible:
https://github.com/spack/spack/blob/develop/lib/spack/spack/test/conftest.py#L132,L158

@adamjstewart
Copy link
Member Author

Even worse, if you have an existing build_stage set in your user-level config.yaml, it gets overwritten.

@adamjstewart
Copy link
Member Author

It looks like this function was added in #12072. @tldahlgren can you take a look? The only fix I've found so far is to comment-out the entire first part of the if-statement, but that's probably there for a reason.

@tldahlgren
Copy link
Contributor

tldahlgren commented Oct 2, 2019 via email

@scheibelp
Copy link
Member

Closing this as a duplicate of #12798. Feel free to reopen if that does not seem to be the case to you. I am updating the title of that issue to make it clearer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug configuration tests General test capability(ies)
Projects
No open projects
3 participants