| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
We can't rely on this being possible any more. It was mostly only used
for testing in any case.
|
| |
|
|
| |
Be consistent about placement of test description, blank lines, etc.
|
| |
|
|
|
|
|
|
|
| |
This gives us consistency with morphologies, where the triplets are
repo|ref|morphology, not repo|ref|filename
Anyone who runs 'morph build baserock:morphs master system.morph' will
now see an error ending with 'was looking for system.morph.morph', which
should make it clear where they have gone wrong.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Except in the missing-ref script, since that one breaks with -e.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This avoids accidentally having tests that depend on each other. It
would be bad to have tests/bar.script do something and then
tests/foo.script only work because of that something: if tests/bar.script
later changes, then the later test starts breaking. Keeping tests
independent is good practice. We don't seem to have had such
dependencies yet, so this is a pre-emptive defensive move.
Also, this means we can use simpler names in $DATADIR, instead of
embedding the test name in everything. This further simplifies the
act of creating new tests.
|
| | |
|
|
|
The "show-dependencies" command takes a series of build tuples and dumps
the resulting dependency graph (including strata and chunks at the
moment) to the standard output. It also dumps the resulting build order
which is a list of groups. These groups indicate which chunks and strata
can be built in parallel and are not dependent on each other.
|
