Re: [openstack-dev] [Neutron] Availability of external testing logs
Yeah - it appears that even if you clear a -1 the countdown clock still keeps ticking, one of my reviews[0] just expired this morning. I'll bring it up at the IPv6 meeting to restore any patches in our topic that are currently abandoned so that you can clear them. [0] https://review.openstack.org/#/c/56381/9 Sean M. Collins From: Torbjorn Tornkvist [kruska...@gmail.com] Sent: Wednesday, January 15, 2014 6:40 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs On 2014-01-14 16:04, Collins, Sean wrote: Can we get the -1 from Tail-F cleared from this review? https://review.openstack.org/#/c/56184/17 I've been trying to do this but it fails. Possibly because it is 'Abandoned' ? See below: $ ssh -p 29418 ncsopenstack gerrit review -m 'Clearing out wrong -1 vote ' --verified=0 26a6c6 X11 forwarding request failed on channel 0 error: Change is closed one or more approvals failed; review output above Cheers, Tobbe ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 2014-01-14 16:04, Collins, Sean wrote: Can we get the -1 from Tail-F cleared from this review? https://review.openstack.org/#/c/56184/17 I've been trying to do this but it fails. Possibly because it is 'Abandoned' ? See below: $ ssh -p 29418 ncsopenstack gerrit review -m 'Clearing out wrong -1 vote ' --verified=0 26a6c6 X11 forwarding request failed on channel 0 error: Change is closed one or more approvals failed; review output above Cheers, Tobbe ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
Can we get the -1 from Tail-F cleared from this review? https://review.openstack.org/#/c/56184/17 -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 01/14/2014 10:04 AM, Collins, Sean wrote: Can we get the -1 from Tail-F cleared from this review? https://review.openstack.org/#/c/56184/17 I thought we had confirmed that all Tail-F -1s prior to now had been cleared or only remained on abandoned or merged patches, I guess we missed one. Tail-F is currently disabled for voting verification. I will work on getting this cleared for you Sean, thanks for bringing it to my attention. Thanks, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
Hi all,
going back to the original topic of making the logs public, I have a
question:
how long should the logs be kept? One week? One month?
cheers,
Rossella
On Tue, Jan 7, 2014 at 1:22 PM, Torbjorn Tornkvist kruska...@gmail.comwrote:
My problem seem to be the same as reported here:
https://bitbucket.org/pypa/setuptools/issue/129/assertionerror-egg-info-pkg-info-is-not-a
Not quite shure however how to bring in the fix into my setup.
Cheers, Tobbe
On 2014-01-07 10:38, Torbjorn Tornkvist wrote:
Hi,
Sorry for the problems.
I've missed any direct mails to me (I'm drowning in Openstack mails...)
I will make sure our Jenkins setup won't be left unattended in the future.
How can I remove those '-1' votes?
It seems that from: Jan 2, 2014 5:46:26 PM
after change: https://review.openstack.org/#/c/64696/
something happend that makes the my tox crash with a traceback.
I'll include the traceback below in case someone can give some help.
(I'm afraid I don't know anything about python...)
---
vagrant@quantal64:~/neutron$ sudo tox -e py27 -r --
neutron.tests.unit.ml2.test_mechanism_ncs
GLOB sdist-make: /home/vagrant/neutron/setup.py
py27 create: /home/vagrant/neutron/.tox/py27
ERROR: invocation failed, logfile:
/home/vagrant/neutron/.tox/py27/log/py27-0.log
ERROR: actionid=py27
msg=getenv
cmdargs=['/usr/bin/python2.7',
'/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv.py',
'--setuptools', '--python', '/usr/bin/python2.7', 'py27']
env={'LC_NUMERIC': 'sv_SE.UTF-8', 'LOGNAME': 'root', 'USER': 'root',
'HOME': '/home/vagrant', 'LC_PAPER': 'sv_SE.UTF-8', 'PATH':
'/home/vagrant/neutron/.tox/py27/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games',
'DISPLAY': 'localhost:10.0', 'LANG': 'en_US.utf8', 'TERM':
'xterm-256color', 'SHELL': '/bin/bash', 'LANGUAGE': 'en_US:',
'LC_MEASUREMENT': 'sv_SE.UTF-8', 'SUDO_USER': 'vagrant', 'USERNAME':
'root', 'LC_IDENTIFICATION': 'sv_SE.UTF-8', 'LC_ADDRESS': 'sv_SE.UTF-8',
'SUDO_UID': '1000', 'VIRTUAL_ENV': '/home/vagrant/neutron/.tox/py27',
'SUDO_COMMAND': '/usr/local/bin/tox -e py27 -r --
neutron.tests.unit.ml2.test_mechanism_ncs', 'SUDO_GID': '1000',
'LC_TELEPHONE': 'sv_SE.UTF-8', 'LC_MONETARY': 'sv_SE.UTF-8', 'LC_NAME':
'sv_SE.UTF-8', 'MAIL': '/var/mail/root', 'LC_TIME': 'sv_SE.UTF-8',
'LS_COLORS':
'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01
;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:'}
Already using interpreter /usr/bin/python2.7
New python executable in py27/bin/python2.7
Also creating executable in py27/bin/python
Installing setuptools, pip...
Complete output from command
/home/vagrant/neutron/.tox/py27/bin/python2.7 -c import sys, pip;
pip...ll\] + sys.argv[1:]) setuptools pip:
Traceback (most recent call last):
File string, line 1, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/pip-1.5-py2.py3-none-any.whl/pip/__init__.py,
line 9, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/pip-1.5-py2.py3-none-any.whl/pip/log.py,
line 8, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 2696, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 429, in __init__
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 443, in add_entry
File
Re: [openstack-dev] [Neutron] Availability of external testing logs
Hi,
Sorry for the problems.
I've missed any direct mails to me (I'm drowning in Openstack mails...)
I will make sure our Jenkins setup won't be left unattended in the future.
How can I remove those '-1' votes?
It seems that from: Jan 2, 2014 5:46:26 PM
after change: https://review.openstack.org/#/c/64696/
something happend that makes the my tox crash with a traceback.
I'll include the traceback below in case someone can give some help.
(I'm afraid I don't know anything about python...)
---
vagrant@quantal64:~/neutron$ sudo tox -e py27 -r --
neutron.tests.unit.ml2.test_mechanism_ncs
GLOB sdist-make: /home/vagrant/neutron/setup.py
py27 create: /home/vagrant/neutron/.tox/py27
ERROR: invocation failed, logfile:
/home/vagrant/neutron/.tox/py27/log/py27-0.log
ERROR: actionid=py27
msg=getenv
cmdargs=['/usr/bin/python2.7',
'/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv.py',
'--setuptools', '--python', '/usr/bin/python2.7', 'py27']
env={'LC_NUMERIC': 'sv_SE.UTF-8', 'LOGNAME': 'root', 'USER': 'root',
'HOME': '/home/vagrant', 'LC_PAPER': 'sv_SE.UTF-8', 'PATH':
'/home/vagrant/neutron/.tox/py27/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games',
'DISPLAY': 'localhost:10.0', 'LANG': 'en_US.utf8', 'TERM':
'xterm-256color', 'SHELL': '/bin/bash', 'LANGUAGE': 'en_US:',
'LC_MEASUREMENT': 'sv_SE.UTF-8', 'SUDO_USER': 'vagrant', 'USERNAME':
'root', 'LC_IDENTIFICATION': 'sv_SE.UTF-8', 'LC_ADDRESS': 'sv_SE.UTF-8',
'SUDO_UID': '1000', 'VIRTUAL_ENV': '/home/vagrant/neutron/.tox/py27',
'SUDO_COMMAND': '/usr/local/bin/tox -e py27 -r --
neutron.tests.unit.ml2.test_mechanism_ncs', 'SUDO_GID': '1000',
'LC_TELEPHONE': 'sv_SE.UTF-8', 'LC_MONETARY': 'sv_SE.UTF-8', 'LC_NAME':
'sv_SE.UTF-8', 'MAIL': '/var/mail/root', 'LC_TIME': 'sv_SE.UTF-8',
'LS_COLORS':
'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:'}
Already using interpreter /usr/bin/python2.7
New python executable in py27/bin/python2.7
Also creating executable in py27/bin/python
Installing setuptools, pip...
Complete output from command
/home/vagrant/neutron/.tox/py27/bin/python2.7 -c import sys, pip;
pip...ll\] + sys.argv[1:]) setuptools pip:
Traceback (most recent call last):
File string, line 1, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/pip-1.5-py2.py3-none-any.whl/pip/__init__.py,
line 9, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/pip-1.5-py2.py3-none-any.whl/pip/log.py,
line 8, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 2696, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 429, in __init__
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 443, in add_entry
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 1722, in find_in_zip
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 1298, in has_metadata
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 1614, in _has
File
Re: [openstack-dev] [Neutron] Availability of external testing logs
My problem seem to be the same as reported here:
https://bitbucket.org/pypa/setuptools/issue/129/assertionerror-egg-info-pkg-info-is-not-a
Not quite shure however how to bring in the fix into my setup.
Cheers, Tobbe
On 2014-01-07 10:38, Torbjorn Tornkvist wrote:
Hi,
Sorry for the problems.
I've missed any direct mails to me (I'm drowning in Openstack mails...)
I will make sure our Jenkins setup won't be left unattended in the future.
How can I remove those '-1' votes?
It seems that from: Jan 2, 2014 5:46:26 PM
after change: https://review.openstack.org/#/c/64696/
something happend that makes the my tox crash with a traceback.
I'll include the traceback below in case someone can give some help.
(I'm afraid I don't know anything about python...)
---
vagrant@quantal64:~/neutron$ sudo tox -e py27 -r --
neutron.tests.unit.ml2.test_mechanism_ncs
GLOB sdist-make: /home/vagrant/neutron/setup.py
py27 create: /home/vagrant/neutron/.tox/py27
ERROR: invocation failed, logfile:
/home/vagrant/neutron/.tox/py27/log/py27-0.log
ERROR: actionid=py27
msg=getenv
cmdargs=['/usr/bin/python2.7',
'/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv.py',
'--setuptools', '--python', '/usr/bin/python2.7', 'py27']
env={'LC_NUMERIC': 'sv_SE.UTF-8', 'LOGNAME': 'root', 'USER': 'root',
'HOME': '/home/vagrant', 'LC_PAPER': 'sv_SE.UTF-8', 'PATH':
'/home/vagrant/neutron/.tox/py27/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games',
'DISPLAY': 'localhost:10.0', 'LANG': 'en_US.utf8', 'TERM':
'xterm-256color', 'SHELL': '/bin/bash', 'LANGUAGE': 'en_US:',
'LC_MEASUREMENT': 'sv_SE.UTF-8', 'SUDO_USER': 'vagrant', 'USERNAME':
'root', 'LC_IDENTIFICATION': 'sv_SE.UTF-8', 'LC_ADDRESS':
'sv_SE.UTF-8', 'SUDO_UID': '1000', 'VIRTUAL_ENV':
'/home/vagrant/neutron/.tox/py27', 'SUDO_COMMAND': '/usr/local/bin/tox
-e py27 -r -- neutron.tests.unit.ml2.test_mechanism_ncs', 'SUDO_GID':
'1000', 'LC_TELEPHONE': 'sv_SE.UTF-8', 'LC_MONETARY': 'sv_SE.UTF-8',
'LC_NAME': 'sv_SE.UTF-8', 'MAIL': '/var/mail/root', 'LC_TIME':
'sv_SE.UTF-8', 'LS_COLORS':
'rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01
;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:'}
Already using interpreter /usr/bin/python2.7
New python executable in py27/bin/python2.7
Also creating executable in py27/bin/python
Installing setuptools, pip...
Complete output from command
/home/vagrant/neutron/.tox/py27/bin/python2.7 -c import sys, pip;
pip...ll\] + sys.argv[1:]) setuptools pip:
Traceback (most recent call last):
File string, line 1, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/pip-1.5-py2.py3-none-any.whl/pip/__init__.py,
line 9, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/pip-1.5-py2.py3-none-any.whl/pip/log.py,
line 8, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 2696, in module
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 429, in __init__
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 443, in add_entry
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
line 1722, in find_in_zip
File
/usr/local/lib/python2.7/dist-packages/virtualenv-1.11-py2.7.egg/virtualenv_support/setuptools-2.0.2-py2.py3-none-any.whl/pkg_resources.py,
Re: [openstack-dev] [Neutron] Availability of external testing logs
Hi, Tail-F NCS Jenkins seems to still be causing issues. It voted -1 on some patches today [1][2] which seem to be fine according to all other jobs. It gives no information on what went wrong, so it's essentially a dead end. I've CCed the owner of the job according to the list Anita posted [3], so hopefully they can disable voting. Salvatore mentioned on IRC that it might make sense to ask the infra team to nullify the access credentials for the job if no response is forthcoming from the job owner. Thanks, Dave. [1] https://review.openstack.org/#/c/48574/ [2] https://review.openstack.org/#/c/53052/ [3] https://review.openstack.org/#/admin/groups/91,members On Tue, Dec 31, 2013 at 12:24 PM, Joe Gordon joe.gord...@gmail.com wrote: On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague s...@dague.net wrote: On 12/23/2013 12:10 PM, Collins, Sean wrote: On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote: I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. +1 I've had Tail-F NCS Jenkins -1 some things that the OpenStack Jenkins has +1'd, and other times where I've seen it +1 things that OpenStack Jenkins -1'd. Agreed. I also think we need to have these systems prove themselves on reliability before they post votes back. A mis configured CI system can easily -1 the entire patch stream, and many of us use -Verified-1 as a filter criteria on reviews, which effectively makes that a DOS attack. Detailed public results need to come first. After those look reliable, voting can be allowed. FYI, we are trying to record the requirements at http://ci.openstack.org/third_party.html/, patch: https://review.openstack.org/#/c/63478/ -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
+1 to this, there are IPv6 patches that have been -1'd by this system that I believe prevents them from being reviewed, since most people skip over changes that have a -1 from Jenkins jobs. I also attempted to Reach out mid December to the owner of Tail-F, but have not yet received a response. It is possible that he/she did reply and it got filed in the wrong folder, and I hope this is the case. https://review.openstack.org/#/q/topic:bp/dnsmasq-mode-keyword,n,z Sean M. Collins From: Dave Cahill [dcah...@midokura.com] Sent: Monday, January 06, 2014 4:36 AM To: OpenStack Development Mailing List (not for usage questions) Cc: to...@tail-f.com Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs Hi, Tail-F NCS Jenkins seems to still be causing issues. It voted -1 on some patches today [1][2] which seem to be fine according to all other jobs. It gives no information on what went wrong, so it's essentially a dead end. I've CCed the owner of the job according to the list Anita posted [3], so hopefully they can disable voting. Salvatore mentioned on IRC that it might make sense to ask the infra team to nullify the access credentials for the job if no response is forthcoming from the job owner. Thanks, Dave. [1] https://review.openstack.org/#/c/48574/ [2] https://review.openstack.org/#/c/53052/ [3] https://review.openstack.org/#/admin/groups/91,members On Tue, Dec 31, 2013 at 12:24 PM, Joe Gordon joe.gord...@gmail.commailto:joe.gord...@gmail.com wrote: On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague s...@dague.netmailto:s...@dague.net wrote: On 12/23/2013 12:10 PM, Collins, Sean wrote: On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote: I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. +1 I've had Tail-F NCS Jenkins -1 some things that the OpenStack Jenkins has +1'd, and other times where I've seen it +1 things that OpenStack Jenkins -1'd. Agreed. I also think we need to have these systems prove themselves on reliability before they post votes back. A mis configured CI system can easily -1 the entire patch stream, and many of us use -Verified-1 as a filter criteria on reviews, which effectively makes that a DOS attack. Detailed public results need to come first. After those look reliable, voting can be allowed. FYI, we are trying to record the requirements at http://ci.openstack.org/third_party.html/, patch: https://review.openstack.org/#/c/63478/ -Sean -- Sean Dague Samsung Research America s...@dague.netmailto:s...@dague.net / sean.da...@samsung.commailto:sean.da...@samsung.com http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
Let me know what you consider a reasonable amount of time to continue waiting for Tail-F NCS Jenkins before we remove verification permissions from the account. We were just talking about this a few hours ago at a Birds of a Feather session. We can get permissions removed from this account. I'd just like to see agreement that we have given this account holder a reasonable amount of time to respond prior to doing so. If the account holder of this account is reading this email, responding to it would certainly be a good idea. Thanks, Anita. On 01/06/2014 08:36 PM, Collins, Sean wrote: +1 to this, there are IPv6 patches that have been -1'd by this system that I believe prevents them from being reviewed, since most people skip over changes that have a -1 from Jenkins jobs. I also attempted to Reach out mid December to the owner of Tail-F, but have not yet received a response. It is possible that he/she did reply and it got filed in the wrong folder, and I hope this is the case. https://review.openstack.org/#/q/topic:bp/dnsmasq-mode-keyword,n,z Sean M. Collins From: Dave Cahill [dcah...@midokura.com] Sent: Monday, January 06, 2014 4:36 AM To: OpenStack Development Mailing List (not for usage questions) Cc: to...@tail-f.com Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs Hi, Tail-F NCS Jenkins seems to still be causing issues. It voted -1 on some patches today [1][2] which seem to be fine according to all other jobs. It gives no information on what went wrong, so it's essentially a dead end. I've CCed the owner of the job according to the list Anita posted [3], so hopefully they can disable voting. Salvatore mentioned on IRC that it might make sense to ask the infra team to nullify the access credentials for the job if no response is forthcoming from the job owner. Thanks, Dave. [1] https://review.openstack.org/#/c/48574/ [2] https://review.openstack.org/#/c/53052/ [3] https://review.openstack.org/#/admin/groups/91,members On Tue, Dec 31, 2013 at 12:24 PM, Joe Gordon joe.gord...@gmail.commailto:joe.gord...@gmail.com wrote: On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague s...@dague.netmailto:s...@dague.net wrote: On 12/23/2013 12:10 PM, Collins, Sean wrote: On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote: I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. +1 I've had Tail-F NCS Jenkins -1 some things that the OpenStack Jenkins has +1'd, and other times where I've seen it +1 things that OpenStack Jenkins -1'd. Agreed. I also think we need to have these systems prove themselves on reliability before they post votes back. A mis configured CI system can easily -1 the entire patch stream, and many of us use -Verified-1 as a filter criteria on reviews, which effectively makes that a DOS attack. Detailed public results need to come first. After those look reliable, voting can be allowed. FYI, we are trying to record the requirements at http://ci.openstack.org/third_party.html/, patch: https://review.openstack.org/#/c/63478/ -Sean -- Sean Dague Samsung Research America s...@dague.netmailto:s...@dague.net / sean.da...@samsung.commailto:sean.da...@samsung.com http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 01/06/2014 08:44 AM, Anita Kuno wrote: Let me know what you consider a reasonable amount of time to continue waiting for Tail-F NCS Jenkins before we remove verification permissions from the account. We were just talking about this a few hours ago at a Birds of a Feather session. We can get permissions removed from this account. I'd just like to see agreement that we have given this account holder a reasonable amount of time to respond prior to doing so. If the account holder of this account is reading this email, responding to it would certainly be a good idea. Honestly, I think that 24hrs with no response is reasonable to pull voting. There are substantial negative effects of someone putting -1s without feedback, and not being responsive. So I'd immediately demote the tool and let the author come back and justify why it's working correctly and why it should be allowed to vote again. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
I believe we have more to lose by leaving the job with verification permissions than we do by revoking them, then reinstating them at a later point, since I-2 is at the end of this month. That way patches that are passing the gate and all other third party tests can start being reviewed by more reviewers and core members who have verification set as a filter in their queue, Sean M. Collins From: Anita Kuno [ante...@anteaya.info] Sent: Monday, January 06, 2014 8:44 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs Let me know what you consider a reasonable amount of time to continue waiting for Tail-F NCS Jenkins before we remove verification permissions from the account. We were just talking about this a few hours ago at a Birds of a Feather session. We can get permissions removed from this account. I'd just like to see agreement that we have given this account holder a reasonable amount of time to respond prior to doing so. If the account holder of this account is reading this email, responding to it would certainly be a good idea. Thanks, Anita. On 01/06/2014 08:36 PM, Collins, Sean wrote: +1 to this, there are IPv6 patches that have been -1'd by this system that I believe prevents them from being reviewed, since most people skip over changes that have a -1 from Jenkins jobs. I also attempted to Reach out mid December to the owner of Tail-F, but have not yet received a response. It is possible that he/she did reply and it got filed in the wrong folder, and I hope this is the case. https://review.openstack.org/#/q/topic:bp/dnsmasq-mode-keyword,n,z Sean M. Collins From: Dave Cahill [dcah...@midokura.com] Sent: Monday, January 06, 2014 4:36 AM To: OpenStack Development Mailing List (not for usage questions) Cc: to...@tail-f.com Subject: Re: [openstack-dev] [Neutron] Availability of external testing logs Hi, Tail-F NCS Jenkins seems to still be causing issues. It voted -1 on some patches today [1][2] which seem to be fine according to all other jobs. It gives no information on what went wrong, so it's essentially a dead end. I've CCed the owner of the job according to the list Anita posted [3], so hopefully they can disable voting. Salvatore mentioned on IRC that it might make sense to ask the infra team to nullify the access credentials for the job if no response is forthcoming from the job owner. Thanks, Dave. [1] https://review.openstack.org/#/c/48574/ [2] https://review.openstack.org/#/c/53052/ [3] https://review.openstack.org/#/admin/groups/91,members On Tue, Dec 31, 2013 at 12:24 PM, Joe Gordon joe.gord...@gmail.commailto:joe.gord...@gmail.com wrote: On Mon, Dec 23, 2013 at 11:13 AM, Sean Dague s...@dague.netmailto:s...@dague.net wrote: On 12/23/2013 12:10 PM, Collins, Sean wrote: On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote: I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. +1 I've had Tail-F NCS Jenkins -1 some things that the OpenStack Jenkins has +1'd, and other times where I've seen it +1 things that OpenStack Jenkins -1'd. Agreed. I also think we need to have these systems prove themselves on reliability before they post votes back. A mis configured CI system can easily -1 the entire patch stream, and many of us use -Verified-1 as a filter criteria on reviews, which effectively makes that a DOS attack. Detailed public results need to come first. After those look reliable, voting can be allowed. FYI, we are trying to record the requirements at http://ci.openstack.org/third_party.html/, patch: https://review.openstack.org/#/c/63478/ -Sean -- Sean Dague Samsung Research America s...@dague.netmailto:s...@dague.net / sean.da...@samsung.commailto:sean.da...@samsung.com http://dague.net ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http
Re: [openstack-dev] [Neutron] Availability of external testing logs
Hi guys, On 6 January 2014 14:44, Anita Kuno ante...@anteaya.info wrote: If the account holder of this account is reading this email, responding to it would certainly be a good idea. Apologies for the disturbance! Please do go ahead and disable the voting rights while we work out what's going wrong and get the voting to work reliably. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
How should we handle existing -1's that have been posted? -- Sean M. Collins ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 6 January 2014 18:12, Collins, Sean sean_colli...@cable.comcast.com wrote: How should we handle existing -1's that have been posted? I suggest removing/ignoring those votes until we see if they are spurious. The Tail-f NCS plugin is very simple code and I'd say it's unlikely that any recent changes will have broken it in a non-trivial way. Probably we will find there is no serious issue and it's only teething problems on the test integration. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 01/06/2014 10:32 PM, Luke Gorrie wrote: Hi guys, On 6 January 2014 14:44, Anita Kuno ante...@anteaya.info wrote: If the account holder of this account is reading this email, responding to it would certainly be a good idea. Apologies for the disturbance! Please do go ahead and disable the voting rights while we work out what's going wrong and get the voting to work reliably. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Verification voting for https://review.openstack.org/#/dashboard/9695 has been revoked. Also, future 3rd party testing accounts will have verification voting turned off by default. Third party testing systems will have to earn the trust of the community in order to have verification voting turned on. We are still hashing out the definition of what it takes to earn trust, but a desire to be worthy of trust certainly goes a long way. There is a conversation happening about requirements for 3rd party tests right here. [0] I strongly encourage your participation and continued awareness of the discussion and the resultant consequences. Thank you to all who are actively participating in this process, Anita. [0] https://review.openstack.org/#/c/63478/ ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 01/07/2014 02:31 AM, Luke Gorrie wrote: On 6 January 2014 18:12, Collins, Sean sean_colli...@cable.comcast.com wrote: How should we handle existing -1's that have been posted? I suggest removing/ignoring those votes until we see if they are spurious. I is my belief that Sean is asking for these votes to be removed. It is also my belief that the account that voted -1 is the only one that can change the vote. I think you are being asked to clean up after yourself. That is the way I am reading it. Doing so would certainly help the whole we are worthy of your trust issue for your account, when you would like verification voting enabled. Thanks, Anita. The Tail-f NCS plugin is very simple code and I'd say it's unlikely that any recent changes will have broken it in a non-trivial way. Probably we will find there is no serious issue and it's only teething problems on the test integration. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 12/22/2013 06:30 AM, Salvatore Orlando wrote: Hi, The patch: https://review.openstack.org/#/c/63558/ failed mellanox external testing. Subsequent patch sets have not been picked up by the mellanox testing system. I would like to see why the patch failed the job; if it breaks mellanox plugin for any reason, I would be happy to fix it. However, the logs are not publicly accessible. I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. +1! -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
On 12/23/2013 12:10 PM, Collins, Sean wrote: On Sun, Dec 22, 2013 at 12:30:50PM +0100, Salvatore Orlando wrote: I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. +1 I've had Tail-F NCS Jenkins -1 some things that the OpenStack Jenkins has +1'd, and other times where I've seen it +1 things that OpenStack Jenkins -1'd. Agreed. I also think we need to have these systems prove themselves on reliability before they post votes back. A mis configured CI system can easily -1 the entire patch stream, and many of us use -Verified-1 as a filter criteria on reviews, which effectively makes that a DOS attack. Detailed public results need to come first. After those look reliable, voting can be allowed. -Sean -- Sean Dague Samsung Research America s...@dague.net / sean.da...@samsung.com http://dague.net signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Neutron] Availability of external testing logs
Thanks for the clarification Roey. Have a good day, Salvatore On 22 December 2013 14:18, Roey Chen ro...@mellanox.com wrote: Hi, The patch failed due to external-testing setup issues, This is why its currently disabled and no subsequent patch sets were picked. All apologies, Roey Chen *From:* Salvatore Orlando [mailto:sorla...@nicira.com] *Sent:* Sunday, December 22, 2013 1:35 PM *To:* OpenStack Development Mailing List *Subject:* [openstack-dev] [Neutron] Availability of external testing logs Hi, The patch: https://review.openstack.org/#/c/63558/ failed mellanox external testing. Subsequent patch sets have not been picked up by the mellanox testing system. I would like to see why the patch failed the job; if it breaks mellanox plugin for any reason, I would be happy to fix it. However, the logs are not publicly accessible. I would suggest that external jobs should not vote until logs are publicly accessible, otherwise contributors would have no reason to understand where the negative vote came from. Regards, Salvatore ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
