spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.

Age	Commit message (Collapse)	Author	Files	Lines
2021-02-16	Add RHEL8 Universal Base Image with platform-python to CI unit tests (#21655)	Chuck Atkins	1	-0/+27

2020-11-18	spack test (#15702)	Greg Becker	1	-1/+1
	Users can add test() methods to their packages to run smoke tests on installations with the new `spack test` command (the old `spack test` is now `spack unit-test`). spack test is environment-aware, so you can `spack install` an environment and then run `spack test run` to run smoke tests on all of its packages. Historical test logs can be perused with `spack test results`. Generic smoke tests for MPI implementations, C, C++, and Fortran compilers as well as specific smoke tests for 18 packages. Inside the test method, individual tests can be run separately (and continue to run best-effort after a test failure) using the `run_test` method. The `run_test` method encapsulates finding test executables, running and checking return codes, checking output, and error handling. This handles the following trickier aspects of testing with direct support in Spack's package API: - [x] Caching source or intermediate build files at build time for use at test time. - [x] Test dependencies, - [x] packages that require a compiler for testing (such as library only packages). See the packaging guide for more details on using Spack testing support. Included is support for package.py files for virtual packages. This does not change the Spack interface, but is a major change in internals. Co-authored-by: Tamara Dahlgren <dahlgren1@llnl.gov> Co-authored-by: wspear <wjspear@gmail.com> Co-authored-by: Adam J. Stewart <ajstewart426@gmail.com>
2020-11-17	Github actions: add CI for ASP based solver	Massimiliano Culpo	1	-0/+21

2020-10-23	csh: don't require SPACK_ROOT for sourcing setup-env.csh (#18225)	Todd Gamblin	1	-4/+9
	Don't require SPACK_ROOT for sourcing setup-env.csh and make output more consistent
2020-10-11	Add testing for Python 3.9 (#19261)	Adam J. Stewart	1	-2/+2

2020-07-31	Move Python 2.6 unit tests to Github Actions (#17279)	Massimiliano Culpo	1	-2/+15
	* Run Python2.6 unit tests on Github Actions * Skip url tests on Python 2.6 to reduce waiting times * Skip foreground background tests on Python 2.6 to reduce waiting times * Removed references to Travis in the documentation * Deleted install_patchelf.sh (can be installed from repo on CentOS 6)
2020-07-29	Use "fetch-depth: 0" to retrieve all history from remote	Massimiliano Culpo	1	-6/+6

2020-07-29	Simplified YAML files for Github Actions workflows	Massimiliano Culpo	1	-6/+3
	Updated actions where needed
2020-07-29	Group tests with similar duration together	Massimiliano Culpo	1	-38/+0
	Style and documentation tests take just a few minutes to run. Since in Github actions one can't restart a single job but needs to restart an entire workflow, here we group tests with similar duration together.
2020-07-01	Moved flake8, shell and documentation tests to Github Action (#17328)	Massimiliano Culpo	1	-0/+80
	* Move flake8 tests on Github Actions * Move shell test to Github Actions * Moved documentation build to Github Action * Don't run coverage on Python 2.6 Since we get connection errors consistently on Travis when trying to upload coverage results for Python 2.6, avoid computing coverage entirely to speed-up tests.
2020-06-30	run github workflows on release branches (#17317)	Greg Becker	1	-0/+1

2020-06-23	Added unit tests to Github Actions (#16610)	Massimiliano Culpo	1	-0/+61
	* Added unit tests to Github Actions * Set user e-mail and name for git tests to succeed * Simplify setup.sh logic * Replicate Travis script on Github Actions * Update flags since '.' is not allowed * Added badge, simplified workflow * Remove pinning of coverage * Remove unit tests run on Github Actions from Travis