jenkins.typesafe.com can run through the tests.
(No description)
Leave a comment
on 2012-07-02 09:06 *
By Patrik Nordwall
Also note that the jobs at scalable1 started to fail with
java.lang.OutOfMemoryError: PermGen
Could that be related to latest commits? Leak? Or should I just increase MaxPermSize?
which was -XX:MaxPermSize=256M
java.lang.OutOfMemoryError: PermGen
Could that be related to latest commits? Leak? Or should I just increase MaxPermSize?
which was -XX:MaxPermSize=256M
for the record, here’s how I generated the diff for that jenkins run: take the “Revision” from above and compare it to its parent on master (e.g. looking at the network graph) with a URL like this
https://github.com/akka/akka/compare/b684eb1...34b05e55
https://github.com/akka/akka/compare/b684eb1...34b05e55
I ran the tests manually, and they took 1698s to compile and 2563s to run, which is obviously more than 1 hour in total. Watching it run (and checking the test timings) nothing sticks out, it was just dead slow.
Thread dumps show that ActorRefSpec, ActorModelSpec (for BalancingDispatcher if I’m not mistaken) and SupervisorMiscSpec did not terminate their actor systems.
from Thread Dump:
So PermGen is actually full, though I did not see any related error messages printed.
Thread dumps show that ActorRefSpec, ActorModelSpec (for BalancingDispatcher if I’m not mistaken) and SupervisorMiscSpec did not terminate their actor systems.
from Thread Dump:
Heap
PSYoungGen total 299456K, used 105030K [0x00000000eaab0000, 0x0000000100000000, 0x0000000100000000)
eden space 254080K, 32% used [0x00000000eaab0000,0x00000000efb27ca8,0x00000000fa2d0000)
from space 45376K, 49% used [0x00000000fa2d0000,0x00000000fb8e9c38,0x00000000fcf20000)
to space 44736K, 0% used [0x00000000fd450000,0x00000000fd450000,0x0000000100000000)
PSOldGen total 578688K, used 387836K [0x00000000c0000000, 0x00000000e3520000, 0x00000000eaab0000)
object space 578688K, 67% used [0x00000000c0000000,0x00000000d7abf0e0,0x00000000e3520000)
PSPermGen total 235840K, used 235830K [0x00000000b0000000, 0x00000000be650000, 0x00000000c0000000)
object space 235840K, 99% used [0x00000000b0000000,0x00000000be64db70,0x00000000be650000)
So PermGen is actually full, though I did not see any related error messages printed.
okay, thanks to Paul who fixed it by re-setting the machine’s date it should be fine: running the tests manually worked again. more background at
http://blog.wpkg.org/2012/07/01/java-leap-second-bug-30-june-1-july-2012-fix/
http://blog.wpkg.org/2012/07/01/java-leap-second-bug-30-june-1-july-2012-fix/
Updating tickets (#2186, #2187, #2189, #2192, #2196, #2197, #2198, #2200, #2203, #2208, #2212, #2217, #2218, #2221, #2224, #2225, #2226, #2227, #2228, #2232, #2236, #2237, #2247, #2248, #2255, #2257, #2260, #2262, #2268, #2269, #2272, #2276, #2285, #2288, #2292, #2294, #2295, #2298, #2301, #2302, #2312, #2315, #2318, #2319, #2332, #2333, #2335, #2337, #2340, #2341, #2342, #2345)