Download
Browse source Changelog
Documentation
Project   Bug Bounty   Help us   Known bugs   TODO Protocols   CA bundle   HTTP Cookies   HTTP/2   SSL Certs Releases   Security   Version numbers   Vulnerabilities curl tool   man page   Tutorial   HTTP scripting Who and Why
libcurl
ABI API Competitors Examples Features Mailing list Related libs Using libcurl Tutorial Testimonials
Get Help
curl-library curl-users Mailing lists Book: Everything curl Video presentations Report a bug Paid support
Development
Autobuilds Code Style Contribute Deprecate Internals Release Notes Release Procedure Roadmap Run Tests Security Process Specifications Test curl
News
Changelog Release table
curl / Mailing Lists / curl-library / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: ARM test 323 failure

From: Jeffrey Walton via curl-library <curl-library_at_cool.haxx.se>
Date: Mon, 21 Oct 2019 05:25:13 -0400

On Mon, Oct 21, 2019 at 5:13 AM Jeffrey Walton <noloader_at_gmail.com> wrote:
>
> On Mon, Oct 21, 2019 at 3:13 AM Daniel Stenberg <daniel_at_haxx.se> wrote:
> >
> > On Sat, 19 Oct 2019, Jeffrey Walton wrote:
> >
> > >> The sad results is however that on this machine test 323 seems to work just
> > >> fine even if I try to repeat it mant times! :-O
> > >>
> > >> The particular machine I used features a "AArch64 Processor rev 1
> > >> (aarch64)" in a board called "APM X-Gene Mustang".
> > >
> > > The other ones to try is GCC117 or GCC118. They are roughly the same Aarch64
> > > machines, but with CRC+Crypto. The Mustang boards lack the cpu features.
> >
> > I've now also ran test 323 on gcc117 and the test works fine for me there too.
> >
> > I noticed however that if I try to use valgrind for the tests on this machine,
> > not a single TLS-related test seems to work. Calling RAND_status() in the
> > OpenSSL 1.1.0l version triggers an 'Illegal instruction' error which sounds
> > pretty bad! =(
>
> That is probably either (1) Valgrind missing a VEX decode for an
> instruction, or (2) OpenSSL performing a feature probe.
>
> I used to encounter (1) all the time especially when compiling with
> -march=native. For (2), feature probes are business as usual. See the
> SIGILL topic at https://www.openssl.org/docs/faq.html#PROG .
>
> For (1) you stop using Valgrind and file a bug report. (Or you build
> Valgrind from sources hoping the VEX has been updated). For (2) you
> ignore it.
>
> > On gcc115 I could run 323 even with valgrind, but it sports OpenSSL 1.0.1f
> > which I have no idea if it makes a difference or not.
> >
> > So, to sum it up: I still have no idea why test 323 fails on travis arm64!
>
> Yeah, I would not worry too much about it until you determine the
> cause. It could be something wonky like a bad shell interaction or
> unexpected iptables result.

I probably should have mentioned you have two choices here. First is
to move the 323 test to 'allowed_failures:' This keeps your test
result green and the status as passing.

The second is to SSH into the remote console using Debug mode. It gets
you shell access to the VM. Also see
https://docs.travis-ci.com/user/running-build-in-debug-mode/.

Jeff
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2019-10-21