Bug 1316757, part 3 - Delete IPDL unit tests that look like they only test state machine stuff. r=billm

MozReview-Commit-ID: 7Lek3YzLIft

--HG--
extra : rebase_source : 16a53cbd579554a82b84ee28f638b3517537e413
This commit is contained in:
Andrew McCreight 2016-11-23 09:10:45 -08:00
parent c5c7f69cf3
commit a3d8276ca3
6 changed files with 0 additions and 162 deletions

View File

@ -1,12 +0,0 @@
protocol multiOutStates {
child: async Msg();
// sanity check that multi-out-states are being processed correctly
state S1:
send Msg goto S2 or S3 or S4;
state S2: send Msg goto S2;
state S3: send Msg goto S3;
state S4: send Msg goto S4;
};

View File

@ -1,11 +0,0 @@
protocol multiStartState {
child: async Msg(); async __delete__();
start state S1:
send Msg goto S1; send __delete__;
start state S2:
send Msg goto S2; send __delete__;
};

View File

@ -1,27 +0,0 @@
protocol race_DiamondRule1 {
child:
async Msg1();
async Msg1_();
parent:
async Msg2();
async Msg2_();
// OK: this state machine is one of the simplest that follows the
// Diamond Rule
start state S1:
send Msg1 goto S2;
recv Msg2 goto S3;
state S2:
recv Msg2 goto S4;
recv Msg2_ goto S2;
state S3:
send Msg1 goto S4;
send Msg1_ goto S3;
state S4:
send Msg1 goto S4;
};

View File

@ -1,61 +0,0 @@
protocol race_KitchenSink {
child:
async Msg1();
async Msg1_();
parent:
async Msg2();
async Msg2_();
// concatenation of a few other state machines, should be OK
start state S1:
send Msg1 goto S2;
recv Msg2 goto S3;
state S2:
recv Msg2 goto S4;
recv Msg2_ goto S2;
state S3:
send Msg1 goto S4;
send Msg1_ goto S3;
state S4:
send Msg1 goto S4;
start state S5:
send Msg1 goto S5;
recv Msg2 goto S5;
start state S15:
send Msg1 goto S16 or S17;
recv Msg2 goto S18 or S19;
state S16:
recv Msg2 goto S20;
recv Msg2_ goto S18;
state S17:
recv Msg2 goto S20;
recv Msg2_ goto S15;
state S18:
send Msg1 goto S20;
send Msg1_ goto S15;
state S19:
send Msg1 goto S20;
send Msg1_ goto S16;
state S20:
send Msg1 goto S20;
send Msg1_ goto S20;
recv Msg2 goto S20;
recv Msg2_ goto S20;
};

View File

@ -1,35 +0,0 @@
protocol race_MultiOut {
child:
async Msg1();
async Msg1_();
parent:
async Msg2();
async Msg2_();
start state S15:
send Msg1 goto S16 or S17;
recv Msg2 goto S18 or S19;
state S16:
recv Msg2 goto S20;
recv Msg2_ goto S18;
state S17:
recv Msg2 goto S20;
recv Msg2_ goto S15;
state S18:
send Msg1 goto S20;
send Msg1_ goto S15;
state S19:
send Msg1 goto S20;
send Msg1_ goto S16;
state S20:
send Msg1 goto S20;
send Msg1_ goto S20;
recv Msg2 goto S20;
recv Msg2_ goto S20;
};

View File

@ -1,16 +0,0 @@
protocol race_Stateless {
// manages Child;
child:
async Msg1();
async Msg1_();
parent:
async Msg2();
async Msg2_();
// OK: this is trivial stateless protocol, so race-free "by definition"
start state S5:
send Msg1 goto S5;
recv Msg2 goto S5;
};