executes both, jackrabbit and oak tests.
individual targets can be specified with {{-Ptest-oak}} or {{-Ptest-jackrabbit}}
> Failing tests when building vault-core with -Doak=true
> --
>
> Key: JCRVLT-293
>
. You probably should
update.
> Failing tests when building vault-core with -Doak=true
> --
>
> Key: JCRVLT-293
> URL: https://issues.apache.org/jira/browse/JCRVLT-293
> Project: Ja
[
https://issues.apache.org/jira/browse/JCRVLT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16495044#comment-16495044
]
angela commented on JCRVLT-293:
---
[~reschke], i was using 1.8.0_40.
> Failing tests when building va
for JCRVLT-294, the tests pass for me.
> Failing tests when building vault-core with -Doak=true
> --
>
> Key: JCRVLT-293
> URL: https://issues.apache.org/jira/browse/JCRVLT-293
> P
lt;<< FAILURE!
java.lang.AssertionError
at
org.apache.jackrabbit.vault.fs.io.DocViewFormatTest.setup(DocViewFormatTest.java:48)
testFormatting(org.apache.jackrabbit.vault.fs.io.DocViewFormatTest) Time
elapsed: 0.016 s <<< ERROR!
java.lang.NullPointerException
at
org.apache.jackrabbit.vault.fs.io.DocViewFormatTest.tearDown(Do
[~anchela] reported.
> Failing tests when building vault-core with -Doak=true
> --
>
> Key: JCRVLT-293
> URL: https://issues.apache.org/jira/browse/JCRVLT-293
> Project: Jackrabbit FileVaul
[
https://issues.apache.org/jira/browse/JCRVLT-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16494662#comment-16494662
]
Tobias Bocanegra commented on JCRVLT-293:
-
which jdk version ?
> Failing tests when build
ZipEntry:736 »
NoSuchField xdos...
{code}
is this expected or am i missing something?
> Failing tests when building vault-core with -Doak=true
> --
>
> Key: JCRVLT-293
> URL: https://issues.apache
angela created JCRVLT-293:
-
Summary: Failing tests when building vault-core with -Doak=true
Key: JCRVLT-293
URL: https://issues.apache.org/jira/browse/JCRVLT-293
Project: Jackrabbit FileVault
Issue
my fault, I¹m looking into it now
On 17/08/15 12:02, Davide Giannella dav...@apache.org wrote:
Hello team,
trying to release Oak 1.3.4 but it's constantly failing on my local.
Details can be found here
https://issues.apache.org/jira/secure/attachment/12750782/oak-1.3.4-failin
g-1439805620.log
Hello team,
trying to release Oak 1.3.4 but it's constantly failing on my local.
Details can be found here
https://issues.apache.org/jira/secure/attachment/12750782/oak-1.3.4-failing-1439805620.log
looking into it but if you know the answer ping me please.
Davide
On 17/08/2015 12:21, Stefan Egli wrote:
my fault, I¹m looking into it now
Thanks Stefan for the cooperation.
However the build is still blocked as there are some pedantic issues I
can't manage to clear.
For some reasons even if I tell rat-pluing to ignore files in many ways
it's ignoring my
Hello everyone,
I think all of us is aware of those but I have a fairly consistent
failing test (first one at the end) and a more randomly failing one.
Did a pull from upstream this morning as usual.
While the second is randomly failing and not really blocking the build,
the first one succeed
Hi Davide,
I'm looking into the Solr one.
Regards,
Tommaso
2014-03-31 10:55 GMT+02:00 Davide Giannella giannella.dav...@gmail.com:
Hello everyone,
I think all of us is aware of those but I have a fairly consistent
failing test (first one at the end) and a more randomly failing one.
Did
Hi,
I have a test failing on the DOCUMENT_JDBC impl only (OAK-1472).
Following the example from OAK-1488, I've enabled the test and added a
clause to skip in the case of the above fixture.
As far I can tell, this is not related to the test, so there's nothing I
can do here, unless there's more
hi julian
Julian Reschke wrote:
- is anybody looking at these?
- do we have JIRA issues (except JCR-1293 which seems to be something
different)?
i have been looking at the problem described in
JCR-1293 and i assume that all the occasional
failing tests are a result of the same problem
Hi,
I can't help noticing that we currently seem to have *various* test
cases that occasionally fail. This is very disturbing, because I'm a
believer in not checking in new code until tests pass. With the current
failures it's very hard to be sure that a change is good, and I fear
that the
as known issues in the 1.4 release
notes.
- do we have JIRA issues (except JCR-1293 which seems to be something
different)?
Not that I know of. We should add a bug report about the failing tests
after which it's OK to disable the tests as known issues. I'll do that
tomorrow unless anyone beats me
18 matches
Mail list logo
