summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)AuthorFilesLines
2020-06-29cray compilers: fix bug with verifying cray compilers (#17303)Greg Becker1-5/+15
* fix bug with verifying cray compilers
2020-06-29remove three commands that have been deprecated since v0.13.0 (#17291)Greg Becker3-150/+0
* remove three commands that have been deprecated since v0.13.0
2020-06-29autotools: Fix config.guess detection (#17149)Michael Kuhn1-2/+4
The config.guess detection used a relative path that did not work in combination with `check_call`. Use an absolute path instead.
2020-06-29Detect FE compilers automatically on Cray (#17267)Massimiliano Culpo2-2/+85
* cray: detect frontend compilers automatically This commit permits to detect frontend compilers automatically, with the exception of cce. Co-authored-by: Gregory Becker <becker33.llnl.gov>
2020-06-29Fix indentation in containerize example (#17228)George Hartzell1-1/+1
[george.hartzell@172-16-193-97 spack-explore-docker]$ spack containerize Running `spack containerize` with the example `spack.yaml` file fails with an error that ends like so: ``` [...] File "/local_scratch/hartzell/tmp/spack-explore-docker/lib/spack/external/ruamel/yaml/scanner.py", line 165, in need_more_tokens self.stale_possible_simple_keys() File "/local_scratch/hartzell/tmp/spack-explore-docker/lib/spack/external/ruamel/yaml/scanner.py", line 309, in stale_possible_simple_keys "could not find expected ':'", self.get_mark()) ruamel.yaml.scanner.ScannerError: while scanning a simple key in "/local_scratch/hartzell/tmp/spack-explore-docker/spack.yaml", line 26, column 1 could not find expected ':' in "/local_scratch/hartzell/tmp/spack-explore-docker/spack.yaml", line 28, column 5 ``` Indenting the block string fixes the problem for me. CentOS 7, ``` $ spack --version 0.14.2-1529-ec58f28c2 ```
2020-06-29Restore compilers.yaml default directory (#17283)Greg Becker1-2/+2
2020-06-27Add support for macOS Big Sur (#17236)Adam J. Stewart1-0/+1
* Add support for macOS Big Sur * Big Sur is actually macOS 11.0
2020-06-26env: no automatic activation (#17258)Greg Becker4-19/+10
* env: no automatic activation * Ensure ci rebuild jobs activate the environment (no longer automagic) Co-authored-by: Scott Wittenburg <scott.wittenburg@kitware.com>
2020-06-26Use json for buildcache index (#15002)Scott Wittenburg12-305/+440
* Start moving toward a json buildcache index * Add spec and database index schemas * Add a schema for buildcache spec.yaml files * Provide a mode for database class to generate buildcache index * Update db and ci tests to validate object w/ new schema * Remove unused temporary upload-s3 command * Use database class to generate buildcache index * Do not generate index with each buildcache creation * Make buildcache index mode into a couple of constructor args to Database class * Use keyword args for _createtarball * Parse new json index when we get specs from buildcache Now that only one index file per mirror needs to be fetched in order to have all the concrete specs for binaries available on the mirror, we can just fetch and refresh the cached specs every time instead of needing to use the '-f' flag to force re-reading.
2020-06-26build_environment: verify compiler executables exist are are accessible (#17260)Greg Becker4-20/+77
* build_environment: verify compiler executables exist and are accessible * fix existing tests * test compiler executable verification
2020-06-26fix sorting issue with ci workarounds (#17277)Omar Padron2-30/+38
2020-06-26First fix for SPACK_DEPENDENCIES problem when doing setup (#10715)cedricchevalier191-9/+2
* First fix for SPACK_DEPENDENCIES problem when doing setup * Get rid of transitive include path in setup. * Export SPACK_INCLUDE_DIRS into spconfig.py
2020-06-26spack ci generate: allow use of --output-file <file> with wo/ preceding path ↵eugeneswalker1-4/+4
(#17275)
2020-06-26add environment-awareness to `buildcache create` (#16580)Jeffrey Salmond2-2/+57
* add buildcache create test * add functionality and test to create buildcache from environment * use env.concretized_user_specs rather than env.roots to get concretized specs, as suggested in review from becker33
2020-06-26Allow `spack remove -f` and `spack uninstall` to work on matrices (#17222)Greg Becker2-10/+55
* Allow `spack remove -f` and `spack uninstall` to work on matrices Allow Environment.remove(force=True) to remove the concrete spec from the environment even when the user spec cannot be removed because it is in a matrix.
2020-06-25Allow detection for "-classic" version of CCE (#17256)Massimiliano Culpo3-6/+21
* cce: detect modules based on the classic backend * cce: tweaked version checks for clang based options * Added unit test for cce flags
2020-06-25add workaround for gitlab ci needs limit (#17219)Omar Padron5-7/+235
* add workaround for gitlab ci needs limit * fix style/address review comments * convert filter obj to list * update command completion * remove dict comprehension * add workaround tests * fix sorting issue between disparate types * add indeces to format
2020-06-25prevent multiple version sigils in the same spec (#17246)Greg Becker3-9/+44
* prevent multiple version sigils in the same spec * fix packages with malformed versions
2020-06-25environment spec lists: improve ability to query architecture in when ↵Greg Becker3-5/+34
clauses (#17056)
2020-06-25Separate Apple Clang from LLVM Clang (#17110)Massimiliano Culpo17-256/+396
* Separate Apple Clang from LLVM Clang Apple Clang is a compiler of its own. All places referring to "-apple" suffix have been updated. * Hack to use a dash in 'apple-clang' To be able to use autodoc from Sphinx we need a valid Python name for the module that contains Apple's Clang code. * Updated packages to account for the existence of apple-clang Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com> * Added unit test for XCode related functions Co-authored-by: Gregory Becker <becker33@llnl.gov> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-06-25Fix global activation check for upstream extendees (#17231)Peter Scheibel2-0/+34
* short-circuit is_activated check when the extendee is installed upstream * add test for checking activation status of packages with an extendee installed upstream
2020-06-25spack config: new subcommands add/remove (#13920)Greg Becker12-102/+718
spack config add <value>: add nested value value to the configuration scope specified spack config remove/rm: remove specified configuration from the relevant scope
2020-06-24features: Add install failure tracking removal through `spack clean` (#15314)Tamara Dahlgren8-36/+140
* Add ability to force removal of install failure tracking data through spack clean * Add clean failures option to packaging guide
2020-06-24Unset environment variables that are most commonly used by Autotools ↵Sergey Kosukhin2-1/+13
packages. (#8623)
2020-06-23Some minor fixes to set_permissions() in file_permissions.py (#17020)Tom Payerle2-6/+35
* Some minor fixes to set_permissions() in file_permissions.py The set_permissions() routine claims to prevent users from creating world writable suid binaries. However, it seems to only be checking for/preventing group writable suid binaries. This patch modifies the routine to check for both world and group writable suid binaries, and complain appropriately. * permissions.py: Add test to check blocks world writable SUID files The original test_chmod_rejects_group_writable_suid tested that the set_permissions() function in lib/spack/spack/util/file_permissions.py would raise an exception if changed permission on a file with both SUID and SGID plus sticky bits is chmod-ed to g+rwx and o+rwx. I have modified so that more narrowly tests a file with SUID (and no SGID or sticky bit) set is chmod-ed to g+w. I have added a second test test_chmod_rejects_world_writable_suid that checks that exception is raised if an SUID file is chmod-ed to o+w * file_permissions.py: Raise exception when try to make sgid file world writable Updated set_permissions() in file_permissions.py to also raise an exception if try to make an SGID file world writable. And added corresponding unit test as well. * Remove debugging prints from permissions.py
2020-06-23tests: check rpath presence not equality (#17216)Tamara Dahlgren1-1/+2
2020-06-23Module index should not be unconditionally overwritten (#14837)Matthias Wolf4-9/+36
* Module index should not be unconditionally overwritten Uncovered after we switched our CI to generate modules for packages one-by-one rather than in bulk. This overwrote a complete module index with an index with a single entry, and broke our downstream Spack instances that needed the upstream module index.
2020-06-23Added support for --fail-fast install option to terminate on first failureTamara Dahlgren4-5/+67
2020-06-23Allow a single ctrl-c to terminate an install in progressTamara Dahlgren2-3/+31
2020-06-23fix compiler environment handling to reset environment after (#17204)Greg Becker2-19/+84
bugfix: fix compiler environment handling to reset environment after
2020-06-22Pre ci optimization (#16372)Omar Padron3-2/+392
* add initial optimization script * integrate optimization in spack ci * make optimization opt-in * fix import error * flake8 fixes * update command completion * work around vermin errors * fix sphynx errors
2020-06-22swig: fix older builds on newer platforms by updating config files (#16854)Joseph Ciurej1-61/+82
* swig: revise 'autotools' automated 'config.*' update mechanism to support 'config.sub' and adapt 'swig' accordingly
2020-06-18Fetching from urls: Error Message (#16434)Axel Huebl2-4/+10
* Fetching from urls: Error Message Fix the error message when fetching from consecutive `urls` of a package version. Each fail should show the currently failing URL, not the first url. Example multi-problem run that occured in real life: ``` ==> 5821: Installing util-macros curl: (28) Connection timed out after 10000 milliseconds curl: (16) Error in the HTTP2 framing layer curl: (22) The requested URL returned error: 403 Forbidden ==> Fetching https://www.x.org/archive/individual/util/util-macros-1.19.1.tar.bz2 ==> Failed to fetch file from URL: https://www.x.org/archive/individual/util/util-macros-1.19.1.tar.bz2 Curl failed with error 28 ==> Fetching https://mirrors.ircam.fr/pub/x.org/individual/util/util-macros-1.19.1.tar.bz2 ==> Failed to fetch file from URL: https://www.x.org/archive/individual/util/util-macros-1.19.1.tar.bz2 Curl failed with error 16 ==> Fetching http://xorg.mirrors.pair.com/individual/util/util-macros-1.19.1.tar.bz2 ==> Failed to fetch file from URL: https://www.x.org/archive/individual/util/util-macros-1.19.1.tar.bz2 URL https://www.x.org/archive/individual/util/util-macros-1.19.1.tar.bz2 was not found! ==> Fetching from https://www.x.org/archive/individual/util/util-macros-1.19.1.tar.bz2 failed. ==> Error: FetchError: All fetchers failed for spack-stage-util-macros-1.19.1-se2a2e74oyusj2r4esgcb7pr3qhh45ef ``` - `urls[0]`: HTTP2 layer error - `urls[1]`: timeout - `urls[2]`: missing file on mirror * x.org: two more mirrors x.org mirrors are a bit tricky, since many are out-of-sync or off. A good package to test with is `util-macros`, which had a "recent" release.
2020-06-18Docs: fix rst link to spack ci (#17147)Adam J. Stewart1-3/+3
2020-06-17cray module do not work without CRAY_LD_LIBRARY_PATH (#17031)Greg Becker2-5/+9
Co-authored-by: Gregory Becker <becker33.llnl.gov>
2020-06-16Doc: E4S Build Cache Link (#16986)Axel Huebl1-0/+6
Link to the E4S build cache in the according section of the docs.
2020-06-16Yaml spec parsing corner case (#17101)psakievich2-7/+28
* Catch yaml filename corner case in spec parser * improved regex and remove redundant error checking Co-authored-by: Gregory Becker <becker33@llnl.gov>
2020-06-15Skip failing test on MacOS (#17072)Massimiliano Culpo1-0/+2
* Skip failing test on MacOS * Update setup-python action and unpin coverage
2020-06-13clang: add 'version_argument', remove redundant method (#17071)Greg Becker2-20/+3
2020-06-12Buildcache: Fix bug in binary string replacement (#17075)Patrick Gartung1-1/+5
* Fix bug in binary string replacement that results in padding being added multiple times * Update comment * Update comment again
2020-06-11Renamed flags.py to basics.pyMassimiliano Culpo2-1/+2
2020-06-11Reworked tests on compilers to separate version detectionMassimiliano Culpo3-170/+183
Tests on version detection are now separate from other tests done on compiler.
2020-06-10Move to temporary directory before running dev-build test (#17028)Massimiliano Culpo1-3/+4
Without this the test would leave spurious "spack-build-*.txt" files in the current working directory.
2020-06-09lib/spack : expand spack config vars in 'include' section (#16210)Joseph Ciurej2-2/+33
* Changed the 'include' config section to use 'substitute_path_variables' to allow for Spack config variables to be used (e.g. $spack). * Fixed a bug with 'include' section path expansion and added a test case for 'include' paths with embedded config variables.
2020-06-09Testing: create mock executable fixture (#16999)Massimiliano Culpo2-9/+19
2020-06-09SpecList: fix recursion for references (#16897)Greg Becker2-29/+59
* SpecList: fix and refactor variable expansion
2020-06-08Cray: fix Blue Waters support and user-built MPIs on Cray (#16593)Adam J. Stewart2-11/+19
* Cray: fix Blue Waters support * pkg-config env vars needed on Blue Waters * cray platform: fix support for user-build MPI on cray machines * reintroduce cray environment cleaning behind cnl version guard * cray platform: fix support for user-build MPI on cray machines Co-authored-by: Gregory <becker33@llnl.gov>
2020-06-08view remove: directly check whether specs own files before removing from ↵Greg Becker2-5/+44
view (#16955) Bugfix for hardlinks and copies
2020-06-05spack dev-build: Do not mark -u builds in database (#16333)Greg Becker4-21/+61
Builds can be stopped before the final install phase due to user requests. Those builds should not be registered as installed in the database. We had code intended to handle this but: 1. It caught the wrong type of exception 2. We were catching these exceptions to suppress them at a lower level in the stack This PR allows the StopIteration to propagate through a ChildError, and catches it properly. Also added to an existing test to prevent regression.
2020-06-05commands: use a single ThreadPool for `spack versions` (#16749)Massimiliano Culpo4-251/+228
This fixes a fork bomb in `spack versions`. Recursive generation of pools to scrape URLs in `_spider` was creating large numbers of processes. Instead of recursively creating process pools, we now use a single `ThreadPool` with a concurrency limit. More on the issue: having ~10 users running at the same time spack versions on front-end nodes caused kernel lockup due to the high number of sockets opened (sys-admin reports ~210k distributed over 3 nodes). Users were internal, so they had ulimit -n set to ~70k. The forking behavior could be observed by just running: $ spack versions boost and checking the number of processes spawned. Number of processes per se was not the issue, but each one of them opens a socket which can stress `iptables`. In the original issue the kernel watchdog was reporting: Message from syslogd@login03 at May 19 12:01:30 ... kernel:Watchdog CPU:110 Hard LOCKUP Message from syslogd@login03 at May 19 12:01:31 ... kernel:watchdog: BUG: soft lockup - CPU#110 stuck for 23s! [python3:2756] Message from syslogd@login03 at May 19 12:01:31 ... kernel:watchdog: BUG: soft lockup - CPU#94 stuck for 22s! [iptables:5603]
generated by cgit v1.2.3-70-g09d2 (git 2.46.0) at 2024-11-01 12:54:50 +0000