summaryrefslogtreecommitdiff
path: root/scripts/test-shell.c
Commit message (Collapse)AuthorAgeFilesLines
* Convert last cmdtests to yarnsTiago Gomes2015-12-021-1/+11
| | | | | | | The conversion was made so that the build command was used instead of the build-morphology command. Change-Id: I67c43d765ed603ecdd806bc649815526243b7b87
* Use the shell X-ray modeTiago Gomes2015-08-121-3/+4
| | | | | | | | | | | Instead of logging every command for ourselves, use the shell X-ray mode. As side effect, each command argument will now be printed out in its evaluated form, which aids debugging. Also, improve the visual separation between the different build steps, and display those steps with finer granularity. Change-Id: I16ebe9ba4ac46fef82e37d0b3e05f42d14249de8
* Fix Yarn tests to not include .git directory in built artifactsSam Thursfield2015-08-111-1/+6
| | | | | | | | | When I spotted that artifacts contained a .git directory I was worried that it might indicate a Morph bug. It turned out to be due to the way the 'test shell' used in the Yarn tests works. This change should save anyone else from similar confusion. Change-Id: I97b57eff7aa947506d4062a76e9803398e46c2b6
* scripts/test-shell.c: Add missing license headerJavier Jardón2015-03-171-0/+15
| | | | Change-Id: I46ad9c15064de752e839611d2ce3ee016ec7cc46
* test-shell: Report write failuresRichard Maw2014-11-121-2/+9
|
* Merge branch 'baserock/richardmaw/test-system-integrations'Richard Maw2014-10-241-31/+60
|\ | | | | | | | | | | Reviewed-by: Sam Thursfield Reviewed-by: Pedro Alvarez Reviewed-by: Daniel Silverstone
| * test-shell: Allow to be used in system-integrationsRichard Maw2014-10-241-39/+49
| | | | | | | | | | | | It now works when passed a file, rather than a command to run, and ignores comments and set commands, so the generated preamble is accepted.
| * test-shell: add create file commandRichard Maw2014-10-241-0/+20
|/
* Add echo to the test shellRichard Maw2014-10-081-0/+6
|
* Add test shell for use in staging area testsRichard Maw2014-10-011-0/+144
This is intended to be statically linked, so it can be run in the staging area, without having to build a libc. You shouldn't generally statically link GLibc, because it dynamically links things like NSS modules or locale data, but we only need some very simple stuff, so we can get away with that. There's also potential licensing issues, as GLibc is LGPLv2, so distribution requires providing the ability to re-link against another library, but its use in the test-suite shouldn't count as distribution. There's a couple of commands, the only two needed by the yarn test suite are "copy files" which is like `cp -r . "$DESTDIR"`, and "false", which is for commands to deliberately fail.