analyze --capture-analysis-output writes corrupt zipfiles

Describe the bug At the end of analyze, I see hundreds of the following warnings:

/usr/lib/python3.8/zipfile.py:1517: UserWarning: Duplicate name: 'sources-root/home/cc-runs/src/qt/qt5/qtbase/src/printsupport/kernel/qprint_p.h'
  return self._open_to_write(zinfo, force_zip64=force_zip64)

The zipfiles stored under results_dir/run_name/failed are troublesome to unzip. On linux with the unzip command I am asked countless of times whether I want to overwrite certain files.

CodeChecker version is today’s latest HEAD at d78f1d9306868669ec07b8996c2cec1d29a664a3.

[csordasmarton]

You can use the following option of the CodeChecker analyze command:

--file FILE [FILE ...]
                        Analyze only the given file(s) not the whole
                        compilation database. Absolute directory paths should
                        start with '/', relative directory paths should start
                        with '*' and it can contain path glob pattern.
                        Example: '/path/to/main.cpp', 'lib/*.cpp', */test*'.

[jimis]

Do you have the standard output and error logs related to the analysis of qdatetime.cpp file?

Because in your zip file name I can see the unknown keyword which comes from this code:

https://github.com/Ericsson/codechecker/blob/792bd8150210c6cdd2f2ac728ed75ce31d77972c/analyzer/codechecker_analyzer/analysis_manager.py#L536-L540

So the problem is not a compiler crash or a compiler error. I am curious what it can be.

So as you can see in the log, the error is:

/usr/include/c++/9/array:245:28: error: cannot import unsupported AST node CXXFoldExpr
      -> array<enable_if_t<(is_same_v<_Tp, _Up> && ...), _Tp>,

The return code cannot be seen in the log, but in the file return-code I see -11.

As mentioned earlier, this has been reported at #3012 (see 2nd point in description). It is blocking CTU analysis for C++17 projects.

But how is it related to the corrupted zipfiles issue?