From: Niek Linnenbank <nieklinnenbank@gmail.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Beniamino Galvani <b.galvani@gmail.com>,
qemu-arm <qemu-arm@nongnu.org>,
Pavel.Dovgaluk@ispras.ru, Cleber Rosa <crosa@redhat.com>,
Willian Rampazzo <willianr@redhat.com>
Subject: Re: [PATCH v2 1/2] tests/acceptance: replace unstable apt.armbian.com URLs for orangepi-pc, cubieboard
Date: Thu, 25 Feb 2021 20:39:42 +0100 [thread overview]
Message-ID: <CAPan3Wp-4Ey+vmMfw2F_yynC_un+byCcYh1U4HuMQYypOJp3GA@mail.gmail.com> (raw)
In-Reply-To: <YDdx9N0Wtv8F47Ka@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 4312 bytes --]
Hi Philippe, Thomas, Daniel,
Thank you all. Then I'll just prepare a new version of the patch that uses
currently working archive.armbian.com links.
Kind regards,
Niek
On Thu, Feb 25, 2021 at 10:46 AM Daniel P. Berrangé <berrange@redhat.com>
wrote:
> On Wed, Feb 24, 2021 at 09:02:51PM +0100, Niek Linnenbank wrote:
> > Hi Philippe, Cleber,
> >
> > On Wed, Feb 24, 2021 at 8:14 PM Cleber Rosa <crosa@redhat.com> wrote:
> >
> > > On Wed, Feb 24, 2021 at 10:12:10AM +0100, Philippe Mathieu-Daudé wrote:
> > > > Hi Niek,
> > > >
> > > > On 2/23/21 11:53 PM, Niek Linnenbank wrote:
> > > > > Currently the automated acceptance tests for the Orange Pi PC and
> > > cubieboard
> > > > > machines are disabled by default. The tests for both machines
> require
> > > artifacts
> > > > > that are stored on the apt.armbian.com domain. Unfortunately,
> some of
> > > these artifacts
> > > > > have been removed from apt.armbian.com and it is uncertain whether
> > > more will be removed.
> > > > >
> > > > > This commit moves the artifacts previously stored on
> apt.armbian.com
> > > to github
> > > > > and retrieves them using the path: '/<machine>/<artifact>'.
> > > > >
> > > > > Signed-off-by: Niek Linnenbank <nieklinnenbank@gmail.com>
> > > > > Reviewed-by: Willian Rampazzo <willianr@redhat.com>
> > > > > Reviewed-by: Cleber Rosa <crosa@redhat.com>
> > > >
> > > > > Tested-by: Cleber Rosa <crosa@redhat.com>
> > > >
> > > > Did Cleber test this new version?
> > > >
> > >
> >
> > You're right, it was the previous version (v1) that Cleber tested using
> my
> > own machine URL's.
> >
> > I was actually not sure whether I should or should not have added the
> > Tested-by/Reviewed-by tags in such scenario.
> > The content had to be changed due to the outcome of our discussion but
> also
> > I thought I don't want to silently drop
> > the tags since Cleber invested his time into it too.
> >
> > What should I do here, next time?
> >
> >
> >
> > >
> > > Nope, and I'm having issues with those URLs. For instance:
> > >
> > > $ curl -L
> > >
> https://github.com/nieklinnenbank/QemuArtifacts/raw/master/cubieboard/linux-image-dev-sunxi_5.75_armhf.deb
> > > version https://git-lfs.github.com/spec/v1
> > > oid
> > > sha256:a4b765c851de76592f55023b1ff4104f7fd29bf90937e6054e0a64fdda56380b
> > > size 20331524
> > >
> > > Looks like it has to do with GitHub's behavior wrt quota.
> > >
> >
> > Indeed. Just this morning I received an e-mail from github with the
> > following text:
> >
> > "[GitHub] Git LFS disabled for nieklinnenbank
> >
> > Git LFS has been disabled on your personal account nieklinnenbank because
> > you’ve exceeded your data plan by at least 150%.
> > Please purchase additional data packs to cover your bandwidth and storage
> > usage:
> >
> > https://github.com/account/billing/data/upgrade
> >
> > Current usage as of 24 Feb 2021 09:49AM UTC:
> >
> > Bandwidth: 1.55 GB / 1 GB (155%)
> > Storage: 0.48 GB / 1 GB (48%)"
> >
> > I wasn't aware of it but it appears that Github has these quota's for the
> > Large File Storage (LFS). I uploaded the files in the git LFS
> > because single files are also limited to 100MiB each on the regular Git
> > repositories.
> >
> > With those strict limits, in my opinion Github isn't really a solution
> > since the bandwidth limit will be reached very quickly. At least for the
> > LFS part that is. I don't know yet if there is any limit for regular
> access.
> >
> > My current ideas:
>
> > - we can try to just update the URLs to armbian that are working now
> > (with the risk of breaking again in the near future). Ive also found this
> > link, which may be more stable:
> > https://archive.armbian.com/orangepipc/archive/
>
> Just do this, as it is the simplest option that gets things working. We
> have already spent far too long talking about the problem instead of
> just fixing the URLs.
>
>
> Regards,
> Daniel
> --
> |: https://berrange.com -o-
> https://www.flickr.com/photos/dberrange :|
> |: https://libvirt.org -o-
> https://fstop138.berrange.com :|
> |: https://entangle-photo.org -o-
> https://www.instagram.com/dberrange :|
>
>
--
Niek Linnenbank
[-- Attachment #2: Type: text/html, Size: 6994 bytes --]
next prev parent reply other threads:[~2021-02-25 19:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 22:53 [PATCH v2 0/2] Allwinner H3 fixes for EMAC and acceptance tests Niek Linnenbank
2021-02-23 22:53 ` [PATCH v2 1/2] tests/acceptance: replace unstable apt.armbian.com URLs for orangepi-pc, cubieboard Niek Linnenbank
2021-02-24 9:12 ` Philippe Mathieu-Daudé
2021-02-24 19:13 ` Cleber Rosa
2021-02-24 20:02 ` Niek Linnenbank
2021-02-24 23:10 ` Philippe Mathieu-Daudé
2021-02-25 5:22 ` Thomas Huth
2021-02-25 9:46 ` Daniel P. Berrangé
2021-02-25 19:39 ` Niek Linnenbank [this message]
2021-02-23 22:53 ` [PATCH v2 2/2] hw/net/allwinner-sun8i-emac: traverse transmit queue using TX_CUR_DESC register value Niek Linnenbank
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=CAPan3Wp-4Ey+vmMfw2F_yynC_un+byCcYh1U4HuMQYypOJp3GA@mail.gmail.com \
--to=nieklinnenbank@gmail.com \
--cc=Pavel.Dovgaluk@ispras.ru \
--cc=b.galvani@gmail.com \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=willianr@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).