Travis build fails by timeout in testErrnoCallback for all pull requests

[forax at univ-mlv.fr]

Hi Doug,
i think you're right not the same bug,
mine is spurious and doesn't seem to be related to graal after all,
sorry for the noise.

Rémi 

----- Mail original -----
> De: "Doug Simon" <doug.simon at oracle.com>
> À: "Remi Forax" <forax at univ-mlv.fr>
> Cc: "Dmitry Samersoff" <dms at samersoff.net>, "graal-dev" <graal-dev at openjdk.java.net>
> Envoyé: Lundi 16 Juillet 2018 16:59:24
> Objet: Re: Travis build fails by timeout in testErrnoCallback for all pull requests

>> On 16 Jul 2018, at 16:00, Remi Forax <forax at univ-mlv.fr> wrote:
>> 
>> Hi Doug,
>> 
>> ----- Mail original -----
>>> De: "Doug Simon" <doug.simon at oracle.com>
>>> À: "Dmitry Samersoff" <dms at samersoff.net>
>>> Cc: "graal-dev" <graal-dev at openjdk.java.net>
>>> Envoyé: Lundi 16 Juillet 2018 15:48:10
>>> Objet: Re: Travis build fails by timeout in testErrnoCallback for all pull
>>> requests
>> 
>>>> On 16 Jul 2018, at 15:28, Dmitry Samersoff <dms at samersoff.net> wrote:
>>>> 
>>>> Hello Everybody,
>>>> 
>>>> Travis build "JDK=\"jdk11\" GATE=\"build,test\"", fails by timeout:
>>>> 
>>>> Test testErrnoCallback(com.oracle.truffle.nfi.test.ErrnoNFITest) not
>>>> finished after 249 ms
>>>> 
>>>> for all pull requests.
>>>> 
>>>> Is there any workaround/solution for this problem?
>>> 
>>> I think the issue is actually a compilation error caused by the preceding test
>>> com.oracle.truffle.sl.test.SLDebugDirectTest. I've opened an internal ticket
>>> for this and hope it will be investigated soon. Can you please let me know if
>>> this fails for you when JAVA_HOME points to JDK11:
>>> 
>>> mx unittest -Dgraal.TruffleBackgroundCompilation=false
>>> -Dgraal.TruffleCompileImmediately=true -Dgraal.TraceTruffleCompilation=false
>>> com.oracle.truffle.sl.test.SLDebugDirectTest
>>> 
>> 
>> this is maybe a different bug but i also had the same kind of issue with latest
>> jdk 11 (b22),
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__travis-2Dci.org_forax_exotic_jobs_404348683&d=DwIFaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=BmNY5KuefACTr_P43s8fXOXgNDkDiqlviyafeiVaP18&m=fbdeH0MKVtcRhPTiuJVQpQhRJkri9lOVsGDzXQE4aA8&s=UGeDId7vPADJKV0Wuo4VqJJFFrJqaUoQSz3T19HevCc&e=
>> (note that while these are perf tests, the perf tests are using c2, only the VM
>> that runs the tester is using Graal)
>> 
>> the VM has finished to run but something is holding it to exit.
> 
> Thanks for the suggestion but I think it's a different issue. In the failing
> Travis test, we have a combination of Truffle compilation being done on
> background threads and the option TrufflePerformanceWarningsAreFatal=true. So a
> compilation triggered by an earlier unittest can fail and interrupt monitoring
> of a later test while the VM is exiting.
> 
> -Doug