1817962 - The number of warnings locally and on the CI is different

Status: NEW

(Developer Infrastructure :: Source Documentation, defect)

Description

[ogiorgis]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0

Steps to reproduce:

The command ./mach doc have less warnings on local than on CI.

Expected results:

We need to list what are the additional warnings on the CI and understand why they are raised.

Comment 1

[Negritas Sergiu, Desktop QA]

Hello! Could you please provide more detailed steps on how to reproduce the issue?

Comment 2

[ogiorgis]

Hi @sergiu

When I build the doc on my local machine, I have less warning than on gecko.

For example:
This build https://firefoxci.taskcluster-artifacts.net/fMRfJyxVQEeGhfUZwcKU8A/0/public/logs/live_backing.log finish with 6291 warnings.
But the same changeset on my machine finish with 6231 warnings.

In this case, the following warnings are only on CI:

• WARNING: Include file '/builds/worker/checkouts/gecko/obj-x86_64-pc-linux-gnu/docs/html/_staging/ipc/_static/PMyManager.ipdl' not found or reading it failed
• WARNING: autodoc: failed to import module 'docker' from module 'gecko_taskgraph'
• WARNING: autodoc: failed to import method 'moznetwork.get_ip' from module 'moznetwork';
• WARNING: autodoc: failed to import module 'test_transforms_job' from module 'gecko_taskgraph.test'
  ...

but it is not exhaustive

Comment 3

[ogiorgis]

Also on CI: FileNotFoundError: [Errno 2] No such file or directory: '/builds/worker/checkouts/gecko/taskcluster/ci/docker-image/kind.yml'

Comment 4

[BugBot [:suhaib / :marco]]

The severity field is not set for this bug.
:Sylvestre, could you have a look please?

For more information, please visit BugBot documentation.

Comment 5

[Mark Banner (:standard8)]

There's been quite a lot of warnings fixed since this was first filed, additionally bug 1861953 fixed a few as well. I currently see 318 warnings locally and we know there are 809 warnings on CI.

I think the cause might be one of a couple of things:

1. The sparse checkout is not checking out enough. This is causing "file not found" types of errors. This was seen in bug 1861953 which fixed a few.
2. I got the impression from some of the issues that the relevant python modules aren't available. This could be due to the sparse checkout, or it could be they aren't available on the build for some reason.

A first step here might be to do a try run with the sparse checkout effectively turned off, and see how many warnings that generates.

Comment 6

[Mark Banner (:standard8)]

Comment 5 was incorrect. You only get the full count of warnings on a clobber. If you rebuild docs a second time, then you get less.

Bug 1865208 is fixing some issues due to the spares issue.

When run on a clobber, I now see only 4 more warnings over what is seen on CI. I therefore would say it would be better to concentrate on resolving the majority of the warnings, rather than the differences between CI and local machines.