Sometimes the parse_build_log script executed wrongly

Continuous Integration: Failed

Running make failed. The CI rejected the staged commits due to the beforementioned reason. Possible reason could be a bug in one of the commits or some more recent change. Please investigate it.

The error was in "qt/qtbase", revision: dbe26f399d1d2252994eb42e05bbc49f4d844c4b

 Usage: ./parse_build_log [options] <logfile> # e.g., given a very large build log, just extract the interesting lines: $ ./parse_build_log my-log.txt compiling qml/qdeclarativebinding.cpp qml/qdeclarativebinding.cpp: In static member function 'static QDeclarativeBinding* QDeclarativeBinding::createBinding(int, QObject*, QDeclarativeContext*, const QString&, int, QObject*)': qml/qdeclarativebinding.cpp:238: error: cannot convert 'QDeclarativeEngine*' to 'QDeclarativeEnginePrivate*' in initialization make[3]: *** [.obj/debug-shared/qdeclarativebinding.o] Error 1 make[2]: *** [sub-declarative-make_default-ordered] Error 2 make[1]: *** [module-qtdeclarative-src-make_default] Error 2 make: *** [module-qtdeclarative] Error 2 # Or perhaps attempt to summarize the error in human-readable format, # and directly load the log over HTTP: $ ./parse_build_log --summarize [http://example.com/some-ci-system/linux-build-log.txt.gz] qtdeclarative failed to compile on Linux: compiling qml/qdeclarativebinding.cpp qml/qdeclarativebinding.cpp: In static member function 'static QDeclarativeBinding* QDeclarativeBinding::createBinding(int, QObject*, QDeclarativeContext*, const QString&, int, QObject*)': qml/qdeclarativebinding.cpp:238: error: cannot convert 'QDeclarativeEngine*' to 'QDeclarativeEnginePrivate*' in initialization make[3]: *** [.obj/debug-shared/qdeclarativebinding.o] Error 1 make[2]: *** [sub-declarative-make_default-ordered] Error 2 make[1]: *** [module-qtdeclarative-src-make_default] Error 2 make: *** [module-qtdeclarative] Error 2 This script takes a raw plain text or gzip-compressed build log and attempts to extract the interesting parts, and possibly provide a nice human-readable summary of the failure. Options: --help Print this message. --summarize If given, as well as printing out the interesting lines from the log, the script will attempt to print out a human-readable summary of the error(s). This option has no effect when --yaml is given. --yaml Use YAML instead of plain text output. The output will consist of a single YAML document with zero or more of the following key/value pairs: summary The human-readable summary of the failure reason (if known). Usually one or two sentences. detail The extracted text from the build log relating to the failure. should_retry A hint that it might make sense to retry the build/test. If set, this indicates that the failure extracted from the log may be unrelated to the code under test; for example, a temporary network outage. --limit LINES Limit the amount of extracted lines to the given value. Use 0 for no limit. If omitted, an undefined but reasonable default is used. --debug Enable some debug messages to STDERR. Use this to troubleshoot when some log is not parsed in the expected manner. 

Build log: [https://testresults.qt.io/logs/qt/qtbase/ad0241a0fcca0a9289c03e3eb124a27c8a324e27/LinuxRHEL_7_6x86_64AndroidAndroid_ANYarmv7Clangqtci-linux-RHEL-7.6-x86_64-0cbc04DisableTests/ea026455277f4e8e3490ac30f75c6464a35c8842/build_1560065500/log.txt.gz]