Open line-o opened 2 years ago
I see a different error in exist/extensions/modules/expathrepo
, but that one consistently. mvn clean test -fae
:
<testcase name="" classname="org.exist.repo.PackageTriggerTest" time="2.032">
<error type="java.io.IOException">
<![CDATA[java.io.IOException: storeDocument received a null InputStream when trying to store a Binary Document at org.exist.repo.PackageTriggerTest.setup(PackageTriggerTest.java:81)]]>
</error>
</testcase>
mvn -v
Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/homebrew/Cellar/maven/3.8.5/libexec
Java version: 1.8.0_322, vendor: Azul Systems, Inc., runtime: /Library/Java/JavaVirtualMachines/zulu-8.jdk/Contents/Home/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "mac os x", version: "12.3", arch: "aarch64", family: "mac"
funnily : mvn clean verify -fae
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 10:05 min
[INFO] Finished at: 2022-03-22T11:42:00+01:00
[INFO] ------------------------------------------------------------------------
@line-o looks like joe had the same error on ci https://github.com/eXist-db/exist/pull/4269#issuecomment-1068375035
(I didn't experience it myself - I just saw it in the GitHub Actions CI error logs.)
so repeated the same with mvn clean package -Dmac.signing=false -Ddocker=false -DskipTests -Ddependency-check.skip=true -P '!installer'
:
…
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:06 min
[INFO] Finished at: 2022-03-23T10:38:49+01:00
[INFO] ------------------------------------------------------------------------
the difference in the expathrepo
test failing with mvn test
while passing with mvn verify
remains
to sum up,
test
but pass when executed as verify
either our maven config needs some tweaks, or the test needs to be executed with some dependency resolved in the verify phase onlyToday, with support from @duncdrum I was able to have a full successful test run on M1. Since we saw the above issue also in CI, I guess this is not processor architecture related. I will change the title of this issue.
What I did in order to get to a running setup was:
git clean -dfX
mvn package
When running the tests as part of the maven package goal these failures were reported on my machine. update The same issue was now also observed happening in CI by @joewiz
The weird thing is that it seems that the expected values are actually returned based on the output.
Context (please always complete the following information):
Additional context
conf.xml
? none