summaryrefslogtreecommitdiff
path: root/yarns/architecture.yarn
diff options
context:
space:
mode:
authorRichard Maw <richard.maw@codethink.co.uk>2013-11-25 11:50:03 +0000
committerRichard Maw <richard.maw@codethink.co.uk>2013-11-29 16:11:32 +0000
commit21d7299e927696c2536e2170f77eef9b25f80172 (patch)
tree5e6333d08174bca4b98d62aefede4caaf5d63356 /yarns/architecture.yarn
parent5ecc3651d4cab13d244e394ab63e45d79294f62d (diff)
downloadmorph-21d7299e927696c2536e2170f77eef9b25f80172.tar.gz
yarns: un-parameterise architecture in system morphologies
It doesn't make sense to be able to specify an architecture from the IMPLEMENTS name, since you either need your architecture for something to build, or testarch for something that consistently doesn't build.
Diffstat (limited to 'yarns/architecture.yarn')
-rw-r--r--yarns/architecture.yarn2
1 files changed, 1 insertions, 1 deletions
diff --git a/yarns/architecture.yarn b/yarns/architecture.yarn
index 038492cd..521575a3 100644
--- a/yarns/architecture.yarn
+++ b/yarns/architecture.yarn
@@ -4,7 +4,7 @@ Morph Cross-Building Tests
SCENARIO building a system for a different architecture
GIVEN a workspace
AND a git server
- AND a system called base-system-testarch for architecture testarch in the git server
+ AND a system called base-system-testarch for the test architecture in the git server
WHEN the user checks out the system branch called master
AND the user attempts to build the system base-system-testarch in branch master
THEN morph failed