diff options
| author | Kartik K. Agaram <vc@akkartik.com> | 2015-05-02 11:49:11 -0700 |
|---|---|---|
| committer | Kartik K. Agaram <vc@akkartik.com> | 2015-05-02 11:49:11 -0700 |
| commit | d9a7e6abc7dba8e84a5e80a6593145f1aaeb6f6c (patch) | |
| tree | af2345c92315d623124d5612931914c54042a42b /cpp/.traces/channel-write-full | |
| parent | 981cc9e8e9fd2f76b4dced8b88f3dac41c87d761 (diff) | |
| download | mu-d9a7e6abc7dba8e84a5e80a6593145f1aaeb6f6c.tar.gz | |
1239 - scheduler bugfix
In the process, some extra unit tests as well. The final scenario is newly fixed.
Between the earlier support for '%' escaping C code inside scenarios,
and the previous commit, we now actually have the ability to setup
the Routines data structure just so to simulate different situations.
One unanticipated but happy consequence of ignoring run(""): I can interleave
'+' lines with '-' lines to avoid making any ordering assertions between '+'
lines. So the '+' lines here are checked in order:
+layer1: a
+layer3: c
But here they will pass even if present out of order:
+layer1: a
-layer2: b
+layer3: c
This might be too confusing. In general, relying on run("") is just a temporary
hack. It might well have even worse counter-intuitive effects.
At least I'm not seeing any string-escaping issues so far.
Diffstat (limited to 'cpp/.traces/channel-write-full')
0 files changed, 0 insertions, 0 deletions