Closed
Bug 683901
Opened 13 years ago
Closed 13 years ago
Inconsistent versions of Mozmill being reported in JSON report
Categories
(Mozilla QA Graveyard :: Infrastructure, defect)
Mozilla QA Graveyard
Infrastructure
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: u279076, Unassigned)
References
()
Details
Some reports in the daily testruns are showing old versions of Mozmill. If these testruns are actually using older versions of Mozmill to test, this could be causing intermittent failures. Here are some example reports: http://mozmill-release.brasstacks.mozilla.com/#/functional/report/722442d6c697a4301a59e4e1795de27f http://mozmill-release.brasstacks.mozilla.com/#/functional/report/722442d6c697a4301a59e4e1792bfabe http://mozmill-release.brasstacks.mozilla.com/#/functional/report/722442d6c697a4301a59e4e1795db0be Current version should be Mozmill 1.5.4
Comment 1•13 years ago
|
||
Those are not reports from the daily testrun but from our release testing on qa-set or qa-masterblaster. Please CC me the next time when there is something broken related to Mozmill and which gots filed into the infrastructure component. Thanks.
Summary: Inconsistent versions of Mozmill being reported in dailies → Inconsistent versions of Mozmill being reported (qa-set/masterblaster)
Comment 2•13 years ago
|
||
This issue is basically a failure in Mozmill core when we retrieve the version name from the package index:
version = pkg_resources.get_distribution('mozmill').version
>>> import pkg_resources
>>> version = pkg_resources.get_distribution('mozmill').version
>>> print version
1.5.2
$ mozmill --version
mozmill-script.py 1.5.4
Not sure yet, if this is related to how you upgrade Mozmill, i.e. easy_install vs. pip.
Moving over to mozmill core.
Blocks: 636746
Component: Infrastructure → Mozmill
Product: Mozilla QA → Testing
QA Contact: infrastructure → mozmill
Whiteboard: [mozmill-1.5.5?]
Updated•13 years ago
|
Summary: Inconsistent versions of Mozmill being reported (qa-set/masterblaster) → Inconsistent versions of Mozmill being reported in JSON report
Comment 3•13 years ago
|
||
I'm not convinced this is a mozmill bug versus a bad environment that bugs in setuptools/easy_install/pip can't deal with. Using the pypi version, I do not see this behaviour: virtualenv.py tmp cd tmp/ easy_install mozmill (tmp)│python -c 'import mozmill; print mozmill.__file__' /home/jhammel/tmp/lib/python2.6/site-packages/mozmill-1.5.4-py2.6.egg/mozmill/__init__.pyc (tmp)│mozmill --version mozmill 1.5.4
Comment 4•13 years ago
|
||
So there is clearly a different behavior between --version and the version reported in the JSON report. I have checked our three machines where it occurred but I was not able to find it out. The issue has been resolved automatically once I have modified the __init__.py file. Could really be that we are facing an issue with even Python here. Moving back to infrastructure and marking as fixed now that all VMs on qa-set are reporting the right version. I don't have time to debug that further for now. If it happens again we can continue.
Status: NEW → RESOLVED
Closed: 13 years ago
Component: Mozmill → Infrastructure
Product: Testing → Mozilla QA
QA Contact: mozmill → infrastructure
Resolution: --- → FIXED
Whiteboard: [mozmill-1.5.5?]
Updated•6 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•