jeantil commented on PR #2883: URL: https://github.com/apache/james-project/pull/2883#issuecomment-3638994147
:thinking: i tried several things thinking the cache was somehow broken, but I'm starting to think that the tests are indeed broken. the tests in [build 6](https://develocity.apache.org/s/buofvjzgva7t2/tests/goal/org.apache.james:memory-jmap-rfc-8621-integration-tests:surefire:test@default-test/details/org.apache.james.jmap.rfc8621.memory.MemoryEmailGetMethodTest/useDefaultPropertiesWhenNone?expanded-stacktrace=WyIwIl0&top-execution=3) are mostly broken on ``` Different value found in node "methodResponses[0][1].list[0].htmlBody[0].charset", expected: <"utf-8"> but was: <"UTF-8">. Different value found in node "methodResponses[0][1].list[0].textBody[0].charset", expected: <"utf-8"> but was: <"UTF-8">. ``` After pushing a commit to force a compilation in the contract (visibile in goal execution of the [build 8](https://develocity.apache.org/s/nkyy4vdenla5i/timeline?cacheability=cacheable&hide-timeline&outcome=success,failed&sort=longest)) and the in memory test suite (test-compile visible in the goal executions of [build 9](https://develocity.apache.org/s/xpkj4rrwlzxyq/timeline?cacheability=cacheable&hide-timeline&outcome=success,failed&sort=longest) the same tests keep failing suggesting that the build cache is not the cause. Interestingly on my linux laptop some other tests are broken for a different reason when run in intellij ``` Different value found in node "methodResponses[0][1].parsed.1_3.bodyValues.2.value", Expected :"test body\r\n" Actual :"test body\n" ``` or ``` org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a Lambda expression in org.apache.james.jmap.rfc8621.contract.EmailGetMethodContract JSON documents are different: Different value found in node "methodResponses[0][1].list[0].size", Expected :1011 Actual :970 ``` which is most likely linked to all the extra `\n` in the payload. I'm unfamiliar with the JMAP specification, there is no README in these folder providing specific instructions on how to run these tests so I have no idea if the problem is that the test harness is too strict, if there is some missing configuration or if there is a bug in the memoy implementation possibly an environment specific issue ? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
