[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-22847.
------------------------------
Resolution: Done
> jbosstools-jiralint-bzira job fails to create new jiras
> -------------------------------------------------------
>
> Key: JBIDE-22847
> URL: https://issues.jboss.org/browse/JBIDE-22847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Gorkem Ercan
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> it looks like the jiras created after ERT-355 are missing remote link which is causing the job to fail.
> For example:
> {code}
> 11:25:19 [INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js "Relaunch" support - not acting as expected
> 11:25:19 [DEBUG] {'project': {'key': 'ERT'}, 'priority': {'name': 'Major'}, 'description': 'When selecting a current running node process in the debug view.\n\nThere are a few options including "Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".', 'components': [{'name': 'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels': ['bzira', 'General'], 'fixVersions': [], 'summary': 'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
> 11:25:19 [INFO] Created https://issues.jboss.org/browse/ERT-362
> 11:25:19 Traceback (most recent call last):
> 11:25:19 File "bzira.py", line 496, in <module>
> 11:25:19 process(bug, createdbugs)
> 11:25:19 File "bzira.py", line 375, in process
> 11:25:19 jira.add_simple_link(newissue, object=link)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/client.py", line 1129, in add_simple_link
> 11:25:19 url, data=json.dumps(data))
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 152, in post
> 11:25:19 return self.__verb('POST', url, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 145, in __verb
> 11:25:19 raise_on_error(response, verb=verb, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 55, in raise_on_error
> 11:25:19 r.status_code, error, r.url, request=request, response=r, **kwargs)
> 11:25:19 jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.jboss.org/rest/api/2/issue/ERT-362/remotelink details: /tmp/jiraerror-MrYBu8.tmp
> 11:25:19 Build step 'Execute shell' marked build as failure
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22847 at 7/28/16 2:14 PM:
-------------------------------------------------------------
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs against older versions.
{code}
But I can create JIRAs with links.
So, I update to https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz{code}
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e... (from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages (from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737... (from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec... (from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9... (from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt, oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get the above problem.
Solution: refactored the link creation thing (so it can be done for existing issues as well as new ones) and fixed the payload expected for the post.
https://github.com/maxandersen/jiralint/commit/b53c03c55a9bd0112561e35731...
was (Author: nickboldt):
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs against older versions.
{code}
But I can create JIRAs with links.
So, I update to https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz{code}
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e... (from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages (from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737... (from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec... (from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9... (from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt, oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get:
{code}
[DEBUG] 498440 - Node.js "Relaunch" support - not acting as expected [JSDT, General, [---]] {20160727T12:40:25} (1 day, 3:37:27.931356) -> https://bugs.eclipse.org/498440
Query: https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar...
[INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js "Relaunch" support - not acting as expected
[DEBUG] {'project': {'key': 'ERT'}, 'priority': {'name': 'Major'}, 'description': 'When selecting a current running node process in the debug view.\n\nThere are a few options including "Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".', 'components': [{'name': 'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels': ['bzira', 'General'], 'fixVersions': [], 'summary': 'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
[INFO] Created https://issues.jboss.org/browse/ERT-369
Traceback (most recent call last):
File "bzira.py", line 496, in <module>
process(bug, createdbugs)
File "bzira.py", line 375, in process
jira.add_simple_link(newissue, object=link)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/client.py", line 1129, in add_simple_link
url, data=json.dumps(data))
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line 152, in post
return self.__verb('POST', url, **kwargs)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line 145, in __verb
raise_on_error(response, verb=verb, **kwargs)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line 55, in raise_on_error
r.status_code, error, r.url, request=request, response=r, **kwargs)
jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.jboss.org/rest/api/2/issue/ERT-369/remotelink details: /tmp/jiraerror-EGuiSP.tmp
{code}
> jbosstools-jiralint-bzira job fails to create new jiras
> -------------------------------------------------------
>
> Key: JBIDE-22847
> URL: https://issues.jboss.org/browse/JBIDE-22847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Gorkem Ercan
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> it looks like the jiras created after ERT-355 are missing remote link which is causing the job to fail.
> For example:
> {code}
> 11:25:19 [INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js "Relaunch" support - not acting as expected
> 11:25:19 [DEBUG] {'project': {'key': 'ERT'}, 'priority': {'name': 'Major'}, 'description': 'When selecting a current running node process in the debug view.\n\nThere are a few options including "Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".', 'components': [{'name': 'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels': ['bzira', 'General'], 'fixVersions': [], 'summary': 'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
> 11:25:19 [INFO] Created https://issues.jboss.org/browse/ERT-362
> 11:25:19 Traceback (most recent call last):
> 11:25:19 File "bzira.py", line 496, in <module>
> 11:25:19 process(bug, createdbugs)
> 11:25:19 File "bzira.py", line 375, in process
> 11:25:19 jira.add_simple_link(newissue, object=link)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/client.py", line 1129, in add_simple_link
> 11:25:19 url, data=json.dumps(data))
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 152, in post
> 11:25:19 return self.__verb('POST', url, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 145, in __verb
> 11:25:19 raise_on_error(response, verb=verb, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 55, in raise_on_error
> 11:25:19 r.status_code, error, r.url, request=request, response=r, **kwargs)
> 11:25:19 jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.jboss.org/rest/api/2/issue/ERT-362/remotelink details: /tmp/jiraerror-MrYBu8.tmp
> 11:25:19 Build step 'Execute shell' marked build as failure
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-22847 at 7/28/16 2:14 PM:
-------------------------------------------------------------
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs against older versions.
{code}
But I can create JIRAs with links.
So, I update to https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e... (from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages (from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737... (from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec... (from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9... (from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt, oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get the above problem.
Solution: refactored the link creation thing (so it can be done for existing issues as well as new ones) and fixed the payload expected for the post.
https://github.com/maxandersen/jiralint/commit/b53c03c55a9bd0112561e35731...
was (Author: nickboldt):
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs against older versions.
{code}
But I can create JIRAs with links.
So, I update to https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz{code}
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e... (from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages (from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737... (from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec... (from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9... (from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt, oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get the above problem.
Solution: refactored the link creation thing (so it can be done for existing issues as well as new ones) and fixed the payload expected for the post.
https://github.com/maxandersen/jiralint/commit/b53c03c55a9bd0112561e35731...
> jbosstools-jiralint-bzira job fails to create new jiras
> -------------------------------------------------------
>
> Key: JBIDE-22847
> URL: https://issues.jboss.org/browse/JBIDE-22847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Gorkem Ercan
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> it looks like the jiras created after ERT-355 are missing remote link which is causing the job to fail.
> For example:
> {code}
> 11:25:19 [INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js "Relaunch" support - not acting as expected
> 11:25:19 [DEBUG] {'project': {'key': 'ERT'}, 'priority': {'name': 'Major'}, 'description': 'When selecting a current running node process in the debug view.\n\nThere are a few options including "Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".', 'components': [{'name': 'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels': ['bzira', 'General'], 'fixVersions': [], 'summary': 'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
> 11:25:19 [INFO] Created https://issues.jboss.org/browse/ERT-362
> 11:25:19 Traceback (most recent call last):
> 11:25:19 File "bzira.py", line 496, in <module>
> 11:25:19 process(bug, createdbugs)
> 11:25:19 File "bzira.py", line 375, in process
> 11:25:19 jira.add_simple_link(newissue, object=link)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/client.py", line 1129, in add_simple_link
> 11:25:19 url, data=json.dumps(data))
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 152, in post
> 11:25:19 return self.__verb('POST', url, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 145, in __verb
> 11:25:19 raise_on_error(response, verb=verb, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 55, in raise_on_error
> 11:25:19 r.status_code, error, r.url, request=request, response=r, **kwargs)
> 11:25:19 jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.jboss.org/rest/api/2/issue/ERT-362/remotelink details: /tmp/jiraerror-MrYBu8.tmp
> 11:25:19 Build step 'Execute shell' marked build as failure
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22847) jbosstools-jiralint-bzira job fails to create new jiras
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22847?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22847:
------------------------------------
When I run locally, I see:
{code}/usr/lib/python2.7/site-packages/jira/client.py:282: UserWarning: You are running an outdated version of JIRA Python 1.0.3. Current version is 1.0.7. Do not file any bugs against older versions.
{code}
But I can create JIRAs with links.
So, I update to https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
{code}
pip install --upgrade --user bugzilla bugzillatools python-bugzilla jira pytz{code}
Requirement already up-to-date: bugzilla in /usr/lib/python2.7/site-packages
Requirement already up-to-date: bugzillatools in /usr/lib/python2.7/site-packages
Requirement already up-to-date: python-bugzilla in /usr/lib/python2.7/site-packages
Downloading/unpacking jira from https://pypi.python.org/packages/ef/70/f779824bf23a9a8122d4df2644ef518a5a...
Downloading jira-1.0.7-py2.py3-none-any.whl (58kB): 58kB downloaded
Downloading/unpacking pytz from https://pypi.python.org/packages/ba/c7/3d54cad4fb6cf7bf375d39771e67680ec7...
Downloading pytz-2016.6.1-py2.py3-none-any.whl (481kB): 481kB downloaded
Downloading/unpacking requests from https://pypi.python.org/packages/99/b4/63d99ba8e189c47d906b43bae18af4396e... (from python-bugzilla)
Downloading requests-2.10.0-py2.py3-none-any.whl (506kB): 506kB downloaded
Requirement already up-to-date: six>=1.9.0 in /usr/lib/python2.7/site-packages (from jira)
Requirement already up-to-date: tlslite>=0.4.4 in /usr/lib/python2.7/site-packages (from jira)
Downloading/unpacking requests-oauthlib>=0.3.3 from https://pypi.python.org/packages/df/f1/bf7fcb853c7a0abfd53c7ef71a72ad6737... (from jira)
Downloading requests_oauthlib-0.6.2-py2.py3-none-any.whl
Downloading/unpacking requests-toolbelt from https://pypi.python.org/packages/57/60/cc85ca45c85585191e70e21687aeaa74ec... (from jira)
Downloading requests_toolbelt-0.7.0-py2.py3-none-any.whl (52kB): 52kB downloaded
Downloading/unpacking oauthlib>=0.6.2 from https://pypi.python.org/packages/a8/11/fb71ced7057b2a8929f51959f4e97bcee9... (from requests-oauthlib>=0.3.3->jira)
Downloading oauthlib-1.1.2.tar.gz (111kB): 111kB downloaded
Running setup.py (path:/tmp/pip-build-kwjAxw/oauthlib/setup.py) egg_info for package oauthlib
Installing collected packages: jira, pytz, requests, requests-oauthlib, requests-toolbelt, oauthlib
Running setup.py install for oauthlib
Successfully installed jira pytz requests requests-oauthlib requests-toolbelt oauthlib
Cleaning up...
{code}
and I get:
{code}
[DEBUG] 498440 - Node.js "Relaunch" support - not acting as expected [JSDT, General, [---]] {20160727T12:40:25} (1 day, 3:37:27.931356) -> https://bugs.eclipse.org/498440
Query: https://issues.jboss.org/rest/api/2/search?jql=project+%3D+ERT+and+summar...
[INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js "Relaunch" support - not acting as expected
[DEBUG] {'project': {'key': 'ERT'}, 'priority': {'name': 'Major'}, 'description': 'When selecting a current running node process in the debug view.\n\nThere are a few options including "Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".', 'components': [{'name': 'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels': ['bzira', 'General'], 'fixVersions': [], 'summary': 'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
[INFO] Created https://issues.jboss.org/browse/ERT-369
Traceback (most recent call last):
File "bzira.py", line 496, in <module>
process(bug, createdbugs)
File "bzira.py", line 375, in process
jira.add_simple_link(newissue, object=link)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/client.py", line 1129, in add_simple_link
url, data=json.dumps(data))
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line 152, in post
return self.__verb('POST', url, **kwargs)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line 145, in __verb
raise_on_error(response, verb=verb, **kwargs)
File "/home/nboldt/.local/lib/python2.7/site-packages/jira/resilientsession.py", line 55, in raise_on_error
r.status_code, error, r.url, request=request, response=r, **kwargs)
jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.jboss.org/rest/api/2/issue/ERT-369/remotelink details: /tmp/jiraerror-EGuiSP.tmp
{code}
> jbosstools-jiralint-bzira job fails to create new jiras
> -------------------------------------------------------
>
> Key: JBIDE-22847
> URL: https://issues.jboss.org/browse/JBIDE-22847
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Gorkem Ercan
> Assignee: Nick Boldt
> Fix For: 4.4.1.AM3
>
>
> it looks like the jiras created after ERT-355 are missing remote link which is causing the job to fail.
> For example:
> {code}
> 11:25:19 [INFO] Creating jira for #498440 NEW - jsdt.javascript-inbox(a)eclipse.org - Node.js "Relaunch" support - not acting as expected
> 11:25:19 [DEBUG] {'project': {'key': 'ERT'}, 'priority': {'name': 'Major'}, 'description': 'When selecting a current running node process in the debug view.\n\nThere are a few options including "Relaunch", and also "Terminate and Relaunch"\n\nIts not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".', 'components': [{'name': 'JSDT'}], 'issuetype': {'name': 'Task'}, 'labels': ['bzira', 'General'], 'fixVersions': [], 'summary': 'Node.js "Relaunch" support - not acting as expected [EBZ#498440]'}
> 11:25:19 [INFO] Created https://issues.jboss.org/browse/ERT-362
> 11:25:19 Traceback (most recent call last):
> 11:25:19 File "bzira.py", line 496, in <module>
> 11:25:19 process(bug, createdbugs)
> 11:25:19 File "bzira.py", line 375, in process
> 11:25:19 jira.add_simple_link(newissue, object=link)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/client.py", line 1129, in add_simple_link
> 11:25:19 url, data=json.dumps(data))
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 152, in post
> 11:25:19 return self.__verb('POST', url, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 145, in __verb
> 11:25:19 raise_on_error(response, verb=verb, **kwargs)
> 11:25:19 File "/home/hudson/.local/lib/python2.6/site-packages/jira/resilientsession.py", line 55, in raise_on_error
> 11:25:19 r.status_code, error, r.url, request=request, response=r, **kwargs)
> 11:25:19 jira.exceptions.JIRAError: JiraError HTTP 400 url: https://issues.jboss.org/rest/api/2/issue/ERT-362/remotelink details: /tmp/jiraerror-MrYBu8.tmp
> 11:25:19 Build step 'Execute shell' marked build as failure
> {code}
> -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-jiralint-b...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22851) Deploy Docker Wizard: Unhandled event loop exception in Search dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22851?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22851:
-------------------------------------
[~nickboldt] are there any plans to pick up the latest docker tools in 4.4.1.AM3?
> Deploy Docker Wizard: Unhandled event loop exception in Search dialog
> ---------------------------------------------------------------------
>
> Key: JBIDE-22851
> URL: https://issues.jboss.org/browse/JBIDE-22851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.1.AM2
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
>
> In Deploy Image to OpenShift wizard opened via context menu item Deploy Docker Image of a project in OpenShift Explorer view, there is a Search button which opens a Search wizard to search for images on docker hub.
> At the moment, when I search any image, table showing images is empty and there is Unhandled Event Loop Exception with following stack trace
> {code}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.SWT.error(SWT.java:4419)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1321)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageSearchPage$IconColumnLabelProvider.measure(ImageSearchPage.java:436)
> at org.eclipse.jface.viewers.OwnerDrawLabelProvider$OwnerDrawListener.handleEvent(OwnerDrawLabelProvider.java:56)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349)
> at org.eclipse.swt.widgets.Table.sendMeasureEvent(Table.java:2653)
> at org.eclipse.swt.widgets.Table.rendererGetPreferredWidthProc(Table.java:2673)
> at org.eclipse.swt.widgets.Display.rendererGetPreferredWidthProc(Display.java:1398)
> at org.eclipse.swt.internal.gtk.OS._gtk_cell_renderer_get_preferred_size(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_cell_renderer_get_preferred_size(OS.java:6838)
> at org.eclipse.swt.widgets.Widget.gtk_cell_renderer_get_preferred_size(Widget.java:2076)
> at org.eclipse.swt.widgets.Table.rendererRender(Table.java:2772)
> at org.eclipse.swt.widgets.Table.rendererRenderProc(Table.java:2690)
> at org.eclipse.swt.widgets.Display.rendererRenderProc(Display.java:1412)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$3.widgetSelected(DeployImagePage.java:251)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler$2$1.run(DeployImageHandler.java:94)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22851) Deploy Docker Wizard: Unhandled event loop exception in Search dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22851?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-22851:
-------------------------------------
This has been fixed upstream https://bugs.eclipse.org/bugs/show_bug.cgi?id=496432
> Deploy Docker Wizard: Unhandled event loop exception in Search dialog
> ---------------------------------------------------------------------
>
> Key: JBIDE-22851
> URL: https://issues.jboss.org/browse/JBIDE-22851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.1.AM2
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
>
> In Deploy Image to OpenShift wizard opened via context menu item Deploy Docker Image of a project in OpenShift Explorer view, there is a Search button which opens a Search wizard to search for images on docker hub.
> At the moment, when I search any image, table showing images is empty and there is Unhandled Event Loop Exception with following stack trace
> {code}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.SWT.error(SWT.java:4419)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1321)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageSearchPage$IconColumnLabelProvider.measure(ImageSearchPage.java:436)
> at org.eclipse.jface.viewers.OwnerDrawLabelProvider$OwnerDrawListener.handleEvent(OwnerDrawLabelProvider.java:56)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349)
> at org.eclipse.swt.widgets.Table.sendMeasureEvent(Table.java:2653)
> at org.eclipse.swt.widgets.Table.rendererGetPreferredWidthProc(Table.java:2673)
> at org.eclipse.swt.widgets.Display.rendererGetPreferredWidthProc(Display.java:1398)
> at org.eclipse.swt.internal.gtk.OS._gtk_cell_renderer_get_preferred_size(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_cell_renderer_get_preferred_size(OS.java:6838)
> at org.eclipse.swt.widgets.Widget.gtk_cell_renderer_get_preferred_size(Widget.java:2076)
> at org.eclipse.swt.widgets.Table.rendererRender(Table.java:2772)
> at org.eclipse.swt.widgets.Table.rendererRenderProc(Table.java:2690)
> at org.eclipse.swt.widgets.Display.rendererRenderProc(Display.java:1412)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$3.widgetSelected(DeployImagePage.java:251)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler$2$1.run(DeployImageHandler.java:94)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22851) Deploy Docker Wizard: Unhandled event loop exception in Search dialog
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22851?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-22851:
--------------------------------
Component/s: upstream
> Deploy Docker Wizard: Unhandled event loop exception in Search dialog
> ---------------------------------------------------------------------
>
> Key: JBIDE-22851
> URL: https://issues.jboss.org/browse/JBIDE-22851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.4.1.AM2
> Environment: Fedora 24, GTK 3
> Reporter: Marián Labuda
> Labels: deploy_docker_wizard, openshift_v3
>
> In Deploy Image to OpenShift wizard opened via context menu item Deploy Docker Image of a project in OpenShift Explorer view, there is a Search button which opens a Search wizard to search for images on docker hub.
> At the moment, when I search any image, table showing images is empty and there is Unhandled Event Loop Exception with following stack trace
> {code}
> org.eclipse.swt.SWTException: Graphic is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.SWT.error(SWT.java:4419)
> at org.eclipse.swt.graphics.Image.getBounds(Image.java:1321)
> at org.eclipse.linuxtools.internal.docker.ui.wizards.ImageSearchPage$IconColumnLabelProvider.measure(ImageSearchPage.java:436)
> at org.eclipse.jface.viewers.OwnerDrawLabelProvider$OwnerDrawListener.handleEvent(OwnerDrawLabelProvider.java:56)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349)
> at org.eclipse.swt.widgets.Table.sendMeasureEvent(Table.java:2653)
> at org.eclipse.swt.widgets.Table.rendererGetPreferredWidthProc(Table.java:2673)
> at org.eclipse.swt.widgets.Display.rendererGetPreferredWidthProc(Display.java:1398)
> at org.eclipse.swt.internal.gtk.OS._gtk_cell_renderer_get_preferred_size(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_cell_renderer_get_preferred_size(OS.java:6838)
> at org.eclipse.swt.widgets.Widget.gtk_cell_renderer_get_preferred_size(Widget.java:2076)
> at org.eclipse.swt.widgets.Table.rendererRender(Table.java:2772)
> at org.eclipse.swt.widgets.Table.rendererRenderProc(Table.java:2690)
> at org.eclipse.swt.widgets.Display.rendererRenderProc(Display.java:1412)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4141)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$3.widgetSelected(DeployImagePage.java:251)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:257)
> at org.jboss.tools.openshift.internal.ui.handler.DeployImageHandler$2$1.run(DeployImageHandler.java:94)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (ERT-373) Node.js "Relaunch" support - not acting as expected [EBZ#498440]
by Nick Boldt (JIRA)
Nick Boldt created ERT-373:
------------------------------
Summary: Node.js "Relaunch" support - not acting as expected [EBZ#498440]
Key: ERT-373
URL: https://issues.jboss.org/browse/ERT-373
Project: Eclipse Release Train
Issue Type: Task
Components: JSDT
Reporter: Nick Boldt
When selecting a current running node process in the debug view.
There are a few options including "Relaunch", and also "Terminate and Relaunch"
Its not clear that relaunch should act any differently than terminate and relaunch, because without first terminating the process, launching the node process will always result in a type of "Error: listen EADDRINUSE".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBTIS-819) Update fuse icons for 9.0.1.GA
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-819:
--------------------------------
Summary: Update fuse icons for 9.0.1.GA
Key: JBTIS-819
URL: https://issues.jboss.org/browse/JBTIS-819
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: distribution, Fuse IDE
Affects Versions: 9.0.1.CR3
Reporter: Paul Leacu
Assignee: Paul Leacu
Priority: Minor
Fix For: 9.0.1.GA
Update the fuse icons - they are out of date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22852) Add check for errors in log when cancelling New Project wizard in OpenNewApplicationWizardWithNoProjectTest
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22852?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22852:
---------------------------------------
Yeah, it would be nice. But this is an issue for many tests. Mostly in tests, when there is a failure, a popped-up error dialog is expected. If there is silent error in error log, it is often not discovered by automated tests. It would be nice to have general logic to test whether there are new "silent" errors in error log created during a specific test run.
> Add check for errors in log when cancelling New Project wizard in OpenNewApplicationWizardWithNoProjectTest
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22852
> URL: https://issues.jboss.org/browse/JBIDE-22852
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift, qa
> Affects Versions: 4.4.1.AM1
> Reporter: Viacheslav Kabanovich
> Fix For: 4.4.1.AM3
>
>
> There is testOpenNewApplicationWizardFromCentralWithNoProjects that creates new project and checks that the created project is selected in New Application wizard.
> We need a test like testOpenNewApplicationWizardFromOpenShiftExplorerWithNoProjectsAndCancelNewProject that cancels creating new project and (in this case of starting from Openshift explorer) checks that New Application wizard is closed and no errors are logged to the Eclipse log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months