similar to: [LLVMdev] 1 week before 1.8 branch creation!

LLVMers, It is now 1 week before I will create the 1.9 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before the

LLVM Developers, It is now 1 week before I will create the 2.0 release branch. I'm asking that all platform maintainers and available llvm developers review the nightly tester results. Please XFAIL any dejagnu tests that are currently failing, fix any warnings, and review the results of the full llvm test suite. If a test failure is determined to be something that needs to be fixed before

Tanya M. Lattner wrote: > I'm asking that all platform maintainers and available llvm developers > review the nightly tester results. Please XFAIL any dejagnu tests that are > currently failing, fix any warnings, and review the results of the full > llvm test suite. If a test failure is determined to be something that > needs to be fixed before the release, please fix it or

I will be creating the branch at 9PM PST. Please refrain from checking in any large changes until after the branch creation. I'm still seeing unexpected dejagnu failures for PPC and X86. Platform maintainers, please XFAIL these and file bugzilla bugs. Email me if you have concerns or questions. -Tanya

Tanya Lattner wrote: > I've finished adding the -rundejagnu option to the nightly tester script, > which was the last step to fully support Dejagnu. I think now is the > appropriate time to discuss keeping QMTest or switching to Dejagnu. A lot > of work went into using QMTest, so I think we should make this decision > carefully and before the 1.4 release. > > Here are the

LLVMers, Its been over 6 months since the last LLVM release, and there have been a huge number of improvements in LLVM CVS. Chris asked me to fill the role of release manager, and would like to get the release out the door in the next couple weeks. The target release date for 1.7 is April 20th. We would appreciate help from anyone who is available. The process will be as follows: 1) All

Aaron Gray wrote: > It would be good to have a mailing list for test results where 'make check' > results could be posted so that there is some reference and people could > avoid repeating builds. There's the llvm-testresults list, but I find it less than fully useful because it's not immediately obvious from scanning message subjects if there's been a test

I've finished adding the -rundejagnu option to the nightly tester script, which was the last step to fully support Dejagnu. I think now is the appropriate time to discuss keeping QMTest or switching to Dejagnu. A lot of work went into using QMTest, so I think we should make this decision carefully and before the 1.4 release. Here are the pros and cons in my eyes, please feel free to add your

On Sunday 28 November 2004 00:24, Tanya Lattner wrote: Just some comments from a QMTest user... Note however, that even with them, dejagnu looks better. > Cons of QMTest: > 1) You have to use the gui to add directories. I think you're wrong. Manually creating a directory would work, as QMTest does not place anything special in directories. > 2) You have to use the gui to XFAIL

On Fri, Feb 20, 2009 at 11:45 PM, Tanya Lattner <tonic at nondot.org> wrote: > LLVMers, > > The 2.5 pre-release2 is finally available for testing: > http://llvm.org/prereleases/2.5/ > > If you have time, I'd appreciate anyone who can help test the release. > Please do the following: > > 1) Download/compile llvm source, and either compile llvm-gcc source or use

> Tanya M. Lattner wrote: > >> How large of a change have you made? With 3 days before the branch >> creation, I strongly advise people not to be checking in major changes. > > Depends how you look at it. Structurally, it separates two files into > four and moves some functionality from one class to a new class, so in a > sense that's a big change.

In an effort to simplify how tests are added to the LLVM testsuite, I've added support for Dejagnu. This only applies to the Feature and Regression tests. If this experiment goes well, we may switch from using QMTest to Dejagnu. I'm asking for people (especially those running nightly testers) to give Dejagnu a try. You will need to install Dejagnu (http://www.gnu.org/software/dejagnu/)

Hi Chris, > I think that this is a great idea. However, instead of picking up yet > another setting of testing infrastructure, I think we should make what > we have already (the nightly testers) better. In particular, the main > page of the tester: > http://llvm.org/nightlytest/ > > Already captures a lot of this: it tells you the number of unexpected > failures,

On Sat, 5 May 2007, David Greene wrote: > There's the llvm-testresults list, but I find it less than fully useful > because it's not immediately obvious from scanning message subjects if > there's been a test failure. It's a lot of messages to wade through and > read to get this information. Right. > What about a Tinderbox-like setup where we could consult a web

On May 9, 5:37 pm, "Tanya M. Lattner" <to... at nondot.org> wrote: > LLVMers, > > I will be creating the 2.3 release branch today at 9PM PDT. During that > time, commit access to SVN will be forbidden. I will send out mail shortly > before the branch creation, and once it has been completed. Hi Tanya, I do not really understand this strict rule :-) While I get it

Aaron Gray wrote: >>> On Sat, 5 May 2007, Aaron Gray wrote: >>> >>>> It would be good to have a mailing list for test results where 'make >>>> check' >>>> results could be posted so that there is some reference and people could >>>> avoid repeating builds. >>>> >>> llvm-testresults :)

LLVMers, I will be creating the branch in 30 minutes (9PM PDT). At that time, I will send out mail announcing SVN commit access is suspended. Those with commit privileges should refrain from committing until I send out mail saying commit access is restored. Thanks, Tanya Lattner

LLVMers, I will be creating the 2.3 release branch today at 9PM PDT. During that time, commit access to SVN will be forbidden. I will send out mail shortly before the branch creation, and once it has been completed. Thanks, Tanya

Hi, Tanya! >* November 6, 2006: Code freeze and release branch created. Documentation > revisions. Does it mean that I can commit my changes to LLVM until November 6? Thanks. Tony. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20061030/1e4ae18f/attachment.html>

LLVMers, The LLVM 2.2 code freeze and branch creation is less than 1 week away. At this point, I'm encouraging everyone to think "stability". Please do not check in major changes and please carefully watch all the nightly tester results when commiting any changes at all. As a reminder, here is the complete release schedule (which can also be found on the main page in the right