create dummy images in advance for doxygen not to complain

[ferdymercury]

This Pull request:

Changes or fixes:

Currently, building the documentation issues 3700 warnings, see https://lcgapp-services.cern.ch/root-jenkins/view/ROOT/job/root-makedoc-master/lastBuild/parsed_console/

With the current hack, we would go down to just 2700.

By the way, it would be nice to fine-tune the parser: see root-project/jenkins-pipelines#10

Checklist:

• tested changes locally
• updated the docs (if necessary)

See related discussion doxygen/doxygen#9044

[phsft-bot]

Starting build on ROOT-debian10-i386/soversion, ROOT-performance-centos8-multicore/cxx17, ROOT-ubuntu18.04/nortcxxmod, ROOT-ubuntu2004/python3, mac1015/cxx17, mac11/cxx14, windows10/cxx14
How to customize builds

[couet]

I see the idea... you are creating empty pictures first just to remove the warnings?

[ferdymercury]

Exactly. Just a workaround, in order to be able to focus on the other real warnings.

[couet]

I see the idea. I will try locally

[couet]

The grep is quite long to perform.. it adds 1 minute. Well compared to the whole build it is only a small %.

[couet]

You are looking only for macro_image. This is used only in the tutorials. So you do not need to grep the whole ROOT repository as you do. You need to grep only the tutorials folder.

[couet]

And by the way, I cannot reproduce locally these warnings. For example:

...
Info in <TCanvas::Print>: SVG file mathsymb.svg has been created
Info in <TCanvas::Print>: png file /Users/couet/rootdoc/html/pict1_latex5.C.png has been created
Info in <TCanvas::Print>: ps file mathsymb.ps has been created
...

On the log-ouput you pointed we can see a warning about latex5.C but locally, with a fresh build, it is fine. No warning.

[phsft-bot]

Starting build on ROOT-debian10-i386/soversion, ROOT-performance-centos8-multicore/cxx17, ROOT-ubuntu18.04/nortcxxmod, ROOT-ubuntu2004/python3, mac1015/cxx17, mac11/cxx14, windows10/cxx14
How to customize builds

[ferdymercury]

You are looking only for macro_image. This is used only in the tutorials. So you do not need to grep the whole ROOT repository as you do. You need to grep only the tutorials folder.

Good point. Changed.

[ferdymercury]

And by the way, I cannot reproduce locally these warnings. For example:

...
Info in <TCanvas::Print>: SVG file mathsymb.svg has been created
Info in <TCanvas::Print>: png file /Users/couet/rootdoc/html/pict1_latex5.C.png has been created
Info in <TCanvas::Print>: ps file mathsymb.ps has been created
...

On the log-ouput you pointed we can see a warning about latex5.C but locally, with a fresh build, it is fine. No warning.

Maybe it would be useful to add to the Jenkins build a step that cleans the git repository on sftnight before starting the build? To get fresh builds there too?

[phsft-bot]

Build failed on windows10/cxx14.
Running on null:C:\build\workspace\root-pullrequests-build
See console output.

Failing tests:

• projectroot.roottest.root.hist.operator.roottest_root_hist_operator_runsparse

[ferdymercury]

Maybe it would be useful to add to the Jenkins build a step that cleans the git repository on sftnight before starting the build? To get fresh builds there too?

For example using the git clean command within https://github.com/root-project/rootspi/blob/master/rdoc/preparesource.sh:
https://www.geeksforgeeks.org/git-clean/

[couet]

It is more tricky than I thought. Actually I see the error "sometimes" on fresh builds only. That's not clear yet ...

[ferdymercury]

Maybe it's just a multi-threading thing? The output lines are ordered differently each time because the threads write to stdout in different order. If you Search for "latex5.C", don't you see always a warning line (every time in different position):
/home/sftnight/build/workspace/root-makedoc-master/rootspi/rdoc/src/master/tutorials/graphics/latex5.C:8: warning: image file pict1_latex5.C.png is not found in IMAGE_PATH: assuming external image.

[couet]

I thought of it, that's why I do not use the option -j to be sure it is not multithreaded. I will investigate further asap.

[phsft-bot]

Starting build on ROOT-debian10-i386/soversion, ROOT-performance-centos8-multicore/cxx17, ROOT-ubuntu18.04/nortcxxmod, ROOT-ubuntu2004/python3, mac12/noimt, mac11/cxx14, windows10/cxx14
How to customize builds

[couet]

Do we still want this? It does not seem really safe...