Baseline issues resolved in 1795540. Retrying the build to see what errors
out next.
On Thu, May 18, 2017 at 10:15 AM, Daniel Klco wrote:
> I just ran mvn clean install from a fresh clone of the trunk branch in
> GitHub and am seeing baseline issues and integration test failures in
> sightly. It
I just ran mvn clean install from a fresh clone of the trunk branch in
GitHub and am seeing baseline issues and integration test failures in
sightly. It did seem to resolve the rat issues. Let me look to see if I can
resolve the baseline issue...
On Thu, May 18, 2017 at 9:44 AM, Daniel Klco wrote
Ah, @Radu, the issue I'm having is with launchpad/integration-tests. I can
confirm running mvn clean verify from launchpad/testing works fine.
On Thu, May 18, 2017 at 9:34 AM, Radu Cotescu wrote:
> Hi Daniel,
>
> What are you trying to run and how?
>
> I get this result when running mvn clean ve
I performed a git clean -f and git clean -d, I would assume that should
return me to a good state but let me try a clean clone off GitHub.
On Thu, May 18, 2017 at 9:41 AM, Carsten Ziegeler
wrote:
> Daniel Klco wrote
> > Hm, I'm trying to do a reactor build on 1795515 and am getting rat
> errors,
Daniel Klco wrote
> Hm, I'm trying to do a reactor build on 1795515 and am getting rat errors,
> baseline errors and integration testing errors in
> bundles/scripting/sightly/testing. Still trying to get a successful reactor
> build...
>
At some point we moved modules around, so you might have st
Hi Daniel,
What are you trying to run and how?
I get this result when running mvn clean verify in launchpad/testing: Tests
run: 570, Failures: 0, Errors: 0, Skipped: 2
Cheers,
Radu
On Thu, 18 May 2017 at 15:19 Daniel Klco wrote:
> Hm, I'm trying to do a reactor build on 1795515 and am getting
Hm, I'm trying to do a reactor build on 1795515 and am getting rat errors,
baseline errors and integration testing errors in
bundles/scripting/sightly/testing. Still trying to get a successful reactor
build...
On Thu, May 18, 2017 at 2:27 AM, Bertrand Delacretaz wrote:
> On Thu, May 18, 2017 at
Hi Dan,
On Wed, 2017-05-17 at 23:00 -0400, Daniel Klco wrote:
> I don't feel like this was happening until recently. Perhaps
> introduced
> with the recent Commons Scheduler? You can reproduce the issue off
> the
> trunk by running the launchpad integration tests as such:
>
> mvn test -Dtest=**/i
On Thu, May 18, 2017 at 8:14 AM, Carsten Ziegeler wrote:
> ...I did a full build several times now and I don't get any
> test failures at all...
Same here, full build at revision 1795477 works.
-Bertrand
Interesting, I did a full build several times now and I don't get any
test failures at all.
I doubt that it's related to commons scheduler as this is still on the
old version 2.5.2
Regards
Carsten
Daniel Klco wrote
> Hey All,
>
> I'm seeing 5 launchpad test errors on the current trunk:
>
> Fai
Hey All,
I'm seeing 5 launchpad test errors on the current trunk:
Failed tests:
FullTextIndexingTest.testUploadedPdfIsIndexed:117 RetryLoop failed,
condition is false after 45 seconds: A document containing 'Excepteur' is
found under /tmp/test-FullTextIndexingTest
FullTextIndexingTest.testU
11 matches
Mail list logo
