aboutsummaryrefslogtreecommitdiff
path: root/debuginfo-tests/foreach.m
AgeCommit message (Collapse)AuthorFilesLines
2017-11-21Re-revert "Refactor debuginfo-tests."Zachary Turner1-0/+31
This is still breaking greendragon. At this point I give up until someone can fix the greendragon bots, and I will probably abandon this effort in favor of using a private github repository. llvm-svn: 318722
2017-11-20Resubmit "Refactor debuginfo-tests" again.Zachary Turner1-31/+0
This was reverted due to the tests being run twice on some build bots. Each run had a slightly different configuration due to the way in which it was being invoked. This fixes the problem (albeit in a somewhat hacky way). Hopefully in the future we can get rid of the workflow of running debuginfo-tests as part of clang, and then this hack can go away. llvm-svn: 318697
2017-11-17Re-revert "Refactor debuginfo-tests"Zachary Turner1-0/+31
This is still broken because it causes certain tests to be run twice with slightly different configurations, which is wrong in some cases. You can observe this by running: ninja -nv check-all | grep debuginfo-tests And seeing that it passes clang/test and clang/test/debuginfo-tests to lit, which causes it to run debuginfo-tests twice. The fix is going to involve either: a) figuring out that we're running in this "deprecated" configuration, and then deleting the clang/test/debuginfo-tests path, which should cause it to behave identically to before, or: b) make lit smart enough that it doesn't descend into a sub-suite if that sub-suite already has a lit.cfg file. llvm-svn: 318486
2017-11-16Resubmit "Refactor debuginfo-tests"Zachary Turner1-31/+0
This was reverted due to some failures on specific darwin buildbots, the issue being that the new lit configuration was not setting the SDKROOT environment variable. We've tested a fix locally and confirmed that it works, so this patch resubmits everything with the fix applied. llvm-svn: 318435
2017-11-13Revert "Update test_debuginfo.pl script to point to new tree location."Zachary Turner1-0/+31
This reverts the aforementioned patch and 2 subsequent follow-ups, as some buildbots are still failing 2 tests because of it. Investigation is ongoing into the cause of the failures. llvm-svn: 318112
2017-11-10[debuginfo-tests] Make debuginfo-tests work in a standard configuration.Zachary Turner1-31/+0
Previously, debuginfo-tests was expected to be checked out into clang/test and then the tests would automatically run as part of check-clang. This is not a standard workflow for handling external projects, and it brings with it some serious drawbacks such as the inability to depend on things other than clang, which we will need going forward. The goal of this patch is to migrate towards a more standard workflow. To ease the transition for build bot maintainers, this patch tries not to break the existing workflow, but instead simply deprecate it to give maintainers a chance to update the build infrastructure. Differential Revision: https://reviews.llvm.org/D39605 llvm-svn: 317925
2014-10-18New round of fixes for "Always compile debuginfo-tests for the host triple"Filipe Cabecinhas1-2/+2
clang tests were breaking, at least when compiling clang only, from an installed llvm. Make the lit.cfg script deal with the case when we don't have a host_triple available. llvm-svn: 220152
2014-10-16Always compile debuginfo-tests for the host tripleFilipe Cabecinhas1-2/+2
Since these tests expect a working debugger, always compile them for the host triple, assuming a working debugger is present. This enables us to compile and run them, even when clang is, by default, a cross-compiler (but can still target the host). llvm-svn: 219992
2012-10-20XTARGET was removed, update debug-info tests.Argyrios Kyrtzidis1-2/+2
llvm-svn: 166362
2011-06-13New test case for r132949.Devang Patel1-0/+31
llvm-svn: 132950