houshengbo edited a comment on issue #4357: Test cases with consistent failures in Jenkins pipeline build URL: https://github.com/apache/incubator-openwhisk/issues/4357#issuecomment-478008918 @sven-lange-last @chetanmeh Is this something we can fix with our test code instead of system configuration? Here is detailed error message: ``` org.apache.openwhisk.core.limits.ActionLimitsTests > Action limits should be aborted when exceeding its memory limits STANDARD_OUT check failed for activation 6f6e0aa9aa004c29ae0aa9aa00ac2967: {"activationId":"6f6e0aa9aa004c29ae0aa9aa00ac2967","annotations":[{"key":"path","value":"guest/TestNodeJsMemoryExceeding"},{"key":"waitTime","value":3210},{"key":"kind","value":"nodejs:6"},{"key":"timeout","value":false},{"key":"limits","value":{"concurrency":1,"logs":10,"memory":128,"timeout":60000}},{"key":"initTime","value":154}],"duration":4334,"end":1553871361722,"logs":["2019-03-29T14:55:57.548627106Z stdout: helloEatMemory: memory 256MB","2019-03-29T14:55:57.55555352Z stdout: helloEatMemory: memoryInB=268435456, memoryInPages=65536","2019-03-29T14:55:57.555578446Z stdout: helloEatMemory: pagesPerBlock=8, blockSizeInB=32768, memoryInBlocks=8192","2019-03-29T14:56:00.910102376Z stdout: helloEatMemory: blocks.length=8192","2019-03-29T14:56:00.910250839Z stdout: helloEatMemory: completed allocating memory","2019-03-29T14:56:00.945215021Z stdout: { rss: 123826176,","2019-03-29T14:56:00.945254206Z stdout: heapTotal: 21004288,","2019-03-29T14:56:00.945268176Z stdout: heapUsed: 10337800,","2019-03-29T14:56:00.945276636Z stdout: external: 268452540 }"],"name":"TestNodeJsMemoryExceeding","namespace":"guest","publish":false,"response":{"result":{"msg":"OK, buffer of size 256 MB has been filled."},"status":"success","success":true},"start":1553871357388,"subject":"guest","version":"0.0.1"} Exception occurred during test execution: java.util.NoSuchElementException: key not found: error ```
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
