cjdb added a comment. @fdeazeve I haven't been able to repro this issue at all.
In D116203#3740092 <https://reviews.llvm.org/D116203#3740092>, @fdeazeve wrote: > In D116203#3740015 <https://reviews.llvm.org/D116203#3740015>, @cjdb wrote: > >> In D116203#3739856 <https://reviews.llvm.org/D116203#3739856>, @fdeazeve >> wrote: >> >>> It seems like non-lldb bots are also failing, if it makes it easier to >>> reproduce: >>> >>> https://green.lab.llvm.org/green/view/Clang/job/clang-stage1-RA/30837/consoleFull#-54352964249ba4694-19c4-4d7e-bec5-911270d8a58c >> >> Thanks for flagging this. Based on the fact it only seems to be >> `remove_reference_t`, I'm wondering if this is an issue with D131732 >> <https://reviews.llvm.org/D131732> (which was merged immediately after >> D116203 <https://reviews.llvm.org/D116203>). > > I'm not sure, to expand on my previous message, I tested these two commits > which appear one right after the other in the log: > > - e9ef45635b77 > <https://reviews.llvm.org/rGe9ef45635b77598fc9ce0cd38d7d3f8c9d88a49d> (14 > hou..) cjdb@g.. [clang] adds unary type transformations as compiler built-ins > - d2d77e050b32 > <https://reviews.llvm.org/rGd2d77e050b32ce3f917688aeeb9e6f8f3c209560> (15 > hou..) Ting.W.. [PowerPC][Coroutines] Add tail-call check with call > information for coroutines > > The tests pass on `d2d77e050b32` and fail on `e9ef45635b77` I haven't been able to repro yet. If you're able to test without In D116203#3740227 <https://reviews.llvm.org/D116203#3740227>, @aprantl wrote: > @cjdb Would you mind reverting the patch until we figured out a solution to > unblock the CI? Sure, go ahead. I'm not even able to get to a point where I can repro the issue, as I get the following: Command Output (stdout): -- lldb version 16.0.0git (g...@github.com:llvm/llvm-project.git revision 11ce014a121ed0bbdbb2af6ea20c75f85e89fbe9) clang revision 11ce014a121ed0bbdbb2af6ea20c75f85e89fbe9 llvm revision 11ce014a121ed0bbdbb2af6ea20c75f85e89fbe9 Unable to load lldb extension module. Possible reasons for this include: 1) LLDB was built with LLDB_ENABLE_PYTHON=0 2) PYTHONPATH and PYTHONHOME are not set correctly. PYTHONHOME should refer to the version of Python that LLDB built and linked against, and PYTHONPATH should contain the Lib directory for the same python distro, as well as the location of LLDB's site-packages folder. 3) A different version of Python than that which was built against is exported in the system's PATH environment variable, causing conflicts. 4) The executable '/tmp/lldb-breaks/bin/lldb' could not be found. Please check that it exists and is executable. -- Command Output (stderr): -- Traceback (most recent call last): File "/home/cjdb/projects/llvm-bisect/lldb/test/API/dotest.py", line 7, in <module> lldbsuite.test.run_suite() File "/home/cjdb/projects/llvm-bisect/lldb/packages/Python/lldbsuite/test/dotest.py", line 892, in run_suite import lldb ModuleNotFoundError: No module named 'lldb' 1 and 4 seem to be fine. Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D116203/new/ https://reviews.llvm.org/D116203 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
