baserock/baserock/morph.git - Morph -- Baserock build tool

	Commit message (Collapse)	Author	Age	Files	Lines
*	Fix directory names for chunks to use slashes, not colons	Lars Wirzenius	2014-03-06	1	-5/+5
\| \| \| \| \|	These are _directory_ names, not chunk repo URLs, so a slash is correct now.
*	Merge remote-tracking branch ↵	Richard Maw	2014-02-17	1	-0/+22
\|\ \| \| \| \| \| \| \| \| \| \| \| \| \| \|	'origin/baserock/richardmaw/10312/ensure-not-add-repo-ref' This includes a typo fix of Unpertify -> Unpetrify Reviewed-by: Lars Wirzenius
\| *	yarns: Ensure machine altered morphologies don't include repo/ref	Richard Maw	2014-02-14	1	-0/+22
\|/
*	Warn and default to null if repo or ref are given	Richard Maw	2014-02-13	1	-12/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This now means that the system morphology is not altered when chunks are altered, so some tests had to change. Since this uses the python warnings API, these warnings can be ignored by running python -W ignore:"stratum morphology" \ -W ignore:"system morphology" \ "$(which morph)" ...` or turned into errors with python -W error:"stratum morphology" \ -W error:"system morphology" \ "$(which morph)" ...`
*	Remove tests for working with null refs	Richard Maw	2014-02-13	1	-63/+0
\| \| \| \| \|	Refs should be completely omitted, and this is now the standard behaviour, so there's little value in testing the behaviour separately.
*	Standardizes language and refactors some implementation steps	Daniel Firth	2013-11-05	1	-60/+60
\|
*	Added scenario test to prevent morph edit from being used without a system ↵	Daniel Firth	2013-11-01	1	-0/+10
\| \| \| \|	argument
*	Some tests refactorized for better understanding.	Pedro Alvarez	2013-10-31	1	-11/+11
\|
*	Add yarn test for autotools version guesser	Richard Ipsum	2013-10-08	1	-0/+8
\|
*	Make branch commands work with null refs	Richard Maw	2013-09-26	1	-0/+62
\|
*	Rename test to fix name clash	Richard Maw	2013-09-23	1	-1/+1
\|
*	Remove duplicate yarn	Richard Maw	2013-09-23	1	-9/+0
\|
*	Revert "Merge branch 'liw/restore-old-cmds'"	Richard Maw	2013-08-29	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This reverts commit 2dc382a2a9ae977b1158002cd2631ec5593959c1, reversing changes made to 89a019af088ff62459699a6efdadf8ac8fe35dd9. We decided to restore the old commands for the release, as we weren't confident the new implementations were correct yet. To gain that confidence we need to use them, so the old versions are no longer available, and the new edit code is used when the edit subcommand is invoked. Doing so also requires the test suite to use the edit command instead of new-edit.
*	Fix name of yarn scenario	Lars Wirzenius	2013-08-19	1	-1/+1
\| \| \| \| \| \| \| \| \|	This exposed a bug in yarn: it does not notice when two scenarios have the same name, and uses the same DATADIR directory for two scenarios. Oops. Fixed this by changing one of the scenario names in the Morph test suite. Yarn itself will be fixed separately.
*	yarns: add a scenario for checking out a chunk	Richard Maw	2013-08-08	1	-0/+18
\|
*	Add scenario (yarn) tests for most of branching and merging	Lars Wirzenius	2013-07-30	1	-0/+283
	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.