[
https://issues.apache.org/jira/browse/BEAM-8737?focusedWorklogId=346120&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-346120
]
ASF GitHub Bot logged work on BEAM-8737:
----------------------------------------
Author: ASF GitHub Bot
Created on: 19/Nov/19 17:26
Start Date: 19/Nov/19 17:26
Worklog Time Spent: 10m
Work Description: suztomo commented on issue #10155: [BEAM-8737]
Incorporate TRIAGE NEEDED status in beam_Dependency_Check
URL: https://github.com/apache/beam/pull/10155#issuecomment-555616860
Actually I was not sure "TRIAGE NEEDED" is correct value or not.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 346120)
Time Spent: 50m (was: 40m)
> beam_Dependency_Check is missing bigtable-client-core as high priority items
> ----------------------------------------------------------------------------
>
> Key: BEAM-8737
> URL: https://issues.apache.org/jira/browse/BEAM-8737
> Project: Beam
> Issue Type: Bug
> Components: build-system
> Reporter: Tomo Suzuki
> Assignee: Tomo Suzuki
> Priority: Major
> Time Spent: 50m
> Remaining Estimate: 0h
>
> beam_Dependency_Check is missing high priority items such as
> bigtable-client-core.
> For example,
> https://builds.apache.org/job/beam_Dependency_Check/235/consoleFull sent
> email but the email did not contain bigtable-client-core. The current version
> 1.8.0 is 4-minor-version older than the latest 1.12.1.
> Initially I was suspecting the line with {{high_priority_deps.append}}:
> {noformat}
> if (version_comparer.compare_dependency_versions(curr_ver, latest_ver)
> or
> compare_dependency_release_dates(curr_release_date,
> latest_release_date)):
> # Create a new issue or update on the existing issue
> jira_issue = jira_manager.run(dep_name, curr_ver, latest_ver,
> sdk_type, group_id = group_id)
> if (jira_issue.fields.status.name == 'Open' or
> jira_issue.fields.status.name == 'Reopened'):
> dep_info += "<td><a href=\'{0}\'>{1}</a></td></tr>".format(
> ReportGeneratorConfig.BEAM_JIRA_HOST+"browse/"+ jira_issue.key,
> jira_issue.key)
> high_priority_deps.append(dep_info)
> {noformat}
> and 2nd run would include the artifact in the email. But it did not:
> https://builds.apache.org/job/beam_Dependency_Check/237/
> {noformat}
> 15:43:02 Start processing: - com.google.cloud.bigtable:bigtable-client-core
> [1.8.0 -> 1.12.1]
> 15:43:02
> 15:43:02 INFO:root:Finding release date of
> com.google.cloud.bigtable:bigtable-client-core 1.8.0 from the Maven Central
> 15:43:02 INFO:root:Finding release date of
> com.google.cloud.bigtable:bigtable-client-core 1.12.1 from the Maven Central
> 15:43:03 INFO:root:Start handling the JIRA issues for Java dependency:
> com.google.cloud.bigtable:bigtable-client-core 1.12.1
> 15:43:04 INFO:root:The parent issue BEAM-8690 is not opening. Attempt
> reopening the issue
> 15:43:04 Traceback (most recent call last):
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/.test-infra/jenkins/jira_utils/jira_manager.py",
> line 90, in run
> 15:43:04 self.jira.reopen_issue(parent_issue)
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/.test-infra/jenkins/jira_utils/jira_client.py",
> line 130, in reopen_issue
> 15:43:04 self.jira.transition_issue(issue.key, 3)
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/dependency/check/lib/python3.5/site-packages/jira/client.py",
> line 126, in wrapper
> 15:43:04 result = func(*arg_list, **kwargs)
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/dependency/check/lib/python3.5/site-packages/jira/client.py",
> line 1578, in transition_issue
> 15:43:04 url, data=json.dumps(data))
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/dependency/check/lib/python3.5/site-packages/jira/resilientsession.py",
> line 154, in post
> 15:43:04 return self.__verb('POST', url, **kwargs)
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/dependency/check/lib/python3.5/site-packages/jira/resilientsession.py",
> line 147, in __verb
> 15:43:04 raise_on_error(response, verb=verb, **kwargs)
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/dependency/check/lib/python3.5/site-packages/jira/resilientsession.py",
> line 57, in raise_on_error
> 15:43:04 r.status_code, error, r.url, request=request, response=r,
> **kwargs)
> 15:43:04 jira.exceptions.JIRAError: JiraError HTTP 400 url:
> https://issues.apache.org/jira/rest/api/2/issue/BEAM-8690/transitions
> 15:43:04 text: It seems that you have tried to perform a workflow
> operation (Reopen Issue) that is not valid for the current state of this
> issue (BEAM-8690). The likely cause is that somebody has changed the issue
> recently, please look at the issue history for details.
> 15:43:04
> 15:43:04 response headers = {'X-AREQUESTID': '1243x60347388x3', 'Date':
> 'Mon, 18 Nov 2019 20:43:04 GMT', 'X-AUSERNAME': ****, 'Cache-Control':
> 'no-cache, no-store, no-transform', 'Server': 'Apache', 'Connection':
> 'close', 'X-XSS-Protection': '1; mode=block', 'Content-Type':
> 'application/json;charset=UTF-8', 'Content-Security-Policy': "frame-ancestors
> 'self'", 'Transfer-Encoding': 'chunked', 'X-Frame-Options': 'SAMEORIGIN',
> 'X-ASEN': 'SEN-2062203', 'X-Seraph-LoginReason': 'OK',
> 'X-Content-Type-Options': 'nosniff', 'X-ASESSIONID': '877oha'}
> 15:43:04 response text = {"errorMessages":["It seems that you have tried
> to perform a workflow operation (Reopen Issue) that is not valid for the
> current state of this issue (BEAM-8690). The likely cause is that somebody
> has changed the issue recently, please look at the issue history for
> details."],"errors":{}}
> 15:43:04 ERROR:root:Failed reopening the parent issue BEAM-8690.
> 15:43:04 Stop handling the JIRA issue for
> com.google.cloud.bigtable:bigtable-client-core, 1.12.1
> 15:43:04 Traceback (most recent call last):
> 15:43:04 File
> "/home/jenkins/jenkins-slave/workspace/beam_Dependency_Check/src/.test-infra/jenkins/dependency_check/dependency_check_report_generator.py",
> line 143, in prioritize_dependencies
> 15:43:04 if (jira_issue.fields.status.name == 'Open' or
> 15:43:04 AttributeError: 'NoneType' object has no attribute 'fields'
> 15:43:04 INFO:root:
> {noformat}
> It seems JIRA ticket lifecycle issue. The successful case
> (https://issues.apache.org/jira/browse/BEAM-5897 ) has status Open, while the
> failed case has "TRIAGE NEEDED"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
