aheejin wrote:
@llvm-ci The CI failure does not look relevant.
https://github.com/llvm/llvm-project/pull/130220
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvm-ci wrote:
LLVM Buildbot has detected a new failure on builder `llvm-clang-x86_64-sie-win`
running on `sie-win-worker` while building `clang` at step 7
"test-build-unified-tree-check-all".
Full details are available at:
https://lab.llvm.org/buildbot/#/builders/46/builds/13207
Here is th
https://github.com/aheejin closed
https://github.com/llvm/llvm-project/pull/130220
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
https://github.com/dschuff approved this pull request.
https://github.com/llvm/llvm-project/pull/130220
___
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
llvmbot wrote:
@llvm/pr-subscribers-clang
Author: Heejin Ahn (aheejin)
Changes
I think it is generally better for tests have some descriptive function names
so that we can insert new tests in the middle and don't have to renumber all
tests.
Also recently I added a (named) test to this f
https://github.com/aheejin created
https://github.com/llvm/llvm-project/pull/130220
I think it is generally better for tests have some descriptive function names
so that we can insert new tests in the middle and don't have to renumber all
tests.
Also recently I added a (named) test to this fi
