| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
tests.deploy is gone since we have yarn coverage instead.
tests/setup had unnecessary setup in it, since the remaining tests
require custom setup anyway.
A bunch of tests were disabled anyway, so they're gone.
Also, there was still code in ./check to run tests.merging, which have
been gone for a while.
|
|
|
|
|
| |
This patch has been split out of the previous one so that it is easier
to review the changes. cmdtests do not pass without this change.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
This hasn't been used in a long time to my knowledge, its API completely
misses the point, and its implementation relies on old APIs that need to
change.
Until we discover we need it, and work out what it should look like, I
think the best thing to do is get rid of it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rather than repeatedly stripping and appending an optional .morph extension
morphology names, instead always use the file path of the morphology
relative to the definitions repository.
This is an inversion of the previous logic, which would strip the .morph
extension and use the "name" internally.
The exception to this rule of always using the filename, is that `morph
edit CHUNK` uses the name of the morphology as-defined in the stratum.
This is based off Adam Coldrick's inital patch, but this version will
allow the old style of providing the "name" by converting it into a path
if it does not have either a / or a . in it.
An unfortunate consequence of this change is that the show-dependencies
command's output changed, so the test needed updating.
|
|
|
|
|
| |
uname tends to only give us a valid morph architecture on x86_64,
this makes it work on other architectures.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This is already needed elsewhere for tests that perform builds,
however in future, validation will be more strict, so now these
dummy strata need to be marked as tests as well.
|
| |
|
|
|
|
|
|
|
| |
We do not currently install an /etc/hosts in Baserock, and thus the name
localhost is not guaranteed to resolve as expected. This patch changes
the tests to use 127.0.0.1 instead, since that is the IP address we want
localhost to resolve to.
|
|\
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
morphlib/app.py
Also fixed copyright year in tests/trove-id.script, which was not from
Richard's patch, but from an earlier commit, and all my own fault.
|
| | |
|
|\ \
| |/
|/|
| | |
Changed Paul's patch so that --trove-prefix still works as an alias.
|
| | |
|
|/ |
|
|
|
|
|
|
| |
That means that bootstrapping Baserock is currently not possible with
this branch of Morph, but there's no reason it cannot be bootstrapped
using an older version of Morph instead.
|
|
|
|
|
| |
We can't rely on this being possible any more. It was mostly only used
for testing in any case.
|
| |
|
| |
|
|
|
|
| |
No longer possible for this to happen.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously some code used `git show-ref`, which is wrong -- given two
refs named 'alpha/master' and 'master', `git show-ref master` will
return both, sorted alphabetically. This can lead to build failures,
etc. due to refs resolving to the wrong SHAs.
We should also use `git rev-parse --verify` to verify SHA1s, which
we previously did with `git rev-list`.
Finally, `git rev-parse --verify` is more than twice as fast as
`git show-ref`.
|
|
|
|
| |
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.
|