| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
./check with no arguments is as-before, similarly ./check --full,
but now you may also specify individual tests to run.
So just the style check is `./check --style`. Everything but style
is `./check --full --no-style`.
I found this convenient when working on the test suite.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
We carefully _add_ to PYTHONPATH in ./check, if it was set by the user.
However, yarn cleans the environment when it runs tests, so we tell it
to add PYTHONPATH from ./check to the test environment.
Additionally, we change yarns/morph.shell-lib so it doesn't override
PYTHONPATH, but adds to it.
All of this is necessary to get morph, when run by yarn steps, to have
the right PYTHONPATH, which can be (and currently is) to allow the user
to specify un-installed versions of dependencies, such as cliapp.
|
| |
|
|
|
|
|
|
|
|
| |
It turns out that only the check-copyright-year script was exiting
properly, but it was not doing the deferred exit that other tests were
doing.
Other tests would set errors=1, then later check the result and exit
if it's non-zero, however the errors variable was set in a sub-shell,
since it was on the right-hand side of a pipe.
|
| | |
|
| |
|
|
|
| |
morph merge works badly enough that we don't really support it right now,
and I don't have time to tweak "morph edit" to make the tests pass.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These scenarios test the basics of most of the subcommands the
branch and merge plugin provides. They don't purport to be complete,
but give some indication that things work, and form a basis upon
which further things can be built. Yarn also isn't included in a
Baserock release yet, so we need to keep the cmdtests until Baserock
10 has been released.
The existing cmdtest tests are not modified by this: they are left
intact, until they can analysed in detail for things to be added to
the scenarios. After that, the cmdtest tests will start to go away.
Merging is not covered by these tests: it is not clear how merge should
work, and the current code is known to do the wrong thing in many cases.
Scenarios for merge will be added later.
Building is also not covered. Testing builds well needs some additional,
careful thinking, and that isn't ready for this patch series. It will
be added later.
|
| |\
| |
| |
| |
| |
| |
| | |
Reviewed-by: Richard Maw
I, Lars, note that we have an old version of CoverageTestRunner
in Baserock. The new version hides the spurious logging messages.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
It is almost never a good idea to catch all exceptions, and then do
nothing about them. This patch logs all caught exceptions so that the
user has some possibilty to debug what is happening.
Also, make ./check check for bare excepts and fail the test suite if it
finds anything.
|
| |/ |
|
| |
|
|
|
| |
To remove need of configuring git to check new system .gitconfig file
added to morph/scripts and check set to use this file.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Running all the checks takes over 20 minutes for me. This makes it
likely that ./check doesn't get run very often. Dropping the slowest
tests by default makes ./check more usefull. Add the --full option
to enable the full test suite again.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
git://git.baserock.org/baserock/baserock/morph
This includes a merge fixup in ./check, so that it
does not complain about build-system-autotools' test's tabs.
|
| |/ |
|
| |
|
|
|
|
| |
This is necessary so that the write extension run by cmdtest finds
the morphlib of the source tree we're running ./check in, rather
than the system installed one.
|
| | |
|
| |\
| |
| |
| | |
Merge commit fixes up a copyright year and removes EOL whitespace
|
| |/
|
|
|
| |
This can go away when we have made a release with yaml in it, and its
staging filler.
|
| |
|
|
| |
Merge is by far the most complex of the branching and merging commands.
|
| |
|
|
|
| |
We don't want to have any *.py files as executable scripts, so hashbangs
never make sense.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Pass 1 is done through morph now, so it doesn't need this any more
|
| | |
|
| |\ |
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
It is possible to run the script as root if needed
We don't have fakeroot in baserock devel yet
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Previously, we required the caller to add /usr/sbin (or
other possible locations for ldconfig) to PATH before
invoking morph. This was inconvenient, so now morph
adds the FHS-compliant possible locations itself,
to save the caller a bit of pain.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Instead, assume the whole build will be run, by the user, under
fakeroot or sudo (the latter for system image builds). This allows
us to run all non-system-image-build tests without root access
at all.
We now always create the cache directory, if missing, even if
we're running as root.
We no longer run ldconfig if ld.so.conf is missing. It is missing
during our tests, but is (now) created by fhs-dirs for real builds.
|
| |
|
|
|
|
|
|
| |
bins now takes an Execute, so the test needed to be changed to also pass one
Execute had to be changed to ignore a statement from coverage
Also fixed Execute.runv not outputting its error. I think it is not logged
this way, but it does get output like it was before.
Also check no longer runs cmdtest from the home directory.
|
| |
|
