Packages are missing some Coin test logs

After cross-checking with the related subject matter experts, it seems that some autotest logs from the Coin integration builds are missing from the installation content.

Example case illustrating this issue (limited access):

See the Coin Web UI from one integration run. See test logs part. The list shows 15 different test configurations executed successfully:

http://10.212.3.36/coin/integration/qt/tqtc-qt5/tasks/1550426820

But when checking the Qt company internal file server where the logs are exported, there are only logs from 12 test configurations:

http://ci-files02-hki.intra.qt.io/packages/jenkins/qt/5.13.0/latest/test_logs/qtcharts_testLogs/

After initial assessment and discussions the feature flags do not define which logs should be included or excluded.

If this issue is valid issue, then expanding the RTA tests that check the existence of the logs could be considered.

Cross-check results (category, Coin row, mapped zip file):

• MAC
  • MacOS MacOS_10_12 (clang-x86_64) DeveloperBuild, NoFramework, Release, QtNamespace, NoPch, AbortTestingOnFirstFailureMacOS
    • MacOS-MacOS_10_12-Clang-MacOS-MacOS_10_12-X86_64
  • MacOS_10_13 (clang-x86_64) Packaging, DebugAndRelease, Release, AbortTestingOnFirstFailure
    • MacOS-MacOS_10_13-Clang-MacOS-MacOS_10_13-X86_64
• QEMU
  • Linux QEMU (gcc-arm64) on Linux Ubuntu_18_04 (gcc-x86_64) Release, AbortTestingOnFirstFailure
    • Linux-Ubuntu_18_04-GCC-Linux-QEMU-ARM64
  • Linux QEMU (gcc-armv7) on Linux Ubuntu_18_04 (gcc-x86_64) Release, AbortTestingOnFirstFailure
    • Linux-Ubuntu_18_04-GCC-Linux-QEMU-ARMv7
• Redhat
  • Linux RHEL_7_4 (gcc-x86_64) Packaging, Release, NoUseGoldLinker, ForceDebugInfo, SeparateDebugInfo, AbortTestingOnFirstFailure
    • Linux-RHEL_7_4-GCC-Linux-RHEL_7_4-X86_64
• Ubuntu
  • Linux Ubuntu_18_04 (gcc-x86_64) DeveloperBuild, OutOfSourceBuild, QtLibInfix, QtNamespace, BuildExamples, Documentation, AbortTestingOnFirstFailure
  • Linux Ubuntu_18_04 (gcc-x86_64) NoWidgets, ForceDebugInfo, AbortTestingOnFirstFailure
  • Linux Ubuntu_18_04 (gcc-x86_64) TestOnly, LicenseCheck, AbortTestingOnFirstFailure

• • • Linux-Ubuntu_18_04-GCC-Linux-Ubuntu_18_04-X86_64
• Windows 10
  • Windows Windows_10 (msvc2015-x86) on Windows Windows_10 (msvc2015-x86_64) Packaging, DebugAndRelease, Release, ForceDebugInfo, OpenGLDynamic, AbortTestingOnFirstFailure
    • Windows-Windows_10-MSVC2015-Windows-Windows_10-X86
  • Windows Windows_10 (msvc2015-x86_64) Packaging, DebugAndRelease, Release, ForceDebugInfo, OpenGLDynamic, AbortTestingOnFirstFailure
  • Windows Windows_10 (msvc2015-x86_64) DeveloperBuild, Release, QtNamespace, QtLibInfix, BuildExamples, AbortTestingOnFirstFailure
    • Windows-Windows_10-MSVC2015-Windows-Windows_10-X86_64
  • Windows Windows_10 (msvc2017-x86) on Windows Windows_10 (msvc2017-x86_64) Packaging, DebugAndRelease, Release, ForceDebugInfo, OpenGLDynamic, AbortTestingOnFirstFailure
    • Windows-Windows_10-MSVC2017-Windows-Windows_10-X86
  • Windows Windows_10 (msvc2017-x86_64) Packaging, DebugAndRelease, Release, ForceDebugInfo, OpenGLDynamic, AbortTestingOnFirstFailure
    • Windows-Windows_10-MSVC2017-Windows-Windows_10-X86_64
• Windows 7
  • Windows Windows_7 (mingw73-x86) DeveloperBuild, Release, OpenGLDynamic, AbortTestingOnFirstFailure

• • • Windows-Windows_7-Mingw73-Windows-Windows_7-X86
• OpenSuse
  • Linux openSUSE_15_0 (gcc-x86_64) DeveloperBuild, NoPch, AbortTestingOnFirstFailure
    • Linux-openSUSE_15_0-GCC-Linux-openSUSE_15_0-X86_64

The red configs above produce only one zipped log file (bolded) while others produce zipped log files correctly