Fix SQA documentation and add code coverage link [!7 merged]

[idaholab]

Fix SQA documentation and add code coverage link [!7 merged]

[moosebuild]

Job Documentation on 7c1dc16 wanted to post the following:

View the site here

This comment will be updated on new commits.

[moosebuild]

Job Coverage on 7c1dc16 wanted to post the following:

Coverage

Coverage did not change

Full coverage report

This comment will be updated on new commits.

[moosebuild]

In GitLab by @cticenhour on Dec 23, 2021, 23:15

added 1 commit

• 7c1dc16 - Add link to malamute code coverage in navigation menu

Compare with previous version

[moosebuild]

CIVET Testing summary for 063ef9b

Precheck : Passed
Documentation : Passed
Mac Test : Passed
Test : Passed
Test Debug : Passed
Non unity build : Canceled by user
Coverage : Passed

[moosebuild]

CIVET Testing summary for 7c1dc16

Precheck : Passed
Documentation : Passed
Mac Test : Passed
Test : Passed
Test Debug : Passed
Non unity build : Passed
Coverage : Passed

[moosebuild]

In GitLab by @cticenhour on Jan 4, 2022, 08:42

requested review from @sapitts

[moosebuild]

In GitLab by @sapitts on Jan 4, 2022, 11:22

Links work well for the code coverage page (although it is a gloomy code coverage report). Looks like the SQA report pages themselves aren't building: https://malamute-dev.hpc.inl.gov/PRs/7/site/sqa/index.html Is that an artifact of the testing system setup / scope creep for this PR? Or did you intent for this PR to enable the successful building of the SQA report pages?

[moosebuild]

In GitLab by @cticenhour on Jan 4, 2022, 11:42

SQA pages aren't rendered on PRs due to overhead, so the page isn't made by default. I could turn that on, if desired, but that's general practice for apps. The negative of this is that SQA render failures only pop up in main documentation testing (as was the case here).

And re: gloomy code coverage report....working on it with Alex. We had to bring Baldr up-to-date from a 3-year-old MOOSE and it's still a WIP. 😅

[moosebuild]

In GitLab by @sapitts on Jan 4, 2022, 13:22

Gotcha, on both counts (I was just taken aback by the coverage because you were so careful with setting up the controls with Freya, but I'd forgotten about Badlr). I'll merge then, if you've tested locally with --with-sqa?

[moosebuild]

In GitLab by @cticenhour on Jan 4, 2022, 13:49

I have tested locally with the --with-sqa option, so it should work just fine. I should consider setting up an optional test for this option for the future.

Yeah, I'm trying to fix this coverage issue ASAP....fixing up tests as we go, and then re-enabling them (you'll notice on CIVET that many are skipped right now).

[moosebuild]

In GitLab by @sapitts on Jan 4, 2022, 13:53

resolved all threads

[moosebuild]

In GitLab by @sapitts on Jan 4, 2022, 13:53

mentioned in commit 6099aa6