Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Samuel Falvo II <sam.falvo@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] libre-riscv-dev Digest, Vol 23, Issue 18
Date: Fri, 10 Jul 2020 19:09:30 -0700
Message-ID: <CAEz=so=eHaD43DHWdAP+9qcwxXfsRE6HxKRVX0FWd9amfjAW1w@mail.gmail.com> (raw)
In-Reply-To: <mailman.5.1594421940.8323.libre-riscv-dev@lists.libre-riscv.org>

On Fri, Jul 10, 2020 at 3:59 PM
<libre-riscv-dev-request@lists.libre-riscv.org> wrote:
> On Friday, July 10, 2020, Luke Kenneth Casson Leighton <lkcl@lkcl.net>
> the main one you want is soc/fu/spr/test/test_pipe_caller.py

This test seems to pass if I run it manually; I get a too many open
files error if I run it from make test.  But you did say that that way
lies the path to the dark-side, so I'll just stick with manual
invocation for now.

I guess my next question is to better understand the nature of the
formal tests you want me to write.  I can try to write a set of
"obvious" formal properties for the main_stage.py module; but, it'd be
better if I had a clearer understanding of the intention of the main
stage module.  Is here a good place to discuss the scope for bug 418
or should we move this discussion to the bug?

BTW, I re-asserted to Mailman that I did *not* want to be on digest
mode.  Mailman presents my configuration to me with it turned off
(screenshot available upon request); I'm not sure why it continues to
keep me in digest mode.

-- 
Samuel A. Falvo II

_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

       reply index

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.5.1594421940.8323.libre-riscv-dev@lists.libre-riscv.org>
2020-07-11  2:09 ` Samuel Falvo II [this message]
2020-07-11  9:02   ` Luke Kenneth Casson Leighton

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='CAEz=so=eHaD43DHWdAP+9qcwxXfsRE6HxKRVX0FWd9amfjAW1w@mail.gmail.com' \
    --to=sam.falvo@gmail.com \
    --cc=libre-riscv-dev@lists.libre-riscv.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

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git