<?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 Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>d4b08ccb - [lldb] Replace TestAbortExitCode with a debugserver specific test</title>
        <link>http://172.16.0.5:8080/history/llvm-project-15.0.7/lldb/test/API/macosx/debugserver-exit-code/Makefile#d4b08ccb</link>
        <description>[lldb] Replace TestAbortExitCode with a debugserver specific testWhen I added TestAbortExitCode I actually planned this to be a generic test for theexit code functionality on POSIX systems. However due to all the different test setups wecan have I don&apos;t think this worked out. Right now the test had to be made so permissivethat it pretty much can&apos;t fail.Just to summarize, we would need to support the following situations:1. ToT debugserver (on macOS)2. lldb-server (on other platforms)3. Any old debugserver version when using the system debugserver (on macOS)This patch is removing TestAbortExitCode and adds a ToT debugserver specific testthat checks the patch that motivated the whole exit code testing. There is alreadyan exit-code test for lldb-server from what I can see and 3) is pretty much untestableas we don&apos;t know anything about the system debugserver.Reviewed By: kastiglioneDifferential Revision: https://reviews.llvm.org/D89305

            List of files:
            /llvm-project-15.0.7/lldb/test/API/macosx/debugserver-exit-code/Makefile</description>
        <pubDate>Thu, 12 Nov 2020 16:20:11 +0000</pubDate>
        <dc:creator>Raphael Isemann &lt;teemperor@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
