All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Generated master docs not up to date - issue in run-docs-build?
Date: Wed, 3 Aug 2022 14:59:23 +0200	[thread overview]
Message-ID: <ac5fc19e-3c47-edb2-b5f0-da408275c0f6@bootlin.com> (raw)

Greetings

I've found issues with https://docs.yoctoproject.org/, generated from 
the master branch:

  * The 4.0.1 and 4.0.2 release notes don't appear on
    https://docs.yoctoproject.org/migration-guides/index.html while they
    are in the master branch
    (https://git.yoctoproject.org/yocto-docs/commit/?id=027a58616db9f3e8ee5992b57fd99cb3c284ece9
    and
    https://git.yoctoproject.org/yocto-docs/commit/?id=a17bfe2636c11ce8e3266d9add804d795991e2ea)
  * PEP517_BUILD_API is still documented on
    https://docs.yoctoproject.org/ref-manual/variables.html#term-PEP517_BUILD_API
    while it was removed by
    https://git.yoctoproject.org/yocto-docs/commit/?id=afa895871e8ec18f4861f48f70b8a54cc2e4cb98

So, some commits in master doesn't seem to have been used for generating 
the docs. However, the latest commit 
(https://git.yoctoproject.org/yocto-docs/commit/?id=5004957d1c65d03d3e296bc9f0a00982457a27f8) 
was used because you have the new hash server (hashserv.yocto.io:8687) 
on 
https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html#building-your-image

On the contrary, https://docs.yoctoproject.org/next generated from the 
master-next branch looks OK as it contains the 3 above changes, and the 
changes from the latest commit.

Weird, isn't it? Could there be an issue in 
https://git.yoctoproject.org/yocto-autobuilder-helper/tree/scripts/run-docs-build 
, the scripts which generates our docs?

I started looking at the Autobuilder logs 
(https://autobuilder.yoctoproject.org/typhoon/#/builders/114), but 
haven't found anything suspicious yet. Investigations may take time though.

Any guesses?

Cheers
Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



             reply	other threads:[~2022-08-03 12:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03 12:59 Michael Opdenacker [this message]
2022-08-03 13:11 ` [docs] Generated master docs not up to date - issue in run-docs-build? Quentin Schulz
2022-08-03 13:20   ` Quentin Schulz
2022-08-03 13:35     ` Michael Opdenacker

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=ac5fc19e-3c47-edb2-b5f0-da408275c0f6@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.