966883 - B2G emulator tests are broken on Pine and Cedar

Status: RESOLVED FIXED

(Release Engineering :: General, defect)

Description

[Gregor Wagner [:gwagner]]

We need this up and running asap again please.

https://tbpl.mozilla.org/?tree=Pine&showall=1

22:18:12     INFO - Copy/paste: /builds/slave/test/build/venv/bin/mozinstall --app b2g /builds/slave/test/build/emulator.tar.gz --destination /builds/slave/test/build/application
22:18:21    ERROR - Errors received:
22:18:21     INFO - Reading from file tmpfile_stderr
22:18:21    ERROR -  Traceback (most recent call last):
22:18:21    ERROR -    File "/builds/slave/test/build/venv/bin/mozinstall", line 9, in <module>
22:18:21    ERROR -      load_entry_point('mozInstall==1.8', 'console_scripts', 'mozinstall')()
22:18:21    ERROR -    File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/mozinstall/mozinstall.py", line 301, in install_cli
22:18:21    ERROR -      binary = get_binary(install_path, app_name=options.app)
22:18:21    ERROR -    File "/builds/slave/test/build/venv/local/lib/python2.7/site-packages/mozinstall/mozinstall.py", line 88, in get_binary
22:18:21    ERROR -      raise InvalidBinary('"%s" does not contain a valid binary.' % path)
22:18:21    ERROR -  mozinstall.mozinstall.InvalidBinary: "/builds/slave/test/build/application/b2g-distro" does not contain a valid binary.
22:18:21     INFO - retry: Calling <built-in function remove> with args: ('tmpfile_stderr',), kwargs: {}, attempt #1
22:18:21     INFO - retry: Calling <built-in function remove> with args: ('tmpfile_stdout',), kwargs: {}, attempt #1
22:18:21    ERROR - Return code: 1
22:18:21    FATAL - Halting on failure while running ['/builds/slave/test/build/venv/bin/mozinstall', '--app', 'b2g', '/builds/slave/test/build/emulator.tar.gz', '--destination', '/builds/slave/test/build/application']
22:18:21    FATAL - Running post_fatal callback...
22:18:21    FATAL - Exiting 1

Comment 1

[Phil Ringnalda (:philor)]

Not quite sure why, other than perhaps an unread copy-paste, Pine's running on mozharness default.

Comment 2

[Andrew Halberstadt [:ahal]]

I believe this is from bug 965588. I backed it out in https://hg.mozilla.org/build/mozharness/rev/1498c10c0430

Comment 3

[Andrew Halberstadt [:ahal]]

The job I re-triggered on Pine is green.

Comment 4

[Phil Ringnalda (:philor)]

But is there any actual reason besides "the config was created by copy-paste from Cedar" to have Pine running on default rather than production?

Comment 5

[Ed Morley [:emorley]]

(In reply to Phil Ringnalda (:philor) from comment #4)
> But is there any actual reason besides "the config was created by copy-paste
> from Cedar" to have Pine running on default rather than production?

Pine was loaned in bug 929203 - it wasn't explicitly requested.

Gregor, could you confirm whether you would like Pine to track mozharness production or default? I'd suggest the former unless many of your changes to green up b2g debug require mozharness landings.

Comment 6

[Gregor Wagner [:gwagner]]

(In reply to Ed Morley [:edmorley UTC+0] from comment #5)
> (In reply to Phil Ringnalda (:philor) from comment #4)
> > But is there any actual reason besides "the config was created by copy-paste
> > from Cedar" to have Pine running on default rather than production?
> 
> Pine was loaned in bug 929203 - it wasn't explicitly requested.
> 
> Gregor, could you confirm whether you would like Pine to track mozharness
> production or default? I'd suggest the former unless many of your changes to
> green up b2g debug require mozharness landings.

I don't really know what this implies but when it is about taking the current build flags from b2g-inbound then I would say yes I rather have production mozharness.