truffle.test.OptimizedCallTargetTest
Christian Humer
christian.humer at gmail.com
Fri Jan 20 16:53:37 UTC 2017
Hi Andrew,
I did not imagine that there could be a platform that compiles so
slowly. OptimizedCallTargetTest as a whole runs in 3.5s locally and it
does hundreds of compilations on my machine.
I pushing your suggested fix.
Cheers,
Christian Humer
On 20.01.2017 17:21:45, "Doug Simon" <doug.simon at oracle.com> wrote:
>Hi Andrew,
>
>We’re looking into why it requires even 10s, let alone 30s. In the mean
>time, you can increase the timeout when running on Aarch64.
>
>-Doug
>
>> On 20 Jan 2017, at 15:46, Andrew Haley <aph at redhat.com> wrote:
>>
>> I've now passed all of the Truffle tests except for one, and that's a
>> timeout waiting for an OSR loop counter to trigger. The test
>>actually
>> takes 17 seconds to run; does anyone mind if I increase the timeout
>> to, say, 30s?
>>
>> Thanks,
>>
>> Andrew.
>>
>>
>> diff --git
>>a/graal/org.graalvm.compiler.truffle.test/src/org/graalvm/compiler/truffle/test/OptimizedCallTargetTest.java
>>b/graal/org.graalvm.compiler.truffle.test/src/org/graalvm/compiler/truffle/test/OptimizedCallTargetTest.java
>> index 8329e17..4a84b70 100644
>> ---
>>a/graal/org.graalvm.compiler.truffle.test/src/org/graalvm/compiler/truffle/test/OptimizedCallTargetTest.java
>> +++
>>b/graal/org.graalvm.compiler.truffle.test/src/org/graalvm/compiler/truffle/test/OptimizedCallTargetTest.java
>> @@ -86,7 +86,7 @@ public class OptimizedCallTargetTest {
>> private static void assertCompiled(OptimizedCallTarget target) {
>> assertNotNull(target);
>> try {
>> - runtime.waitForCompilation(target, 10000);
>> + runtime.waitForCompilation(target, 30_000);
>> } catch (ExecutionException | TimeoutException e) {
>> fail("timeout");
>> }
>
More information about the graal-dev
mailing list