910196 - B2G build failure messages are often non-existent & as such difficult to sheriff

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: GonkIntegration, defect)

Description

[Ed Morley [:emorley]]

Sheriffing B2G builds/tests is already pretty frustrating, given that other than gaia (and even then, not all the time for gaia), all other repos pull from tip, so the changeset that resulted in a broken build is frequently hard to find.

This is made worse, by the failure message in the case of a broken build being ambiguous at best and often non-existent.

eg:
https://tbpl.mozilla.org/php/getParsedLog.php?id=27112033&tree=Mozilla-Central

Other than these failure lines:
{
04:51:29     INFO -  Finished: bootstrapping test proxies/sandboxes
04:51:30     INFO -  Finished: test ui config file: ./test_apps/test-agent/config.json
04:51:30     INFO -  run-js-command  webapp-manifests
04:51:30     INFO -  run-js-command  webapp-optimize
04:51:30    ERROR -  make[1]: *** [webapp-optimize] Error 3
04:51:30     INFO -  make[1]: Leaving directory `/builds/slave/b2g_m-cen_leo_dep-000000000000/build/gaia'
04:51:30     INFO -  make: *** [gaia/profile.tar.gz] Error 2
04:51:30     INFO -  real	10m33.375s
04:51:30     INFO -  user	7m42.997s
04:51:30     INFO -  sys	1m41.934s
04:51:30     INFO -  
04:51:30     INFO -  > Build failed! <
04:51:30     INFO -  Build with |./build.sh -j1| for better messages
04:51:30     INFO -  If all else fails, use |rm -rf objdir-gecko| to clobber gecko and |rm -rf out| to clobber everything else.
04:51:30    ERROR - Return code: 2
}

There is nothing else to say what actually failed (to my eyes at least).

In the example above, the failure was resolved by backing out bug 903913.

Please can we improve this somehow? :-)

Comment 1

[Ed Morley [:emorley]]

(In reply to Ed Morley [:edmorley UTC+1] from comment #0)
> In the example above, the failure was resolved by backing out bug 903913.

Though that didn't fix the problem, so then tried backing out bug 904068.