summaryrefslogtreecommitdiff
path: root/yarns
Commit message (Collapse)AuthorAgeFilesLines
...
* validation: Require there be non-bootstrap chunks in systemsRichard Maw2013-11-292-2/+46
| | | | | | | | | | | | | | Bootstrap chunks don't make it into the final system, so there needs to be an extra check for empty systems after the sources have been collected. This was complicated slightly by the fact that if you try to build a chunk directly you will have no strata in your sources, hence no non-bootstrap chunks, but validation for having been told to build a chunk is best handled later. This amends the old yarns that depended on building a bootstrap chunk and adds a new one that explicitly builds a system with bootstrap chunks.
* morphloader: Require systems have at least one stratumRichard Maw2013-11-292-14/+15
| | | | | | | | | | It doesn't currently make sense to build a system which contains no strata. We may later add other fields, such as initramfs to contribute to the system's artifact, but until then it's another bug to trip over. This uses collections.Sequence for checking the type of the systems entry in the morphology as a style choice, though it allows more flexibility if the types in the parsed morphology change.
* yarns: Correctly allow run_morph to output stderr on failureRichard Maw2013-11-291-7/+10
| | | | | Set -e meant that the stderr could never be re-output, catching the return code and re-outputting was not sufficient.
* yarns: Also output error messages to terminalRichard Maw2013-11-221-0/+3
| | | | | Saving the result is useful for the tests, but diagnostics of failures are quicker if the result is printed to the terminal as well.
* Standardizes language and refactors some implementation stepsDaniel Firth2013-11-056-136/+124
|
* Added scenario test to prevent morph edit from being used without a system ↵Daniel Firth2013-11-012-1/+15
| | | | argument
* Added scenario test for preventing building uncommitted systemsDaniel Firth2013-11-012-0/+21
|
* Add regression test, morph branch doesn't remove existing branch dirPedro Alvarez2013-10-311-0/+20
|
* Some tests refactorized for better understanding.Pedro Alvarez2013-10-312-12/+16
|
* Modify morph test suite to use the new cmdtestPedro Alvarez2013-10-302-0/+20
|
* Deploying a non-cluster morphology now displays an error messageDaniel Firth2013-10-302-1/+18
|
* Added scenario test for preventing cross-buildingDaniel Firth2013-10-303-1/+39
|
* Adding testPedro Alvarez2013-10-282-1/+36
|
* Add fstab.configureLars Wirzenius2013-10-242-0/+139
| | | | | This will allow the user to append text to /etc/fstab during a deployment, without having to write custom configuration extensions.
* Remove TAB charactersLars Wirzenius2013-10-101-2/+2
|
* Merge remote-tracking branch 'origin/baserock/richardipsum'Lars Wirzenius2013-10-082-0/+45
|\ | | | | | | | | Reviewed-by: Lars Wirzenius Reviewed-by: Richard Maw
| * Add yarn test for autotools version guesserRichard Ipsum2013-10-082-0/+43
|/
* Move helper script to scripts for use in cmdtestsRichard Maw2013-09-261-17/+1
|
* Make branch commands work with null refsRichard Maw2013-09-263-0/+95
|
* Rename test to fix name clashRichard Maw2013-09-231-1/+1
|
* Remove duplicate yarnRichard Maw2013-09-231-9/+0
|
* Revert "Merge branch 'liw/restore-old-cmds'"Richard Maw2013-08-292-3/+3
| | | | | | | | | | | | | | | 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.
* Use new edit instead of old one in testsLars Wirzenius2013-08-191-2/+2
| | | | | | | The test suite got adapted so it requires the new edit instead of the old one. So use the new edit instead of the old one in the test. This is a kluge, and needs to be reverted after the BR10 release.
* Fix name of yarn scenarioLars Wirzenius2013-08-191-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.
* Use print-architecture instead of arch -m in testsLars Wirzenius2013-08-151-1/+2
|
* Add "morph print-architecture" subcommandLars Wirzenius2013-08-151-0/+42
|
* Fix test morphology to be a valid oneLars Wirzenius2013-08-141-0/+3
| | | | | | The MorphologyLoader validates morphologies stricter than old code, so adjust the test morphology accordingly: add arch to a system morphology, and build-mode and build-depends to a stratum one.
* yarns: add a scenario for checking out a chunkRichard Maw2013-08-082-0/+30
|
* yarns: allow attempt checkout to sometimes workRichard Maw2013-08-081-1/+1
| | | | | | | | | Checkout needs the branch repository and ref. It was previously only getting the ref. This was not noticed, since the implementation was only used in cases where it was expected to fail, and the nature of the error was not being checked.
* Refactor code for clarityLars Wirzenius2013-07-311-4/+4
| | | | Reported-by: Tiago Gomes
* Add scenario (yarn) tests for most of branching and mergingLars Wirzenius2013-07-303-0/+792
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.
View Lorry Controller Status