On Sun, Jul 08, 2018 at 04:18:31PM -0400, Roberto C. Sánchez wrote: > On Thu, Jul 05, 2018 at 09:40:40AM -0400, Roberto C. Sánchez wrote: > > On Tue, Jul 03, 2018 at 11:40:05PM +0200, Emmanuel Bourg wrote: > > > Le 30/06/2018 à 20:09, Roberto C. Sánchez a écrit : > > > > > > > I would very much appreciate your guidance on this so that I can get > > > > tomcat8 in jessie updated. > > > > > > Hi Roberto, > > > > > > Thank a lot for helping with the Tomcat maintenance. The error probably > > > comes from an expired test certificate or a change in OpenSSL. Try > > > building the package locally without pbuilder and inspect the test logs > > > generated in the output directory. You should get a good indication of > > > the cause of this error. Note that you can build the package and run > > > only one test by adding -Dtest.name=**/TestWebSocketFrameClientSSL* > > > after the "ant test" invocation in debian/rules. That should speed up > > > your investigations. > > > > > Hi Emmanuel, > > > > The SSL certificate expiration was exactly the problem. I have updated > > them from the latest available in the upstream sources and am presently > > running another build. > > > It turns out that build ended up failing. (I meant to ping back as soon > as it had completed, but I did not get around to it.) I tried a build > of the current version (8.0.14-1+deb8u11) with test SSL certificates > updated from upstream, and that build failed as well. A total of 12 > unit tests failed. > > This makes me wonder if I am missing something. I can understand the > SSL certificate expiry preventing a rebuild of the package. But I > cannot understand how the build would fail otherwise. I will dig into > the test failures tonight, but I would appreciate any thoughts on what > might be going wrong. Hello Roberto, If you're still running into build failures, I would be interested in taking a look. Could you push your branch to Salsa when you have a chance? Cheers, tony
Attachment:
signature.asc
Description: PGP signature