[mediacard/*-*-after-suspend] Tests are not running after suspend due to something with insert test

Same thing occurs on the Lenovo E320 (201106-8229) which has a completely different card reader.

After looking deeper into this, I still don't know just what's going on here, but during hte mediacard/*-insert-after-suspend test successfully runs, checkbox decides to skip the other two tests (storage-after-suspend and remove-after-suspend). It's setting their status to unitiated. Perhaps its interpreting the result from insert-after-suspend as a failure?

In any case, I've recreated this on every system tested so far.

The storage-after-suspend and remove-after-suspend tests, because they don't depend on the suspend/suspend_advanced test itself will run before it and therefore before the insert-after-suspend tests which they do depend on. It seems to be suggested that this shouldn't be allowed by Checkbox, but it seems the most plausible explanation.

Indeed there's a problem with dependencies as pointed out by Brendan.

After reproducing the problem I tried to add a dependency against `suspend/suspend_advanced` for both `mediacard/storage-after-suspend` and `mediacard/remove-after-suspend` and I was able to execute them successfully. After that, I tried to remove the dependency just for `mediacard/remove-after-suspend` and again the test case result was uninitiated as expected.

Regarding the root cause of this problem, I still need to investigate further, since I didn't see clue in the logs. Anyway, for now, a workaround to the problem is specify that dependency.

I added a complete description about the changes in the merge proposal.
https://code.launchpad.net/~javier.collado/checkbox/bug990075/+merge/104369

Regarding the testing to verify the correctness of the bug, I used the attached whitelist and also the smoke whitelist successfully in a laptop and a virtual machine.

This should definitely be high - it needs to be fixed soon

Please have a look at the branch and the merge proposal for information about the latest commit that has worked fine for me also for the client-cert whitelist.

As a summary, the whitelist is assumed to be almost correctly ordered and the only changes are that the jobs that have some dependency broken aren't executed in the same order, but as soon as possible (that is, just after their dependencies have been executed).

Also, find attached the final ordering for the client-cert whitelist that looks to be nice (let me know otherwise).

I've run the whitelist in #7 with the latest changes from trunk and I got this feedback (after setting log level to debug) regarding the whitelist ordering:

--- old whitelist
+++ new whitelist
@@ -1,14 +1,14 @@
 __mediacard__
+__networking__
+__power-management__
+__suspend__
+networking/detect
+suspend/network_before_suspend
+suspend/suspend_advanced
 mediacard/mmc-insert-after-suspend
 mediacard/mmc-storage-after-suspend
 mediacard/mmc-remove-after-suspend
-__networking__
-networking/detect
-__power-management__
 power-management/rtc
-__suspend__
-suspend/network_before_suspend
-suspend/resolution_before_suspend
 suspend/cpu_before_suspend
 suspend/memory_before_suspend
-suspend/suspend_advanced
+suspend/resolution_before_suspend

Given that now the mediacard test cases are correctly ordered, you shouldn't get any problem in running them because of bad dependency handling, so I'm setting the status as 'Fix Committed'.