This change adds the infrastructure to mark tests as xfail for specific
Android API levels.
Details
Diff Detail
Event Timeline
| test/lldbtest.py | ||
|---|---|---|
| 450 | Could you specifically check for adb:// scheme? It's conceivable that there could be a device with the name of localhost. | |
| 455 | I'm not sure if it's possible for getprop to return anything else, but could you try/catch ValueError just in case? | |
| 700 | int(device_api) seems unnecessary after int(stdout). | |
| 701 | Just return device_api and (device_api in api_levels)? Is it necessary to check if device_api is valid? None in list should just return false, right? | |
lgtm, with one small comment.
| test/lldbtest.py | ||
|---|---|---|
| 696 | This is missing an else clause. Also, I think it would be more readable if you inverted the logic here: if not match: return False ... | |
| test/lldbtest.py | ||
|---|---|---|
| 696 | This is the last statement in the function. It will return None if the "if ... " is not hit. | |
| test/lldbtest.py | ||
|---|---|---|
| 449 | I meant something like: parsed = urlparse.urlparse(lldb.platform_url)
scheme = parsed.scheme
hostname = parsed.hostname
if scheme == "adb":
device_id = hostname | |
| test/lldbtest.py | ||
|---|---|---|
| 696 | If that is the "python way" then ok, but the c programmer in me does not like it. :) | |
| test/lldbtest.py | ||
|---|---|---|
| 449 | Ah, this is Android specific so I am not sure that is worth it. However, I have changed it. Would an assert be more suitable? assertEqual(scheme, "adb") | |
Fix the "adb" scheme check. Chaoren explained to me offline that the
scheme could be "connect" or "adb"; When its "adb", the hostname is always
the device id. Similarly, if a device id has to be specified in
lldb.platform_url, then the "adb" scheme has to be used.
| test/lldbtest.py | ||
|---|---|---|
| 50 | Is python 3 even supported? | |
Is python 3 even supported?