summaryrefslogtreecommitdiff
path: root/tests.build/bootstrap-mode.stdout
Commit message (Collapse)AuthorAgeFilesLines
* cache-key: Fix obscure cache key collisionRichard Maw2014-01-221-2/+2
| | | | | | | | | | | | | | | | | | | | If two systems with the same name (e.g. different repo/ref) depend on the same strata, then it will collide with systems which depend on different artifacts from that stratum, but the same number of artifacts. For example, if you checkout an existing branch and change the artifacts used by one of its strata, then your local changes won't be built. This is because the 'kids' field lists artifacts it depends on by their cache-key, which is now no longer sufficient to uniquely identify artifacts. The same number of artifacts issue is from it listing cache keys multiple times. The fix for this is to include the artifact name, so the 'kids' field is now a list of dicts, with artifact name and cache key. This is a dict rather than a tuple so that the generated /baserock metadata is more readable.
* cmdtests: Take into account new constructed artifactsRichard Maw2014-01-161-6/+5
|
* Don't install bootstrapped chunks when building artifacts in other strataSam Thursfield2013-03-131-2/+7
| | | | | | | | | | | When building a stratum artifact it's easy to only include chunks that were built in 'staging' mode. Constructing the staging area doesn't use that code path, though, so we need an extra hack to filter out those artifacts while building. It may be neater to express stratum build-depends as actual dependencies on the stratum artifact, rather than each of its constituent chunks as we do now.
* Don't include bootstrap chunks in output strataSam Thursfield2013-03-131-0/+10
This is necessary so that the build-essential stratum doesn't end up containing three different compilers.