Maybe https://reviews.llvm.org/D65163 <https://reviews.llvm.org/D65163> will fix this issue?
> On Jul 23, 2019, at 11:57 AM, Ted Woodward <tedw...@quicinc.com> wrote: > > We saw the same thing internally. We don’t use lldb-vscode, so we turned off > those tests. > > Greg, any thoughts on lldb-vscode tests running forever on Linux? > > From: lldb-dev <lldb-dev-boun...@lists.llvm.org> On Behalf Of Brian Cain via > lldb-dev > Sent: Monday, July 22, 2019 10:44 PM > To: Hans Wennborg <h...@chromium.org> > Cc: llvm-dev <llvm-...@lists.llvm.org>; Release-testers > <release-test...@lists.llvm.org>; clangd-...@lists.llvm.org; openmp-dev > (openmp-...@lists.llvm.org) <openmp-...@lists.llvm.org>; LLDB Dev > <lldb-dev@lists.llvm.org>; cfe-dev <cfe-...@lists.llvm.org>; > libcxx-...@lists.llvm.org > Subject: [EXT] Re: [lldb-dev] [Release-testers] [9.0.0 Release] The release > branch is open; trunk is now 10.0.0 > > Uploaded ubuntu 14. > > I had to kill some tests executing "lldb-vscode", they had been running for > 12+ hours without completing. > > b57383860c7e4317b0194d1a91836e01bd637c95 > clang+llvm-8.0.1-x86_64-linux-gnu-ubuntu-14.04.tar.xz > > On Thu, Jul 18, 2019 at 7:19 AM Hans Wennborg via Release-testers > <release-test...@lists.llvm.org <mailto:release-test...@lists.llvm.org>> > wrote: > Hello everyone, > > The release branch for LLVM 9 and its sub-projects was just created > from trunk at r366426, and the trunk version was subsequently bumped > to 10.0.0. > > Release blockers are tracked by https://llvm.org/PR42474 > <https://llvm.org/PR42474> Please mark > any bugs, old or new, that need to be fixed before the release as > blocking that. > > To get a change committed to the branch, first commit it to trunk as > usual, and then request it to be merged --- ideally by filing a > blocker bug on https://llvm.org/PR42474 <https://llvm.org/PR42474>, or by > cc'ing me on the commit > email. (Please don't request merges over IRC; there's a high risk I'll > miss them.) > > Please help with the release by notifying me about any bugs, commits, > or other issues you think might be relevant. If it's not already > tracked as a blocker of the release bug, or I'm not cc'd on an email > about it, I will probably miss it. > > When the branch is in good enough shape, hopefully by tomorrow, the > first release candidate (RC1) will be tagged and testing can begin. > The release schedule can be found under "Upcoming Releases" to the > right at https://llvm.org <https://llvm.org/> > > Many thanks, > Hans > _______________________________________________ > Release-testers mailing list > release-test...@lists.llvm.org <mailto:release-test...@lists.llvm.org> > https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > <https://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers> > > > -- > -Brian
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
