On 2016年09月23日 03:01, Andrew McKay wrote:
> Just a note that https://bugzilla.mozilla.org/show_bug.cgi?id=1303418
> is about to land and this will prevent an add-on upgrade changing the
> ID of the add-on. That's not happening in this case (the code hasn't
> landed), but just a heads up on a similar front.
Thank you for the heads up.
However, I am a mere user of TB trying to fix a few performance issues and
annoying bugs in TB, and so
the intricacies of the processing here escapes me a little bit :-)
> On 22 September 2016 at 01:33, Mark Banner <mban...@mozilla.com> wrote:
>> On 22/09/2016 08:44, ISHIKAWA,chiaki wrote:
>>> 3:07:56 INFO - 1474488476446 addons.xpi-utils WARN
>>> addMetadata: Add-on specialpow...@mozilla.org is invalid: Error: Invalid
>>> addon ID: expected addon ID specialpow...@mozilla.org, found
>>> special-pow...@mozilla.org in manifest ...
>>> I am not sure if this comes from the intended test.
>>> Rather it looks a configuration error.
>>> The error line seems to appear at beginning of the selected run of each
>>> test directory.
>>> cf. 3 results from the comm-central tree:
>>> ♢7 XPI_PKGNAME = specialpow...@mozilla.org
>> Looks like this is different from what is specified in
>> testing/specialpowers/install.rdf - which is the dashed version, and was
>> introduced when it was rewritten last year.
>> The simplest thing is probably to change the install.rdf to remove the dash
>> as then it wouldn't be changing the file name on disk - and also update the
>> other couple of instances in the tree. Probably worth a running through a
>> few tests on try just to make sure as well.
>> The test infrastructure has probably got away with it due to the next
>> warning of "Could not uninstall invalid item from locked install location",
>> so it kept on using it.
dev-platform mailing list