qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH] docs/devel/testing.rst: Update outdated Avocado URLs
Date: Mon, 8 Feb 2021 10:26:00 -0500	[thread overview]
Message-ID: <200f5c1f-9d4f-12d6-4ca7-b576812b0922@redhat.com> (raw)
In-Reply-To: <CAP+75-XPgqwyDmOtR+thBd9Od4hSavb1qA=4JCcO2jQTTG4eiw@mail.gmail.com>

On 2/8/21 7:59 AM, Philippe Mathieu-Daudé wrote:
> On Fri, Feb 5, 2021 at 12:53 AM John Snow <jsnow@redhat.com> wrote:
>>
>> On 10/10/20 4:07 AM, Philippe Mathieu-Daudé wrote:
>>> Avocado documentation referred returns 404 error.
>>> Update the broken links.
>>>
>>> Signed-off-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>>> ---
>>>    docs/devel/testing.rst | 4 ++--
>>>    1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
>>> index bd64c1bdcdd..23a1697d9f4 100644
>>> --- a/docs/devel/testing.rst
>>> +++ b/docs/devel/testing.rst
>>> @@ -696,7 +696,7 @@ To manually install Avocado and its dependencies, run:
>>>
>>>    Alternatively, follow the instructions on this link:
>>>
>>> -  http://avocado-framework.readthedocs.io/en/latest/GetStartedGuide.html#installing-avocado
>>> +  https://avocado-framework.readthedocs.io/en/latest/guides/user/chapters/installing.html
>>>
>>>    Overview
>>>    --------
>>> @@ -879,7 +879,7 @@ Parameter reference
>>>    To understand how Avocado parameters are accessed by tests, and how
>>>    they can be passed to tests, please refer to::
>>>
>>> -  http://avocado-framework.readthedocs.io/en/latest/WritingTests.html#accessing-test-parameters
>>> +  https://avocado-framework.readthedocs.io/en/latest/guides/writer/chapters/writing.html#accessing-test-parameters
>>>
>>>    Parameter values can be easily seen in the log files, and will look
>>>    like the following:
>>>
>>
>> Do you know if there's a way we can augment sphinx to check link status
>> once in a while?
> 
> No, but good idea! Why not ask on the list, IIRC danpb mentioned something
> similar in another thread.
> 
>> If there's a callback where we can get sphinx to call a python function
>> for every URL it finds, we can use response = requests.head(url) and
>> check response.status_code to make sure it's 200 OK.
>>

OK, at Phil's nudge: Does anyone know if there's a Sphinx callback for 
URL processing? We could probably write a test that we could enable 
every-so-often.

I am thinking there might be some benefit to a test suite that we only 
run once-in-a-while during release candidate phases, and this could be 
one of them.

>> --js
>>
> 



      parent reply	other threads:[~2021-02-08 20:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-10  8:07 [PATCH] docs/devel/testing.rst: Update outdated Avocado URLs Philippe Mathieu-Daudé
2020-10-12  3:15 ` Cleber Rosa
2020-10-21  9:50 ` Philippe Mathieu-Daudé
     [not found] ` <f835ae44-ba70-05cb-59b1-97f43f1f1942@redhat.com>
     [not found]   ` <CAP+75-XPgqwyDmOtR+thBd9Od4hSavb1qA=4JCcO2jQTTG4eiw@mail.gmail.com>
2021-02-08 15:26     ` John Snow [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=200f5c1f-9d4f-12d6-4ca7-b576812b0922@redhat.com \
    --to=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.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
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).