David Scravaglieri <[email protected]> writes:
> On Tue, Oct 6, 2015 at 5:50 PM, Kan-Ru Chen (陳侃如) <[email protected]> wrote:
>
>> David Scravaglieri <[email protected]> writes:
>>
>> > ▾ Automation
>> > • Create a test matrix to define which tests are running on which
>> > platform (Device, Mulet, Emulator)
>>
>> All tests? The most interesting data I'd like to see is which tests are
>> effectively disabled on all platforms. This kind of fallout could go
>> unnoticed and bite us when code breaks (for example some Nuwa tests).
>>
>
> It seems that not all tests make sense to be executed on every platform,
> having a test matrix will help to keep track on which tests are running and
> where.
I agree that it is helpful but there are so many tests that I think it
would be hard to put into a matrix. No objections if there is a good way
to present the data.
>> > • Emulator-x86-KK
>> > Activate emulator-x86-kk on Treeherder, run Gecko unit tests and Gij
>> tests
>> > • Emulator-x86-L
>> > Start porting emulator to L and activate it on Treeherder
>>
>> Are we going to run emulator-x86 and emulator-arm side by side or just
>> -x86?
>>
>
> I do not see value on having emulator-arm still running once we will get
> emulator-x86. Am I wrong ?
Emulator-x86 used to have less upstream support but I don't know what's
the current situation. We may also miss some bugs that only appears on
code compiled to ARM, but I think it's rare.
Kanru
_______________________________________________
dev-fxos mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-fxos
