search

JetBrains / teamcity-investigations-auto-assigner

Assigns investigations of build failures automatically based on heuristics
Apache License 2.0
9 stars 14 forks source link

Broken build processing never stops #45

Closed Sharken03 closed 5 years ago

Sharken03 commented 5 years ago

Problem encountered with TeamCity 2018.2.2 and the bundled Auto-assigner plugin.

We have encountered a problem with builds that gets cancelled. The build is cancelled by a user during test execution, that is nunit3-console.exe is used with the '-teamcity' argument.

The first processing by the Auto-assigner plugin looks normal enough: [2019-01-29 13:52:58,277] DEBUG - dTestAndBuildProblemsProcessor - Start processing build #69749. [2019-01-29 13:52:58,284] DEBUG - processing.BuildProblemsFilter - Filtering of build problems for build id:69749 started [2019-01-29 13:52:58,284] DEBUG - processing.BuildProblemsFilter - Build problem id:69749:Build failure condition is applicable. [2019-01-29 13:52:58,284] DEBUG - er.processing.FailedTestFilter - Filtering of failed tests for build id:69749 started [2019-01-29 13:52:58,284] DEBUG - igner.processing.BaseProcessor - Build #69749: found 1 applicable build problems and 0 applicable failed tests. [2019-01-29 13:52:58,284] DEBUG - er.processing.FailedTestFilter - Filtering before assign of failed tests for build id:69749 started [2019-01-29 13:52:58,284] DEBUG - processing.BuildProblemsFilter - Filtering before assign of build problems for build id:69749 started [2019-01-29 13:52:58,284] DEBUG - processing.BuildProblemsFilter - Build problem id:69749:Build failure condition is applicable. [2019-01-29 13:52:58,284] INFO - ocessing.BuildProblemsAssigner - Automatically assigning investigation(s) to someuser in Solution {id=Solution, internal id=project17} because of Investigation was automatically assigned to someuser who was the only committer to the build.

However we then see the following lines in the log at each 10 minutes interval: [2019-01-29 14:02:58,331] DEBUG - dTestAndBuildProblemsProcessor - Start processing build #69749. [2019-01-29 14:02:58,342] DEBUG - processing.BuildProblemsFilter - Filtering of build problems for build id:69749 started [2019-01-29 14:02:58,342] DEBUG - er.processing.FailedTestFilter - Filtering of failed tests for build id:69749 started [2019-01-29 14:02:58,342] DEBUG - igner.processing.BaseProcessor - Build #69749: found 0 applicable build problems and 0 applicable failed tests. [2019-01-29 14:02:58,342] DEBUG - er.processing.FailedTestFilter - Filtering before assign of failed tests for build id:69749 started [2019-01-29 14:02:58,342] DEBUG - processing.BuildProblemsFilter - Filtering before assign of build problems for build id:69749 started

It looks like the broken builds processing never realize that the build has been processed.

rugpanov commented 5 years ago

Thank you for your report. I created a ticket for the issue in YouTrack: https://youtrack.jetbrains.com/issue/TW-58984

rugpanov commented 5 years ago

fixed at https://teamcity.jetbrains.com/viewLog.html?buildId=1927110&buildTypeId=TeamCityPluginsByJetBrains_InvestigationsAutoAssigner_BuildAgainstTeamCity81x&tab=artifacts

Fix version 2018.2.3