From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: "vapier@gentoo.org" <vapier@gentoo.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Recent simulator patches broke many sims
Date: Mon, 25 Mar 2013 07:39:00 -0000 [thread overview]
Message-ID: <514FB2E0.40204@oarcorp.com> (raw)
In-Reply-To: <201303242323.r2ONNS1m027200@ignucius.se.axis.com>
On 3/24/2013 6:23 PM, Hans-Peter Nilsson wrote:
>> From: Joel Sherrill <joel.sherrill@oarcorp.com>
>> Date: Sun, 24 Mar 2013 15:45:27 +0100
>> This came in after I was done email last night. My test
>> run finished overnight with no horribly bad issues. I have no idea
>> what the make check results should be though and they could be
>> because I simply ran "make check" with no board specified and
>> no gcc for the target installed.
> This would be no news to *you*, but for the record:
It's not a surprise. I fairly regularly run the gcc tests for RTEMS
and they need a baseboard specified. I knew binutils didn't. And
assumed (incorrectly) that applied to the simulator and gdb
as well.
> You need a board (make check RUNTESTFLAGS=--target_board=$board
> with e.g. board=cris-sim). All boards are in "recent"
> dejagnu-1.5 IIRC and most in ancient dejagnu-1.4.4. You need
> installed binutils (e.g. in some temp location added to PATH for
> the duration of the test-run) for each sim configuration as
> mentioned. I don't run with target gcc; not needed for the
> level of smoke test I'm after and I guess not for this change
> either.
I will add this to my testing script for RTEMS targets. Is there somewhere
to email these results like gcc?
>> There were some unexpected failures but I don't know what "truth"
>> on that is.
> The truth is in the baseline.
Using 7.5.91 for that. Just got home and the build for that is done.
>> I have saved logs from the test run and will do so with
>> the run on Mike's patch.
>>
>> Starting another test run with Mike's patch.
>>
>> I can put both sets of logs on an ftp server if someone wants to review
>> them. Guidance on what is a bad number of "unexpected failures" on
>> a target is appreciated.
> You compare against a baseline you create without your patches;
> comparing old/new build logs should be sufficient.
>
> Having said all that, I think just a successful *build* of each
> sim would be sufficient here, if your grep can find no
> sockser-specific tests in the target sim test-suites.
OK. I will follow up with a test results email.
> brgds, H-P
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next prev parent reply other threads:[~2013-03-25 2:14 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 0:22 Hans-Peter Nilsson
2013-03-24 0:38 ` Joel Sherrill
2013-03-24 5:39 ` Hans-Peter Nilsson
2013-03-24 5:39 ` Joel Sherrill
2013-03-24 11:04 ` Hans-Peter Nilsson
2013-03-24 2:12 ` Joel Sherrill
2013-03-24 2:35 ` Joel Sherrill
2013-03-24 2:53 ` Hans-Peter Nilsson
2013-03-24 5:22 ` Hans-Peter Nilsson
2013-03-24 5:36 ` Hans-Peter Nilsson
2013-03-24 4:51 ` Hans-Peter Nilsson
2013-03-24 11:33 ` Mike Frysinger
2013-03-25 3:30 ` Joel Sherrill
2013-03-25 3:50 ` Hans-Peter Nilsson
2013-03-25 7:39 ` Joel Sherrill [this message]
2013-03-26 17:49 ` Mike Frysinger
2013-03-26 18:41 ` Hans-Peter Nilsson
2013-03-26 18:43 ` Joel Sherrill
2013-03-26 19:49 ` Mike Frysinger
2013-03-26 20:50 ` Hans-Peter Nilsson
2013-03-26 21:24 ` Mike Frysinger
2013-03-27 1:39 ` Hans-Peter Nilsson
2013-03-27 9:13 ` Mike Frysinger
2013-03-26 18:56 ` Mike Frysinger
2013-03-27 8:47 ` Joel Brobecker
2013-03-27 8:50 ` Hans-Peter Nilsson
2013-03-27 18:38 ` Joel Sherrill
2013-03-27 19:01 ` Joel Brobecker
2013-03-27 19:43 ` Joel Brobecker
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=514FB2E0.40204@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb-patches@sourceware.org \
--cc=hans-peter.nilsson@axis.com \
--cc=vapier@gentoo.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