From: Teodor Dermendzhiev <Teodor.Dermendzhiev@progress.com>
To: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Travis build issue on PR #414
Date: Tue, 10 Apr 2018 14:42:00 -0000 [thread overview]
Message-ID: <SN1PR05MB220850FCA4029CD8C426120398BE0@SN1PR05MB2208.namprd05.prod.outlook.com> (raw)
Hello,
Couple of weeks ago I submitted a PR targetting arm64 support for SIMD types. After I fixed the errors from the Travis builds now it looks like there is a problem there and I am not sure it is related to my changes. Here (https://travis-ci.org/libffi/libffi/builds/364614226) you can see all the builds but one are successful. According to the error log its related to the log's size. It would be great to have some feedback on this. Thank you.
Greetings,
Teodor Dermendzhiev
NativeScript
next reply other threads:[~2018-04-10 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 14:42 Teodor Dermendzhiev [this message]
2018-04-10 15:09 ` Anthony Green
2018-04-11 10:45 ` Anthony Green
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN1PR05MB220850FCA4029CD8C426120398BE0@SN1PR05MB2208.namprd05.prod.outlook.com \
--to=teodor.dermendzhiev@progress.com \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).