Most expected OS failures or skipped tests are about the target platform on which the test binary is being run, not the host platform launching the tests. This changes expectedFailureOS and skipIfPlatform to check against the remote platform when running remote tests.
Details
- Reviewers
vharron clayborg tberghammer - Commits
- rGefa49c2665b0: Change expectedFailureOS and skipIfPlatform checks to be based on target…
rLLDB233311: Change expectedFailureOS and skipIfPlatform checks to be based on target…
rL233311: Change expectedFailureOS and skipIfPlatform checks to be based on target…
Diff Detail
- Repository
- rL LLVM
Event Timeline
Please check for android also as it use "platform-android" (not platform-linux). I also suggest to use the TargetTriple instead of the given platform to decide the target platform.
Now that it uses Triple, android isn't in the list of OS's for Triple.cc, only an environment, does it return "linux" as well?
Android using <arch>-unknown-linux-android as the target triple so checking for linux will be fine.
test/dotest.py | ||
---|---|---|
1347 | You can get the target triple both on local and remote targets with "triple = lldb.DBG.GetSelectedPlatform().GetTriple()" (after running lldb.DBG.SetSelectedPlatform on remote platforms). In longer term I would like to get rid of most of the usage of sys.platform (leave it only where we want to check the host OS) from the test system but it is out of scope for this CL. | |
1361 | Please don't use sys.platfrom here | |
test/lldbtest.py | ||
588–589 | You can use lldb.DBG.GetSelectedPlatform().GetTriple() here also (both for local and remote) |
- Use lldb.DBG.GetSelectedPlatform().GetTriple() to get target platform triple whether running local or remote tests.
- Change skipIfPlatform checks to also check remote platform.
- Consider both "macosx" and "darwin" as MacOSX - see Triple::isMacOSX for equivalent check.
You can get the target triple both on local and remote targets with "triple = lldb.DBG.GetSelectedPlatform().GetTriple()" (after running lldb.DBG.SetSelectedPlatform on remote platforms).
I suggest to use it so we can use the same OS detection on local and remote debugging.
In longer term I would like to get rid of most of the usage of sys.platform (leave it only where we want to check the host OS) from the test system but it is out of scope for this CL.