<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in feature_tests</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>de3f8155 - [Dexter] Remove false requirement of lldb for dexter regression tests on Windows</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/#de3f8155</link>
        <description>[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&apos;ve also added comments to the genuineREQUIRES, UNSUPPORTED, and XFAIL directives so it&apos;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&apos;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&apos;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&apos;t supported in thedbgeng driver. The third is unsupported on all platforms as the tests involveinvoking clang directly, which isn&apos;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/commands/perfect/limit_steps/limit_steps_check_json_step_count.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/limit_steps/limit_steps_line_mismatch.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/limit_steps/limit_steps_same_line_conditional.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/label_another_line.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/label_offset.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/source-root-dir.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/view.cpp</description>
        <pubDate>Wed, 26 Jan 2022 11:00:00 +0000</pubDate>
        <dc:creator>OCHyams &lt;orlando.hyams@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>1364750d - [RFC][debuginfo-test] Rename debug-info lit tests for general purposes</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/#1364750d</link>
        <description>[RFC][debuginfo-test] Rename debug-info lit tests for general purposesDiscussion thread:https://lists.llvm.org/pipermail/llvm-dev/2021-January/148048.htmlMove debuginfo-test into a subdirectory of a new top-level directory,called cross-project-tests. The new name replaces &quot;debuginfo-test&quot; as anLLVM project enabled via LLVM_ENABLE_PROJECTS.Differential Revision: https://reviews.llvm.org/D95339Reviewed by: aprantl

            List of files:
            /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/unreachable.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/lit.local.cfg/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/help/help.test/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/list-debuggers/list-debuggers.test/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_bad_label_ref.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_duplicate_label.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_paren.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_paren_mline.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_syntax.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_syntax_mline.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_type.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_type_mline.cpp</description>
        <pubDate>Mon, 08 Feb 2021 15:00:00 +0000</pubDate>
        <dc:creator>James Henderson &lt;james.henderson@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>0428d44d - [Dexter] Add DexDeclareAddress command and address function</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/#0428d44d</link>
        <description>[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/err_duplicate_address.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/test/err_undeclared_addr.cpp</description>
        <pubDate>Wed, 01 Dec 2021 13:00:00 +0000</pubDate>
        <dc:creator>Stephen Tozer &lt;stephen.tozer@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>2bd62e0b - [dexter] Don&apos;t generate results files by default</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/#2bd62e0b</link>
        <description>[dexter] Don&apos;t generate results files by defaultDexter saves various files to a new results directory each time it is run(including when it&apos;s run by lit tests) and there isn&apos;t a way to opt-out. Thispatch reconfigures the behaviour to be opt-in by removing the default`--results-directory` location. Now results are only saved if`--results-directory` is specified.Reviewed By: jmorseDifferential Revision: https://reviews.llvm.org/D119545

            List of files:
            /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/clang-opt-bisect/clang-opt-bisect-results.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/subtools/clang-opt-bisect/clang-opt-bisect.cpp</description>
        <pubDate>Fri, 11 Feb 2022 15:00:00 +0000</pubDate>
        <dc:creator>OCHyams &lt;orlando.hyams@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>0f92c113 - [Dexter] Allow DexUnreachable in supplementary .dex files</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/#0f92c113</link>
        <description>[Dexter] Allow DexUnreachable in supplementary .dex filesDexUnreachable is a useful tool for specifying that lines shouldn&apos;t bestepped on. Right now they have to be placed in the source file; lets allowthem to be placed instead in a detached .dex file, by adding on_line andline-range keyword arguments to the command.Differential Revision: https://reviews.llvm.org/D115449

            List of files:
            /llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/unreachable_not_cmd_lineno.cpp/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/commands/perfect/unreachable_on_line.cpp</description>
        <pubDate>Mon, 10 Jan 2022 12:00:00 +0000</pubDate>
        <dc:creator>Jeremy Morse &lt;jeremy.morse@sony.com&gt;</dc:creator>
    </item>
<item>
        <title>1c8366f9 - [Dexter] Collate penalties of the same type into a single line for each</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/cross-project-tests/debuginfo-tests/dexter/feature_tests/#1c8366f9</link>
        <description>[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, &apos;Variable optimized out&apos;, 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</description>
        <pubDate>Tue, 01 Mar 2022 13:00:00 +0000</pubDate>
        <dc:creator>Stephen Tozer &lt;stephen.tozer@sony.com&gt;</dc:creator>
    </item>
</channel>
</rss>
