-
Bug
-
Resolution: Done
-
P0: Blocker
-
None
-
production
-
None
As a symptom: the integration will get stuck in the integration stage and does not resolve its dependencies.
INFO: guessing the prototype: <class 'storagestructs.Task'> { "project": "qt/qt5", "testedChanges": [], "testConfigurations": [ { "type": 0, "vmTemplate": "qtci-windows-8.1-x86_64-b96318", "target": { "os": 2, "arch": 2, "compiler": 22, "osVersion": 102 }, "host": { "os": 2, "arch": 2, "compiler": 22, "osVersion": 102 }, "features": [ 27, 2, 0, 12, 5 ] } ], "type": 1, "id": "web_qt_qt5_1517815961639", "reviewAction": 0, "source_ref": "refs/changes/79/218679/4", "destination_branch": "5.11", "buildKeys": [], "gerritInstance": "qt-project", "workItemPaths": [], "username": "sifalt", "state": 0, "startTime": 1517815952, "sha1": "", "product": { "project": "qt/qt5", "gerritInstance": "qt-project", "sha1": "499f97a0c001f5a379e427e201ea6606fb4a6f12" }, "taskFailureSummary": "", "endTime": 0 }
The fields workitempaths and buildkeys are empty thus the workitems have never been created. Sometimes, restart of Coin might help with picking up the integrations, but this is not always the case.
The integrations that are stuck are for modules that are not part of qt5.git, which indicates that there is a problem in resolving the module dependencies.
- is duplicated by
-
-
- Closed
-
- is required for
-
-
- Closed
-