summaryrefslogtreecommitdiff
path: root/tests.build/stratum-overlap-warns.setup
Commit message (Collapse)AuthorAgeFilesLines
* cmdtests: Use YAML not JSON to represent morphologiesAdam Coldrick2014-08-141-70/+50
|
* Use a relative symlink in test chunkLars Wirzenius2013-03-201-1/+1
| | | | | | The absolute one made the test suite fail in my VM, and is not the right thing to do anyway. $DESTDIR/usr/bin and $DESTDIR/bin are meant to be the same directory here, not $DESTDIR/usr/bin and /bin.
* Add 'build-mode' field for chunks in a stratumSam Thursfield2013-03-131-4/+8
| | | | | | | | | | | | | | | | | | | | | | | | | Allowed values: staging: build with a staging chroot (default) test: build with the host's tools bootstrap: build with the host's tools, and do not include this chunk in the final stratum artifact In the past, 'normal mode' has been used to describe building a chunk with the host's tools. We don't want that mode to ever be used, because it is a huge hole in reproducability, but we need to keep it around to avoid making Morph's cmdtest suite depend on Baserock. Hopefully naming it 'test' should discourage potential abusers. It is unfortunate that the build tests now take a separate code path compared to real-world usage of Morph. However, this is necessary to avoid a circular dependency between Morph's test suite and the build-essential stratum in Baserock. We do whole-build testing of Baserock, too, so the 'staging' code path is still tested outside of Morph. However, testing a staging area requires populating it with at minimum a working shell, and this is a bit too complex to go in Morph's test suite.
* tests.build: Don't build individual chunks or strataSam Thursfield2013-02-201-4/+5
| | | | | We can't rely on this being possible any more. It was mostly only used for testing in any case.
* Separate out build tests from general Morph testsSam Thursfield2013-02-201-0/+117