search for: pr6623

Displaying 6 results from an estimated 6 matches for "pr6623".

Did you mean: pr6613
2010 Apr 07
3
[LLVMdev] Call for Help: Testing
...r every release" > discounts a lot of good, hard work put in by a lot of people. There wasn't a > lot for "the community" to do before late last week except run tests, which in > fact a number of people did. Why? Prerelease 1 tarballs are available for at least 3 weeks. PR6623 was entered into bugzilla at March, 20, etc., etc., etc. > Did I miss an announcement of PR6586 somewhere?  The first I knew about it was > mid last week.  Maybe I missed the posting on this mailing list about it. > It's been open for almost a month.  Without knowing about that bug, i...
2010 Apr 07
0
[LLVMdev] Call for Help: Testing
..." discounts a lot of good, hard work put in by a lot of people. > > There wasn't a lot for "the community" to do before late last week except > > run tests, which in fact a number of people did. > > Why? Prerelease 1 tarballs are available for at least 3 weeks. PR6623 > was entered into bugzilla at March, 20, etc., etc., etc. But where was it posted to let people know about it? > > Did I miss an announcement of PR6586 somewhere?  The first I knew about > > it was mid last week.  Maybe I missed the posting on this mailing list > > about it....
2010 Apr 06
0
[LLVMdev] Call for Help: Testing
On Tuesday 06 April 2010 17:35:00 Tanya Lattner wrote: > >>> We need more people in the community to help and I can't see any way > >>> of sugar coating this message. > > > > AFAICT, the only bugs left are Clang bugs and a Darwin llvm-gfortran bug. > > The Linux bugs have all been triaged and either fixed, have what should > > be a simple
2010 Apr 06
3
[LLVMdev] Call for Help: Testing
On Apr 6, 2010, at 1:04 PM, David Greene wrote: > On Tuesday 06 April 2010 14:52:47 Dustin Laurence wrote: >> On 04/06/2010 11:45 AM, Tanya Lattner wrote: >>> While lack of linux testing of the testsuite is a problem, this is >>> not why the release is slipping. We need more people to fix bugs. It >>> can't be the same people fixing the bugs for every
2010 Apr 07
0
[LLVMdev] Call for Help: Testing
...f good, hard work put in by a lot of people. > > > There wasn't a lot for "the community" to do before late last week > except > > > run tests, which in fact a number of people did. > > > > Why? Prerelease 1 tarballs are available for at least 3 weeks. PR6623 > > was entered into bugzilla at March, 20, etc., etc., etc. > > But where was it posted to let people know about it? > It was posted to the dev mailing lists. In fact, that's the *exact* same place that your email was posted. How can you claim that this is impossible or even ha...
2010 Apr 07
2
[LLVMdev] Call for Help: Testing
On Wednesday 07 April 2010 13:44:44 David Greene wrote: > > Also, I should note that master bug in question was *explicitly* > > mentioned in Tanya's 2.7 prerelease 1 e-mail sent on March, 17. > > Have you seen this e-mail? > > Hmm, I'm sure I got it. I must have missed it. I can't read the list > every day and after a few days things get pretty backed up.