| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Be consistent about placement of test description, blank lines, etc.
|
|
|
|
| |
This requires running git-daemon manually in the tests.
|
|
|
|
|
|
| |
This reworks the blackbox tests to work with the bare repository caches. For
the most part it's slight changes to error messages and tweaks to ignore the
repository caches during file listing.
|
|
|
|
|
|
| |
Move this into a script which can be sourced by the 'setup' scripts
and the actual tests (this is needed as the environment in 'setup' is
not passed on to the tests).
|
|\
| |
| |
| | |
git://roadtrain.codethink.co.uk/baserock/morph
|
| |
| |
| |
| |
| | |
We should now be fully consistent regarding the form of triplets (ie.
the last component is always a morphology name rather than a filename)
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
|
|
|
| |
This adds a way to cause the processed configuration to be dumped out. We do
this in the overridden process_args method so that the configuration dumped has
had all the processing done on it which is necessary.
The test then uses this functionality to ensure that the repo-alias setting has
been correctly updated with the Trove-hosted prefixes.
|
|
|
|
|
|
|
|
|
|
| |
This is needed because we are replacing the current build command
by a new one that builds from a local system branch. Since that will
be the more common scenario, we want the new implementaiton to go by
the name 'morph build'.
This commit therefore renames 'morph build' and updates all the
tests to use 'morph build-morphology' instead.
|
| |
|
|
|
|
|
|
|
|
| |
This removes the requirement that all strata must be in the same
repo as the system morphology.
Both the system "strata" field and the stratum "build-depends" field
are affected.
|
|
|
|
| |
Rename "sources" field of stratum morphologies to "chunks".
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Process substitution is a little funky and bash variable substitution's
suffix stripping is hard to remember.
Instead write the list of sources to a temporary file and redirect that
to the while loop.
|
|
|
|
|
| |
The test expects it to just exit non-zero, so prevent output
changing that.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This will make a build fail if the morphology is missing explicit
build dependencies.
Also fix test causes so that ./check passes.
|
|
|
|
|
|
|
|
| |
Also, some bug fixes.
Also, when handling a BaseException, log the exception (with traceback)
that we're handling, in case there is an error while handling it, because
the second error will otherwise mask the first one.
|
|
|
|
|
| |
They fail on squeeze and should be tested either at system assembly
or in a unit test.
|
|
|
|
|
| |
This adds the ability to do this to the script, and fixes use of
the script to add the new parameter.
|
|
|
|
|
| |
These tests were failing because the stratum metadata was added to
the cache.
|
|
|
|
|
|
|
| |
This required functionality to create a tarball from a json file.
This should probably be rewritten as a morph plugin and refactor it
to consolidate the creation logic, so e.g. the stratum metadata is
kept.
|
|
|
|
|
|
|
| |
This adds a new script called list-overlaps, which when given a json
dump of the overlap can be used to query what is overlapping
The tests use this script to check that the overlaps are detected
|
|
|
|
|
| |
the exact format of the logging may change, so just check that the
artifact, the chunks and the files are mentioned
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Rather than parse the output of tar -tvf, extract the tarballs and
test the files.
This should hopefully be more stable than the output of tar
|
| |
| |
| |
| |
| |
| | |
output is properly sorted, and redundant data is removed
also the stratum in stratum-overlap-*.setup are unpacked in a different
order, so there is a symlink to stomp first
|
| | |
|
| |
| |
| |
| |
| | |
The test is purely that the warnings are logged, whether it handles
overlapping correctly is another issue
|
| |
| |
| |
| |
| | |
It may be better to print it to the console, but that requires
getting self.msg set
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Make sure that this directory is actually created before trying
to save artifacts to it. Also adjust all tests to use this new
directory for looking up artifacts.
|
| |
|
|
|
|
|
|
|
|
| |
At the moment this is done by creating a reverse topological sorting
starting with the artifacts that depend on nothing else. Artifacts
are then added to build groups as late as possible.
Fix show-dependencies test output for the new build order generation.
|
|
|
|
|
|
| |
It is possible that a bunch of stuff will be put in the tarball.
What matters is if the binary is in the tarball, so only print
that line of output
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We should be failing the test, since the code is broken.
The expected output should not include the error; when
the error goes away the test will pass.
|
|\ |
|