reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mariia Mykhailova <mamyk...@microsoft.com>
Subject RE: Error messages in reef functional tests
Date Wed, 15 Jun 2016 17:19:56 GMT
For the "program has stopped working" error pop-ups, you can try following instructions from
https://www.raymond.cc/blog/disable-program-has-stopped-working-error-dialog-in-windows-server-2008/
Enabling "prevent display of the user interface for critical errors" seems to have helped
on Julia's machine.

-Mariia

-----Original Message-----
From: Julia Wang (QIUHE) [mailto:Qiuhe.Wang@microsoft.com] 
Sent: Tuesday, May 24, 2016 3:13 PM
To: dev@reef.apache.org
Subject: RE: Error messages in reef functional tests

Looks like the screen shot becomes text in my previous email. Basically I got the same message
box in .Net testing that says:

messages -REEF.Bridge.exe has stopped

Julia

-----Original Message-----
From: Dhruv Mahajan [mailto:dhruv.mahajan@gmail.com]
Sent: Monday, May 16, 2016 3:41 PM
To: dev@reef.apache.org
Subject: Re: Error messages in reef functional tests

Also I cloned reef at some other location on my machine and re-ran tests.
Got the same errors in tests. This rules out cleaning issues.

Dhruv

On Mon, May 16, 2016 at 3:38 PM, Andrew Chung <afchung90@gmail.com> wrote:

> I've gotten the test logs from Dhruv, and judging from what I see in 
> the logs prior to looking into the code, what is happening seems like 
> the
> following:
>
> 1. Evaluator fails.
> 2. FailedEvaluatorHandler gets called.
> 3. We send request for another Evaluator in FailedEvaluatorHandler.
> 4. Before the EvaluatorRequestor sends the request, the Driver 
> idleness handler kicks in and detects that the Driver is idle, i.e. no 
> active Evaluators and no outstanding requests.
> 5. Driver is declared as idle and shut down.
> 6. EvaluatorRequestor processes requests. Evaluator starts as Driver 
> is shutting down.
> 7. Test failure.
>
> I'll take a closer look at the code and provide updates.
>
> Thanks,
> Andrew
>
> On Mon, May 16, 2016 at 3:03 PM, Dhruv Mahajan 
> <dhruv.mahajan@gmail.com>
> wrote:
>
> > Did deep cleaning and ran tests from command line...Still getting 
> > one error. Also got the error window.
> >
> >
> >
> Org.Apache.REEF.Tests.Functional.Bridge.TestUnhandledTaskException.Tes
> tUnhandledTaskExceptionCrashesEvaluator
> >
> > Expected number of evaluators to fail (2) differs from actual number 
> > of failed evaluator indicators (1)\r\nExpected: True\r\nActual:
> > False
> >
> >    at
> >
> Org.Apache.REEF.Tests.Functional.ReefFunctionalTest.ValidateSuccessFor
> LocalRuntime(Int32
> > numberOfContextsToClose, Int32 numberOfTasksToFail, Int32 
> > numberOfEvaluatorsToFail, String testFolder) in
> >
> >
> c:\Users\dhrumaha\Desktop\projects\reef\lang\cs\Org.Apache.REEF.Tests\
> Functional\ReefFunctionalTest.cs:line
> > 169
> >    at
> >
> Org.Apache.REEF.Tests.Functional.Bridge.TestUnhandledTaskException.Tes
> tUnhandledTaskExceptionCrashesEvaluator()
> > in
> >
> c:\Users\dhrumaha\Desktop\projects\reef\lang\cs\Org.Apache.REEF.Tests\
> Functional\Bridge\TestUnhandledTaskException.cs:line
> > 54
> >
> >
> > On Mon, May 16, 2016 at 2:29 PM, Dhruv Mahajan 
> > <dhruv.mahajan@gmail.com>
> > wrote:
> >
> > > Command line ... Lemme do deep clean once again.
> > >
> > > Dhruv
> > >
> > > On Mon, May 16, 2016 at 2:27 PM, Markus Weimer <markus@weimo.de>
> wrote:
> > >
> > >> Are you running from the command line or Visual Studio? The tests 
> > >> pass
> > all
> > >> the time from the command line for me, and AppVeyor now reports 
> > >> the
> same
> > >> ...
> > >>
> > >> Markus
> > >>
> > >
> > >
> >
>
Mime
View raw message