| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
The conversion was made so that the build command was used instead of
the build-morphology command.
Change-Id: I67c43d765ed603ecdd806bc649815526243b7b87
|
|
|
|
| |
Change-Id: Ibf1edd1b0e58c600167eb2f1394e464d1f0041c1
|
|
|
|
|
|
|
|
|
|
|
| |
Its going to be more likely that a baserock user is more interesed
in the build log than actually the debug output from morph.
And also the intuitive option would be to use -v for this.
--verbose/-v: show build output
--debug/-d: show morph debug output
Change-Id: I1fb99034dc8680a5f168f6306724663aea33ebc5
|
|
|
|
| |
Change-Id: I992dc0c1d40f563ade56a833162d409b02be90a0
|
| |
|
|
|
|
| |
Deploying after distbuild currently broken
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Yarn in Baserock now sets SRCDIR, so it is not necessary for us to set
it anymore.
|
|
|
|
|
|
|
|
| |
As we are running Morph from the source dir we need to set PYTHONPATH so
that extensions are correctly loaded.
Also, the version of Yarn in Baserock sets 'SRCDIR' so we do not need to
set a default any more.
|
|
|
|
|
| |
Refs should be completely omitted, and this is now the standard
behaviour, so there's little value in testing the behaviour separately.
|
|
|
|
|
| |
Set -e meant that the stderr could never be re-output, catching the
return code and re-outputting was not sufficient.
|
|
|
|
|
| |
Saving the result is useful for the tests, but diagnostics of failures
are quicker if the result is printed to the terminal as well.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported-by: Tiago Gomes
|
|
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.
|