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] submitted bugreport to upstream nmigen
Date: Fri, 3 Apr 2020 11:37:55 +0100
Message-ID: <CAPweEDyFfZjD0qRO1qo-JBwnmG4R6FWJ+fOC5Q=an9LVg1_J3w@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD4wCBySE0wT8O=zzH=8edyXw0bmd5LR1bMsYwfqm+TYaQ@mail.gmail.com>

---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

On Fri, Apr 3, 2020 at 5:10 AM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> On Wed, Apr 1, 2020 at 8:03 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> > Rerunning nmutil CI build to find the next errors:
> > https://salsa.debian.org/Kazan-team/nmutil/-/jobs/642930
>
> Fixed the remaining issues with nmutil, ended up adding
> @unittest.skip() to 3 tests.
>
> The CI build passes!

exxcellent, that's really good news.

> https://salsa.debian.org/Kazan-team/nmutil/-/jobs/644343

*pauses*.... ah.  i didn't realise that salsa - an external resource
not archived or under our direct control - had been selected for
creating information (reports) that is critically important to
preserve.

if we are kicked off of salsa or the service is terminated (debian
loses their sponsorship from gitlab) all those reports could be lost.

so we need to do three things:

1. work out how we managed to miss that, when it has been running for
such a long time already.

2. work out how we are going to archive the logs createe by Cl

3. wotk out if there is a way to get backups off of salsa of whatever
databases are being created .

_______________________________________________
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-01  3:21 Jacob Lifshay
2020-04-01 10:16 ` Luke Kenneth Casson Leighton
2020-04-02  3:03   ` Jacob Lifshay
2020-04-02  9:27     ` Luke Kenneth Casson Leighton
2020-04-02 18:19       ` Immanuel, Yehowshua U
2020-04-03  4:10     ` Jacob Lifshay
2020-04-03 10:37       ` Luke Kenneth Casson Leighton [this message]
2020-04-03 17:41         ` Jacob Lifshay
2020-04-03 18:11           ` Luke Kenneth Casson Leighton
2020-04-03 18:26             ` Jacob Lifshay
2020-04-03 19:24               ` Luke Kenneth Casson Leighton
2020-04-03 20:21                 ` Jacob Lifshay
2020-04-03 21:48                   ` Luke Kenneth Casson Leighton
2020-04-04  8:15                     ` Frieder Paape
2020-04-04 11:07                       ` Luke Kenneth Casson Leighton
2020-04-03 20:27                 ` Cole Poirier

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='CAPweEDyFfZjD0qRO1qo-JBwnmG4R6FWJ+fOC5Q=an9LVg1_J3w@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