Better showing of #include

[albert-github]

Getting a better (and consistent) output for the include file to be used with some functions. Normally #include are sown as in a typewrite font, but the #include in these cases were shown in a code block way.

For e.g Weights/group__PkgWeightsRefUniformRegionWeights.htmlthe w`#include was shown as:

and will now be shown as:

[sloriot]

CGAL-6.0-Ic-42 shows new warnings with doxygen 1.8.13 with those changes.

[albert-github]

I think we can ignore these as I think the doxygen version 1.8.13 won't be used anymore for the CGAL 6.0 version as here at least the version 1.9.6 will be used (so no backport).

[albert-github]

Also a bit strange for me is that the CGAL-6.0-Ic-42 exhibits the problem and CGAL-6.0-Ic-43 doesn't though as far as I can see both versions included this proposed patch about #include.

Edit looks like in CGAL-6.0-Ic-43the patch is not tested (though I don't see this reflected in the labels with this issue...)

[sloriot]

CGAL-6.0-Ic-43 only has #7526

[albert-github]

Explains why the CGAL-6.0-Ic-43 doesn't have the problem, though from the, last, label actions I see:

which gave the impression to me, as layman, that the PR #7648 is also included in the test.
(still the remark about the used doxygen versions stands, and has in my opinion a higher relevance than the warnings generated).

[sloriot]

I'm currently using 2 batches, I'm alternating them.

[albert-github]

Ahh that explains it.

[albert-github]

Is there a way so we can see what is tested i.e.:

• what is the base CGAL version tested (i.e. the hash value)
• the pull requests that are tested

(I once saw the labels "Batch_1" and "Batch_2" but they are hardly applied and don't see them at all with the current "Under testing").

[sloriot]

If you click on a test result, you see the list of PRs merged at the top of the page. For example here.

[albert-github]

I nearly finished my reply (I just leave it as a sort of reference) when I got a "brainwave" that there might exist a page https://cgal.geometryfactory.com/CGAL/testsuite analogous to the https://cgal.geometryfactory.com/CGAL/Manual_doxygen_test/page that might give direct access to the information I described and indeed it was present and gives even more selection possibilities.
So I now created a shortcut for myself and can easily visit it.
(As far as I can tell the information is only present for the MSVC tests (edit not true as I see in the long table below the information direct clickable and in the top table in the different parts one has to scroll a bit more down) but that is all sufficient for me).

Thanks for the information and the patience about these questions.

At the top this is the information I requested, though you mentioned the link:

• https://cgal.geometryfactory.com/CGAL/testsuite/CGAL-6.0-Ic-44/AABB_tree/TestReport_Christo_MSVC-2022-Community-Release.gz

that it is "just" for the AABB_tree is not a problem as at the top of the page this information is present, though there is no reference to the mentioned page on:

• https://cgal.geometryfactory.com/CGAL/Manual_doxygen_test/
• https://cgal.geometryfactory.com/CGAL/Manual_doxygen_test/CGAL-6.0-Ic-44/index.html
• the separate log pages

So it is still a bit an educational guess to get the correct link (i.e. changing the CGAL-6.0-Ic-44 and in future the part Christo_MSVC-2022-Community-Release.
So in my opinion it would be nice to have the "top" information available directly through a link at the page https://cgal.geometryfactory.com/CGAL/Manual_doxygen_test/ or to have an extra column in the documentation page.

[sloriot]

I agree that this information should be directly available in the testsuite landing page, especially because now we only merge pull requests, we could only the list of PR + hash. Let's create an issue for that.

[albert-github]

Will you create an issue or should I try to do it. #7654

[sloriot]

Successfully tested in CGAL-6.0-Ic-56