Closed Bug 1190907 Opened 8 years ago Closed 8 years ago

Error running talos


(Testing :: Talos, defect)

Not set


(Not tracked)



(Reporter: BenWa, Assigned: parkouss)




(3 files, 1 obsolete file)

Attached file log
I get this log running python using the latest tip of talos.
this looks like our unintentional dependencies on odd packages.  There is a patch to remove this dependency, I suspect it is ready to land. :parkouss, let me know what I can do to help get the mozlog removal patch landed :)
Flags: needinfo?(j.parkouss)
It's on try in bug 1189714, we should be able to land that soon.
Depends on: 1189714
Flags: needinfo?(j.parkouss)
See Also: → 1189847
This should be better now - Benoit, can you confirm ?
Flags: needinfo?(bgirard)
Attached file log2
Doesn't appear to be as of b6589aef27a5.
Flags: needinfo?(bgirard)
Indeed, there are other errors now. mozlog is required everywhere, and with >= VERSION. As mozversion 3.0 is available but not compatible with the talos dependencies, this ends up in a mess.

We should update our dependencies of talos to the latest versions of mozbase.
Depends on: 1190265
Attached patch deps_temp_fix.patch (obsolete) — Splinter Review
As a temporary workaround, we could apply that patch. This give us time to fix dependencies issues and should allow trys to work also.

jmaher, do you mind pushing this to a simple try (just to check that mozdevice==0.29) is available on internal pypi ?

With this patch, it works well locally for me now.
Assignee: nobody → j.parkouss
Attachment #8643504 - Flags: review?(jmaher)
Comment on attachment 8643504 [details] [diff] [review]

Review of attachment 8643504 [details] [diff] [review]:

this looks great and a reasonable fix.  We do need to test this carefully on try.
Attachment #8643504 - Flags: review?(jmaher) → review+
Some errors on try, because mozdevice 0.29 not in internal pypi. :) So I asked on rely, what is available is here:

so I updated to use mozdevice==0.40 and re-run failed jobs (20).
asked on #releng*
Running pretty good so far, except for g2 tests that are busted again.

Benoit, could that be a side effect of a6529a8 or 582072d ?
updating the patch to make it works locally and on try (this is what was tested on try).

I think we are good to land this now.
Attachment #8643504 - Attachment is obsolete: true
Attachment #8644275 - Flags: review+
Soory no, we should not. mozdevice 0.40 requires mozlog 3.0, so it fails locally. I have to find another one.
If I require mozdevice==0.26, I get:

pkg_resources.VersionConflict: (mozdevice 0.26 (/home/jp/dev/talos/venv2/lib/python2.7/site-packages), Requirement.parse('mozdevice>=0.29'))

If I require mozdevice==0.40 or no mozdevice, we have mozlog errors, and there is no other versions in internal pypi so I am a bit blocked.

Let's wait for talos to use new packages, that will fix everything. In the mean time I updated mozversion to not require mozdevice (bug 1189847). It is already on pypi, but not on internal packages. We are waiting some marionette packages with whimboo to ask internal mirroring (multiple packages in one go).

So, forget about the patch here - talos local is broken until that. Note that you should be able to run:

python talso/ directly as a temporary workaround.
landed this temporary dependency fix on the talos branch:
FYI: I have one of the version posted after Comment 4 locally and it works.
ok, this is working good and deployed!
Closed: 8 years ago
Resolution: --- → FIXED
FYI, now the mozbase dependencies have been updated with bug 1190265, so should be good without local patches now. :)
You need to log in before you can comment on or make changes to this bug.