[PATCH] D39838: [clang] [python] [tests] Update priority values in code completion test

2017-11-09 Thread Michał Górny via Phabricator via cfe-commits
This revision was automatically updated to reflect the committed changes. Closed by commit rL317828: [python] [tests] Update priority values in code completion test (authored by mgorny). Changed prior to commit: https://reviews.llvm.org/D39838?vs=17=122304#toc Repository: rL LLVM

[PATCH] D39838: [clang] [python] [tests] Update priority values in code completion test

2017-11-09 Thread Michał Górny via Phabricator via cfe-commits
mgorny added a comment. In https://reviews.llvm.org/D39838#920399, @ilya-biryukov wrote: > LGTM. > > Can we run those tests as part of `check-all` cmake target or setup a > buildbot that runs those? Seems surprising it went unnoticed for so long. I was thinking of that but I think it'd be

[PATCH] D39838: [clang] [python] [tests] Update priority values in code completion test

2017-11-09 Thread Ilya Biryukov via Phabricator via cfe-commits
ilya-biryukov accepted this revision. ilya-biryukov added a comment. This revision is now accepted and ready to land. LGTM. Can we run those tests as part of `check-all` cmake target or setup a buildbot that runs those? Seems surprising it went unnoticed for so long. Repository: rL LLVM

[PATCH] D39838: [clang] [python] [tests] Update priority values in code completion test

2017-11-09 Thread Michał Górny via Phabricator via cfe-commits
mgorny created this revision. The priority for destructors and operators was reduced in https://reviews.llvm.org/rL314019. Adjust the values used in the test appropriately to fix the test failure. Repository: rL LLVM https://reviews.llvm.org/D39838 Files: