linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wbx@uclibc-ng.org (Waldemar Brodkorb)
To: linux-snps-arc@lists.infradead.org
Subject: [uclibc-ng-devel] ARC uClibc-ng testsuite runs empty ?
Date: Wed, 11 Jan 2017 21:48:50 +0100	[thread overview]
Message-ID: <20170111204849.GH1913@waldemar-brodkorb.de> (raw)
In-Reply-To: <f806e391-de89-5636-ab91-d4eb46e4f482@synopsys.com>

Hi Vineet,
Vineet Gupta wrote,

> Hi Waldemar,
> 
> It seems ARC results are no present for recent releases:
> 
> e.g. following is empty:
> http://tests.embedded-test.org/uClibc-ng/1.0.21/REPORT.arcv2.toolchain.uClibc-ng-1.0.21

Toolchain is always empty, it just shows toolchain building runs
fine.
 
> The last good one seems to be
> http://tests.embedded-test.org/uClibc-ng/1.0.19/REPORT.arcv2.libc.uClibc-ng-1.0.19
> 
> Is this due to the init_module/delete_module change which has been reverted after
> 1.0.21

No, the problem is the removal of the testsuite from uClibc-ng.
Now the test suite is compiled as a part of normal applications and 
arc binutils segfaults.

I reported the issue to Alexey last year.
We added your binutils maintainer to the thread.
Yesterday he had again time to reproduce the problem, but there was
some missing information I gave him yesterday.

So may be you can help with this?

It is really blocking any complete regression testing :( 

Sorry for late response, my mailman has disappeared and no
mailinglist mails where sent out for some days.

best regards
 Waldemar

  reply	other threads:[~2017-01-11 20:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 17:53 ARC uClibc-ng testsuite runs empty ? Vineet Gupta
2017-01-11 20:48 ` Waldemar Brodkorb [this message]
2017-01-11 22:26   ` [uclibc-ng-devel] " Vineet Gupta
2017-01-11 22:40     ` Waldemar Brodkorb
2017-01-13 15:06       ` Cupertino Miranda
2017-01-14 19:01         ` Waldemar Brodkorb

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=20170111204849.GH1913@waldemar-brodkorb.de \
    --to=wbx@uclibc-ng.org \
    --cc=linux-snps-arc@lists.infradead.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 NNTP newsgroup(s).