DPDK CI discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Patrick MacArthur <pmacarth@iol.unh.edu>,
	Jeremy Plsek <jplsek@iol.unh.edu>
Cc: Ali Alnubani <alialnu@mellanox.com>, dpdklab@iol.unh.edu, ci@dpdk.org
Subject: Re: [dpdk-ci] [dpdklab] Re: patchwork REST API patches endpoint 500 error
Date: Sat, 23 Jun 2018 13:54:18 +0200	[thread overview]
Message-ID: <4540187.4GUMsM9S97@xps> (raw)
In-Reply-To: <CABj6NQzjPZ_pbHP78_M9Ynkt3deLzuS0rJ8z8_ga0mi+u6LVWA@mail.gmail.com>

Thanks

One more information: Ali found a disk space issue on the server.
It is now fixed (for some time). We will increase disk space,
and will switch to a new server in few months.


23/06/2018 01:00, Patrick MacArthur:
> Hi, Thomas,
> 
> Just a piece of additional information: I have determined that this appears
> to be an issue with the patch list endpoint in the API (
> http://patches.dpdk.org/api/1.0/patches/), but the patch detail REST API
> endpoint (http://patches.dpdk.org/api/1.0/patches/X/ for a given patch X)
> works fine.
> 
> Based on this, I have been able to work around the issue for now so testing
> of new patch series can resume.
> 
> As for the patch series mbox URLs, we would like to move to using the new
> series support to avoid tracking them by hand, but we have not gotten
> around to it yet.
> 
> Thanks,
> Patrick
> 
> On Fri, Jun 22, 2018 at 11:39 AM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> 
> > 22/06/2018 16:16, Jeremy Plsek:
> > > Hi Thomas,
> > >
> > > The specific URL we are trying to access is:
> > >
> > http://patches.dpdk.org/api/patches/?archived=1&order=-date&project=dpdk&page=1
> > >
> > > Which used to work before.
> > >
> > > I've also noticed 500's every so often on just
> > > http://patches.dpdk.org/api/patches/
> >
> > Indeed it is not working anymore.
> > I don't know what happens.
> >
> > Is it possible to use https://patches.dpdk.org/series/ID/mbox/ ?
> >
> >
> > > On Fri, Jun 22, 2018 at 3:16 AM Thomas Monjalon <thomas@monjalon.net>
> > wrote:
> > >
> > > > 22/06/2018 01:41, Patrick MacArthur:
> > > > > Hi,
> > > > >
> > > > > The Patchwork instance is throwing a 500 error when our scripts try
> > to
> > > > > access the following URL:
> > > > >
> > > > >     http://patches.dpdk.org/api/1.0/patches/
> > > > >
> > > > > Our scripts currently use this endpoint to scrape new patches to be
> > > > applied
> > > > > and tested in our system.
> > > > >
> > > > > Could you please look into this?
> > > >
> > > > You know patchwork has been updated?
> > > >
> > > > Look at this page for the summary of APIs:
> > > >         http://patches.dpdk.org/api/
> > > >
> > > > There is this one:
> > > >         http://patches.dpdk.org/api/patches/
> > > >
> > > > But you should download series with this URL:
> > > >         https://patches.dpdk.org/series/ID/mbox/
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> 
> 

      reply	other threads:[~2018-06-23 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-21 23:41 [dpdk-ci] " Patrick MacArthur
2018-06-22  7:16 ` Thomas Monjalon
2018-06-22 14:16   ` [dpdk-ci] [dpdklab] " Jeremy Plsek
2018-06-22 15:39     ` Thomas Monjalon
2018-06-22 23:00       ` Patrick MacArthur
2018-06-23 11:54         ` Thomas Monjalon [this message]

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=4540187.4GUMsM9S97@xps \
    --to=thomas@monjalon.net \
    --cc=alialnu@mellanox.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    --cc=jplsek@iol.unh.edu \
    --cc=pmacarth@iol.unh.edu \
    /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).