Do not process events in custom scanners' script engines.

Otherwise we will get calls to slots in the executor
at points in time where none are expected.
Note: This means that custom scanner scripts become non-interruptible.
It is not clear if and how we can fix the relevant bug otherwise.
Putting the input artifact scanner into its own thread seems even more
problematic.

Task-number: QBS-782
Change-Id: I44edebfb2a38dc00062cdb9572991ff9352ddd9f
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>

1 files changed, 1 insertions, 2 deletions

diff --git a/src/lib/corelib/buildgraph/inputartifactscanner.cpp b/src/lib/corelib/buildgraph/inputartifactscanner.cpp
index e14d0ec45..620eca1cb 100644
--- a/src/lib/corelib/buildgraph/inputartifactscanner.cpp
+++ b/src/lib/corelib/buildgraph/inputartifactscanner.cpp
@@ -210,7 +210,6 @@ QSet<DependencyScanner *> InputArtifactScanner::scannersForArtifact(const Artifa
 {
     QSet<DependencyScanner *> scanners;
     ResolvedProduct *product = artifact->product.data();
-    ScriptEngine *engine = product->topLevelProject()->buildData->evaluationContext->engine();
     QHash<FileTag, InputArtifactScannerContext::DependencyScannerCacheItem> &scannerCache
             = m_context->scannersCache[product];
     foreach (const FileTag &fileTag, artifact->fileTags()) {
@@ -224,7 +223,7 @@ QSet<DependencyScanner *> InputArtifactScanner::scannersForArtifact(const Artifa
             foreach (const ResolvedScannerConstPtr &scanner, product->scanners) {
                 if (scanner->inputs.contains(fileTag)) {
                     cache.scanners += DependencyScannerPtr(
-                                new UserDependencyScanner(scanner, m_logger, engine));
+                                new UserDependencyScanner(scanner, m_logger));
                     break;
                 }
             }