Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Jacob Lifshay <programmerjake@gmail.com>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: [libre-riscv-dev] sorry state of ieee754fpu repo -- CI desperately needed
Date: Fri, 3 Apr 2020 00:04:16 -0700
Message-ID: <CAC2bXD74QdtDc_7=ojaFc0ED4R3SzPGKS2b4s+mjshi-3ph=ag@mail.gmail.com> (raw)

The ieee754fpu repo is filled with tests that don't work because of
stuff like classes and imports being deleted/renamed, along with a few
files that are just syntatically incorrect. I've given up on cleaning
it up and having anything likely to still work by the time I'm done.

Luke, do you want to try to clean it up?

This is something that could have been caught before it descended into
chaos by having CI because it would fail and someone would get an
email when people break stuff, hence why I'm trying to add CI.

Jacob

_______________________________________________
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: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03  7:04 Jacob Lifshay [this message]
2020-04-03 10:24 ` Luke Kenneth Casson Leighton
2020-04-03 10:28   ` N.A.
2020-04-03 10:29   ` Frieder Paape
2020-04-03 10:48     ` Luke Kenneth Casson Leighton
2020-04-03 10:52       ` N.A.
2020-04-03 10:52       ` Frieder Paape
2020-04-03 11:09         ` Luke Kenneth Casson Leighton
2020-04-06  0:59           ` Jacob Lifshay
2020-04-06  1:06             ` Jacob Lifshay
2020-04-06 10:38               ` Luke Kenneth Casson Leighton
2020-04-06 10:39             ` Luke Kenneth Casson Leighton
2020-04-11 15:55             ` Frieder Paape
2020-04-11 16:10               ` Luke Kenneth Casson Leighton
2020-04-12  3:46               ` Jacob Lifshay
2020-04-12  5:44                 ` 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='CAC2bXD74QdtDc_7=ojaFc0ED4R3SzPGKS2b4s+mjshi-3ph=ag@mail.gmail.com' \
    --to=programmerjake@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