| From: | Jeremy Whiting <jwhiting(at)redhat(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Resource lookup timeout causes Travis IC to fail test. |
| Date: | 2015-05-13 08:01:46 |
| Message-ID: | 555304EA.2000208@redhat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Hi Dave,
This has been fixed.
https://github.com/pgjdbc/pgjdbc/pull/284
Jeremy
On 01/05/15 15:51, Dave Cramer wrote:
> If you can fix it yes.
>
> Many of the Travis CI failures are false
>
> Dave Cramer
>
> dave.cramer(at)credativ(dot)ca
> http://www.credativ.ca
>
> On 1 May 2015 at 09:38, Jeremy Whiting <jwhiting(at)redhat(dot)com
> <mailto:jwhiting(at)redhat(dot)com>> wrote:
>
> Hi,
> Today the Travic CI system failed a test. It looks like the DTD
> lookup
> failed. You can see the failed test for 307.12
>
> https://travis-ci.org/pgjdbc/pgjdbc/builds/60815064
>
> Will it be useful if I created a PR with an XML catalog
> containing the
> resource to enable local resolution ? It would mean false positives of
> this nature do not crop up again.
>
> Regards,
> Jeremy
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org
> <mailto:pgsql-jdbc(at)postgresql(dot)org>)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
>
--
Jeremy Whiting
Senior Software Engineer, JBoss Performance Team
Red Hat
------------------------------------------------------------
Registered Address: RED HAT UK LIMITED, 64 Baker Street, 4th Floor, Paddington. London. United Kingdom W1U 7DF
Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (US), Charles Peters (US), Matt Parson (US) and Michael O'Neill(Ireland)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Lazarević | 2015-05-13 08:53:59 | Can't connect to DB using GSS(Kerberos) auth |
| Previous Message | Alexis Meneses | 2015-05-11 21:05:52 | Re: BUG on postgresql-9.4-1201-jdbc41 ... |