From commits-return-7273-archive-asf-public=cust-asf.ponee.io@fineract.apache.org Thu Jan 23 18:30:52 2020 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 3CB6E18025F for ; Thu, 23 Jan 2020 19:30:52 +0100 (CET) Received: (qmail 6450 invoked by uid 500); 23 Jan 2020 18:30:51 -0000 Mailing-List: contact commits-help@fineract.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.apache.org Delivered-To: mailing list commits@fineract.apache.org Received: (qmail 6436 invoked by uid 99); 23 Jan 2020 18:30:51 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jan 2020 18:30:51 +0000 From: GitBox To: commits@fineract.apache.org Subject: [GitHub] [fineract] vorburger commented on issue #680: Fixing bulk import integration test failures Message-ID: <157980425156.6341.16269211876666187106.gitbox@gitbox.apache.org> References: In-Reply-To: Date: Thu, 23 Jan 2020 18:30:51 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit vorburger commented on issue #680: Fixing bulk import integration test failures URL: https://github.com/apache/fineract/pull/680#issuecomment-577812669 > isn't an Assertion statement at line 143 nor indeed the only assertion around there is the `Assert.assertNotNull(importDocumentId);` which is in line 145 not 143... I would just assume it's that one that's failing here (just because there is no other one), and not loose too much sleep about that (slight) line number mismatch. I can't quite explain it either, but if you made me guess, I would suspect it may be related to and may just have been solved by (my) recent #688 re. CR/LF... you could rebase to the latest develop, to check. If it's still a little bit off, just assume it's that one, and try to fix that. > need to have the complete stacktrace of the AssertionError. Travis unfortunately doesn't let you see it, what we do is locally reproduce and debug. > I'm able recreate this locally on my end. But are you really running `./gradlew integrationTest` (not just `test` or `build`) ? I'm pretty sure you should locally hit it as well... unless this is some mess due to time zone or something, but that seems quite unlikely. ---------------------------------------------------------------- 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: users@infra.apache.org With regards, Apache Git Services