en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp#1c8366f9 [Dexter] Collate penalties of the same type into a single line for eachCurrently in Dexter, every step at which a DexExpectWatchValue/Type doesnot have the correct value is printed on a separate line. This patchreduces the size of the text output by instead printing each incorrectresult (i.e. each incorrect value seen, 'Variable optimized out', and soon) on its own line, alongside a list of the steps at which that resultwas seen. This makes for much less spam in the output when watches aremissing or wrong for many steps.Differential Revision: https://reviews.llvm.org/D120716 List of files: /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp Tue, 01 Mar 2022 13:20:51 +0000 Stephen Tozer <stephen.tozer@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp#de3f8155 [Dexter] Remove false requirement of lldb for dexter regression tests on WindowsNot quite NFC because a little work was required to configure some tests to runon Windows at all.Before this patch on Windows: $ llvm-lit cross-project-tests\debuginfo-tests\dexter\feature-tests Unsupported: 49 Passed : 23After this patch on Windows: $ llvm-lit cross-project-tests\debuginfo-tests\dexter\feature-tests Unsupported : 27 Passed : 39 Expectedly failed: 6There are 3 main changes here. The first is to add a few more substitutions incross-project-tests/lit.cfg.py so that tests need to use specific flags canstill use the dexter regression test defaults for the native platform. Theseare: %dexter_regression_test_debugger %dexter_regression_test_builder %dexter_regression_test_cflags %dexter_regression_test_ldflagsTests that now use these options and therefore can be run on Windows too(though the second is still failing for unknown reasons): cross-project-tests/debuginfo-tests/dexte/feature_tests /subtools/clang-opt-bisect/clang-opt-bisect.cpp /subtools/test/source-root-dir.cppThe second change is to remove spurious `REQUIRES: system-linux, lldb` and`UNSUPPORTED: system-windows` directives, and make changes to lit.local.cfgfiles that have the same effect. I've also added comments to the genuineREQUIRES, UNSUPPORTED, and XFAIL directives so it's easier to understandrequirements at a glance. The most common reason for a test to not be supportedon Windows is that it uses DexLimitSteps, DexDeclareAddress, or DexCommandLine,none of which are supported in the dbgeng driver.There are two failures on Windows that were previously hidden, which I'veXFAILed: cross-project-tests/debuginfo-tests/dexter/feature_tests /commands/perfect/dex_finish_test/default_conditional.cpp /commands/perfect/dex_finish_test/default_conditional_hit_count.cppAnd two that were easy to fix: cross-project-tests/debuginfo-tests/dexter/feature_tests /commands/perfect/dex_finish_test/default_simple.cpp /commands/perfect/dex_finish_test/default_hit_count.cppLastly, I've set three directories as unsupported. cross-project-tests/debuginfo-tests/dexter/feature_tests /commands/perfect/limit_steps /commands/perfect/dex_declare_address /commands/perfect/dex_declare_fileThe first two are unsupported on Windows because they contains tests for theDexLimitSteps and DexDeclareAddress commands which aren't supported in thedbgeng driver. The third is unsupported on all platforms as the tests involveinvoking clang directly, which isn't currently a supported way of buildingtests for dexter in lit (it can cause problems for cross compilers that cantarget the host, as the tests use the default triple and linker, which maybe aligned for the default target, not host).Tested on Windows and Linux.Reviewed By: jmorseDifferential Revision: https://reviews.llvm.org/D118048 List of files: /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp Wed, 26 Jan 2022 11:09:21 +0000 OCHyams <orlando.hyams@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp#f0eef1d2 [Dexter] Fix address_printing test by requiring lldbFixes a failure on the llvm-clang-x86_64-sie-ubuntu-fast buildbot causedby the test requiring lldb (with the standard dexter lit config), butnot including a "Requires: lldb" clause. List of files: /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp Wed, 01 Dec 2021 14:03:53 +0000 Stephen Tozer <stephen.tozer@sony.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp#0428d44d [Dexter] Add DexDeclareAddress command and address functionThis patch adds a new dexter command, DexDeclareAddress, which is usedto test the relative values of pointer variables. The motivation foradding this command is to allow meaningful assertions to be made aboutpointers that go beyond checking variable availability and nullequality.The full explanation and syntax is in Commands.md.Reviewed By: OrlandoDifferential Revision: https://reviews.llvm.org/D111447 List of files: /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/address_printing.cpp Wed, 01 Dec 2021 13:00:22 +0000 Stephen Tozer <stephen.tozer@sony.com>