Yup -- that was my first test run before I saw that request. If all goes according to plan we should get a nightly running at 5am Eastern which I think is noon in Israel. If there is a better time let me know -- nightly is a tricky concept with our geogrpahical distribution which runs from GMT-8 to GMT+2 at least . . .
On Wed, Feb 4, 2015 at 4:21 AM, Itamar Syn-Hershko <[email protected]> wrote: > Wyatt, can we have the entire test suite running nightly? > > -- > > Itamar Syn-Hershko > http://code972.com | @synhershko <https://twitter.com/synhershko> > Freelance Developer & Consultant > Lucene.NET committer and PMC member > > On Wed, Feb 4, 2015 at 3:28 AM, <[email protected]> wrote: > > > Build Lucene.NET :: Lucene.NET Nightly [master] #144 failed (Tests > failed: > > 1 (1 new), passed: 5, ignored: 1; snapshot dependency failed: Lucene.NET > :: > > Lucene.NET Core (new); NUnit error running tests in > > > 'Z:\Builds\work\bcdbe6b8cc677a49\src\Lucene.Net.Tests.Classification\bin\Release\Lucene.Net.Tests.Classifica...). > > Agent: JetBrains-dotnet-agent01 > > Build results: > > > http://teamcity.codebetter.com/viewLog.html?buildId=180536&buildTypeId=LuceneNet_LuceneNetNightly > > > > Failed Tests Summary: > > Newly failed tests (1 test, alphabetically ordered) > > ================================================================== > > Lucene.Net.Tests.dll: Lucene.Net.Util.TestPagedBytes.TestOverflow > > > > > > > > Newly failed tests details (naturally ordered) > > ================================================================== > > Lucene.Net.Tests.dll: Lucene.Net.Util.TestPagedBytes.TestOverflow (new) > > ================= > > Test(s) failed. Test exceeded Timeout value of 20000ms > > > > > > > > > ============================================================================ > > Configure email notifications: > > http://teamcity.codebetter.com/profile.html?init=1&tab=userNotifications > > >
