On 20/04/16 14:13, Nathan Froyd wrote:
On Wed, Apr 20, 2016 at 8:59 AM, James Graham wrote:
On 20/04/16 13:53, Josh Matthews wrote:
Servo has a script [1] that runs on the build machine that executes
--manifest-update and checks whether the contents of MANFEST.json is
On Wed, Apr 20, 2016 at 8:59 AM, James Graham wrote:
> On 20/04/16 13:53, Josh Matthews wrote:
>> Servo has a script [1] that runs on the build machine that executes
>> --manifest-update and checks whether the contents of MANFEST.json is
>> different before and after. We
On 20/04/16 13:53, Josh Matthews wrote:
Servo has a script [1] that runs on the build machine that executes
--manifest-update and checks whether the contents of MANFEST.json is
different before and after. We could do the same for Gecko and make it
turn the job orange on treeherder.
I plan to
Servo has a script [1] that runs on the build machine that executes
--manifest-update and checks whether the contents of MANFEST.json is
different before and after. We could do the same for Gecko and make it
turn the job orange on treeherder.
Cheers,
Josh
[1]
Hi all,
For web-platform-test, it seems some people still update manifest.json
manually, instead of running "--manifest-update" mach command. Running
"--manifest-update" assures the manifest to be in lexicographic order;
however, manually updating manifest may sometimes accidentally add test
info
5 matches
Mail list logo