search for: blockers

Hello everyone, According to the release schedule, we're supposed to be tagging 'final' on Wednesday. Unfortunately, I suspect we will be a little late. There are currently 32 open release blockers: https://bugs.llvm.org/buglist.cgi?f1=blocked&o1=equals&v1=33849&query_format=advanced&resolution=--- Some of those have traction, but many don't. Some just need bisection, checking if the issue still reproduces, etc. Please help take a look at the bugs in that list. It would...

...eed people to help fix regressions and to participate in testing the release. Without this support, I see no reason that the release team should spend their time qualifying a release. We need to get all regressions fixed before 2.7 can continue onto pre-release2. Please take a look at all release blockers: http://llvm.org/bugs/show_bug.cgi?id=6586 If you can help fix any of these bugs, we would really appreciate it. I'd advise using the release branch directly instead of the tarballs since several fixes have gone in. There are 2 patches I have left to merge once I resolve the conflicts. Thanks...

Dear everyone, The release branch was recently created from trunk at r308441 and the trunk version was subsequently incremented to 6.0.0. Release blockers are tracked by https://bugs.llvm.org/show_bug.cgi?id=33849 Please mark any bugs, old or new, that you think need to be fixed before the release as blocking that. Please help out with the release by notifying me of any bugs, commits, or other issues you think might be relevant; ideally by marking t...

On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > Please take a look at all release blockers: > http://llvm.org/bugs/show_bug.cgi?id=6586 5893 is not release-critical according to Doug. 6640 appears to be a test system problem with a patch available (one of the ones you're working on?) Which bugs do you have patches for? I don't want to start looking at something if it'...

So, we’ve had this conversation a few times, and I wanted to coalate a status report for all the interested parties. Here's the outstanding work and my (not necissarily correct) view of the status and importance of each one: * Bug 12157 - llvmconfig.cmake.in make cmake installations not relocatable - There are patches on the bug that we should review, test, and land * Bug 14109 - CMake

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 Our timeline had us start the code freeze last Friday. However, we have not released an RC0 because we have been waiting for PVH dom0 support. Adding bug fixes during RCs makes sense, but RC0 should contain all of the functionality we expect to be in the final release. PVH dom0 support

...was all Out of memory). Now in 2.7 the JIT crashes when running out of memory. While that is a bug, I'm not sure if its part of the release criteria. I tried to make some changes in MallocSlabAllocator to not crash, but then FoldingSet crashed on OOM. P.S.: looking at the current 2.7 release blockers I only see PR6696 as relevant, the others are warnings, experimental code, and a fortran failure. Is that the case, or are the others release blockers too? Best regards, --Edwin

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 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/...

...vmorg-11.0.0-rc4 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc4 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc4 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725 Release testers: if you still have cycles, please run the test script, share your results, and upload binaries. And thank you very much for your help so far. This is very similar to rc3, but picks up a few more fixes. Again, there are currently no open release blockers...

...'s time to prepare the 3.12.5 release, which falls on the 10th of each month, and hence would be 12-01-2018 this time around. This mail is to call out the following, 1) Are there any pending *blocker* bugs that need to be tracked for 3.12.5? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2) Pending reviews in the 3.12 dashboard will be part of the release, *iff* they pass regressions and have the review votes, so use the dashboard [2] to check on the status of your patches to 3.12 and get these going 3) I...

...t; SingleSource/UnitTests/Vector/SSE/sse.stepfft >> >> JIT failures in clang, pass in llvm-gcc: >> MultiSource/Applications/sqlite3/sqlite3 >> SingleSource/Regression/C++/ofstream_ctor >> > > This isn't part of our release criteria. So, these are not release blockers. Ok, something to keep in mind for LLVM 2.8 then. > >> 3. Some performance regressions GCC/LLC (2.6 -> 2.7), but keep in mind >> that I wasn't using GCC 4.4.3 as comparison for llvm 2.6! >> >> MultiSource/Applications/hexxagon/hexxagon 1.22 -> 1.14 >>...

Hi all, Time for another update on the status of the CMake build system. Completed: * Bug 18496 - [cmake] .S assembly files not compiled by cmake in libclang_rt.ARCH * Bug 22725 - lldb build with cmake fails with "Program error: Invalid parameters entered, -h for help. " * Update GettingStarted to prefer CMake Still Outstanding: * Bug 14109 - CMake build for compiler-rt should use

...vmorg-11.0.0-rc3 tag was just created. Source code and docs are available at https://prereleases.llvm.org/11.0.0/#rc3 and https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc3 Pre-built binaries will be added as they become ready. Please file bug reports for any issues you find as blockers of https://llvm.org/pr46725 Release testers: please start your engines, run the script, share your results, and upload binaries. And thank you very much for your help so far. There are currently no open release blockers, so unless anything new and bad comes up, this is what the final release will...

Hello Everyone, 3 weeks back we (most of the maintainers of Gluster projects) had a meeting, and we discussed about features required for Gluster 4.0 and also the possible dates. <https://hackmd.io/GwIwnGBmCsCM0FoDMsAcBTBAWADLLCYATLJiOmBVgMYAmAhvbLUA#summary> Summary: - It is agreed unanimously that the Gluster 4.0 should be feature based release, and not just time based. -

On Tuesday 30 March 2010 17:45:16 David Greene wrote: > On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > > Please take a look at all release blockers: > > http://llvm.org/bugs/show_bug.cgi?id=6586 > > 5893 is not release-critical according to Doug. > > 6640 appears to be a test system problem with a patch available (one of the > ones you're working on?) > > Which bugs do you have patches for? I don't want to s...

...ime to prepare the 3.11.1 release, which falls on the 20th of each month [4], and hence would be June-20th-2017 this time around. This mail is to call out the following, 1) Are there any pending *blocker* bugs that need to be tracked for 3.11.1? If so mark them against the provided tracker [1] as blockers for the release, or at the very least post them as a response to this mail 2) Pending reviews in the 3.11 dashboard will be part of the release, *iff* they pass regressions and have the review votes, so use the dashboard [2] to check on the status of your patches to 3.11 and get these going 3) Em...

On Mar 30, 2010, at 3:45 PM, David Greene wrote: > On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: > >> Please take a look at all release blockers: >> http://llvm.org/bugs/show_bug.cgi?id=6586 > > 5893 is not release-critical according to Doug. > Will take care of this. > 6640 appears to be a test system problem with a patch available (one of the > ones you're working on?) > > Which bugs do you have patche...

On Mar 30, 2010, at 4:04 PM, David Greene wrote: > On Tuesday 30 March 2010 17:45:16 David Greene wrote: >> On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote: >>> Please take a look at all release blockers: >>> http://llvm.org/bugs/show_bug.cgi?id=6586 >> >> 5893 is not release-critical according to Doug. >> >> 6640 appears to be a test system problem with a patch available (one of the >> ones you're working on?) >> >> Which bugs do you have p...

...changes in as soon as possible so that they > are well-tested before the branch. And please keep on top of any failures you see. > > Now would be a good time to look through the bugzilla database to see > if there are any issues you can address. :-) Is there a list of potential branch blockers? E.g. PR 10912 is a crash-on-valid for Qt4 builds, which is kind of high profile. Joerg

As of today, there are two weeks left until we branch for the 3.0 release. Please get your changes in as soon as possible so that they are well-tested before the branch. And please keep on top of any failures you see. Now would be a good time to look through the bugzilla database to see if there are any issues you can address. :-) -bw