ftbfs using JamVM

Bug #796544 reported by Matthias Klose
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jetty (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: jetty

http://people.canonical.com/~lamont/jamvm/logs/jetty_6.1.24-6-armel-20110611-0221

    [junit] Testcase: testRecycledReaders took 0.249 sec
    [junit] Testsuite: org.mortbay.jetty.CheckReverseProxyHeadersTest
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.454 sec
    [junit] ------------- Standard Error -----------------
    [junit] SLF4J: Class path contains multiple SLF4J bindings.
    [junit] SLF4J: Found binding in [jar:file:/usr/share/java/slf4j-simple.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    [junit] SLF4J: Found binding in [jar:file:/usr/share/java/slf4j-simple-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
    [junit] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
    [junit] 4 [main] INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger(org.mortbay.log) via org.mortbay.log.Slf4jLog
    [junit] 6 [main] INFO org.mortbay.log - jetty-6.1.x
    [junit] 35 [main] INFO org.mortbay.log - Started LocalConnector@0.0.0.0:1
    [junit] 188 [main] INFO org.mortbay.log - Stopped LocalConnector@0.0.0.0:1
    [junit] 191 [main] INFO org.mortbay.log - jetty-6.1.x
    [junit] 192 [main] INFO org.mortbay.log - Started LocalConnector@0.0.0.0:1
    [junit] 198 [main] INFO org.mortbay.log - Stopped LocalConnector@0.0.0.0:1
    [junit] 301 [main] INFO org.mortbay.log - jetty-6.1.x
    [junit] 302 [main] INFO org.mortbay.log - Started LocalConnector@0.0.0.0:1
    [junit] 307 [main] INFO org.mortbay.log - Stopped LocalConnector@0.0.0.0:1
    [junit] ------------- ---------------- ---------------
    [junit]
    [junit] Testcase: testCheckReverseProxyHeaders took 0.452 sec
    [junit] Testsuite: org.mortbay.jetty.EncodedHttpURITest
    [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.014 sec
    [junit]
    [junit] Testcase: testNonURIAscii took 0.013 sec
    [junit] Testsuite: org.mortbay.jetty.HttpConnectionTest
*** glibc detected *** /usr/lib/jvm/default-java/bin/java: double free or corruption (out): 0x53beed48 ***
Aborted
make: *** [debian/stamp-ant-build] Error 134
dpkg-buildpackage: error: debian/rules build gave error exit status 2

Tags: armel jamvm
Matthias Klose (doko)
Changed in jetty (Ubuntu):
importance: Undecided → High
Revision history for this message
Xerxes Rånby (xranby) wrote :

jetty builds and passed all tests on armel using JamVM from the openjdk-6 6b23~pre8-1ubuntu1 package.
...
    [junit] Testsuite: org.mortbay.jetty.HttpConnectionTest
    [junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 2.684 sec
...
full test log attached.

Changed in jetty (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.