Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] CI passes for soc.git!!!
Date: Mon, 6 Apr 2020 12:07:21 +0100
Message-ID: <CAPweEDyoA3Om+dtOpsEnCnSdHFPHBS6E3SA_gVTwHfTFH8D=1w@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6UgDvO7LiH9BGju77=BFQfEHVuW=SdrAUvMD7w-V_tMw@mail.gmail.com>

On Mon, Apr 6, 2020 at 2:36 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Sun, Apr 5, 2020 at 5:44 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> >
> > On Sun, Apr 5, 2020 at 5:17 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > >
> > > I pushed a new branch with my changes since basically everything is
> > > changed and I didn't split my commits up very well.
> > > On my computer, out of 234 tests, there are 4 errors and 1 failure.
> > >
> > > https://git.libre-riscv.org/?p=soc.git;a=commitdiff;h=refs/heads/fix-tests
> >
> > better url:
> > https://git.libre-riscv.org/?p=soc.git;a=tree;h=refs/heads/fix-tests;hb=refs/heads/fix-tests

ah.  just noticed.  i really can't stand branches.  they quickly
become an absolute nuisance, losing work, stopping (necessary)
communication and isolating the people who work on them from
absolutely everyone else.

working on the same branch requires that people communicate effectively.

> CI passes!!!

hurrah :)

> https://salsa.debian.org/Kazan-team/soc/-/jobs/649686
>
> I added @unittest.skip() to test_iq, Luke or whoever can fix that test.

can you please merge what you did (and work in master in future unless
there's a really *really* compelling and critical reason for doing
so)?

thx jacob.

l.

_______________________________________________
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: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  0:17 [libre-riscv-dev] added CI to soc.git as well as attempting to fix all tests Jacob Lifshay
2020-04-06  0:44 ` Jacob Lifshay
2020-04-06  1:36   ` [libre-riscv-dev] CI passes for soc.git!!! Jacob Lifshay
2020-04-06 11:07     ` Luke Kenneth Casson Leighton [this message]
2020-04-06 14:37       ` Jacob Lifshay
2020-04-06 17:12         ` Luke Kenneth Casson Leighton
2020-04-06 19:15           ` Jacob Lifshay
2020-04-06 20:34             ` Luke Kenneth Casson Leighton
2020-04-07  0:07               ` Jacob Lifshay
2020-04-07  0:22                 ` Luke Kenneth Casson Leighton
2020-04-06 10:36   ` [libre-riscv-dev] added CI to soc.git as well as attempting to fix all tests 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='CAPweEDyoA3Om+dtOpsEnCnSdHFPHBS6E3SA_gVTwHfTFH8D=1w@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --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