Closed Bug 800047 Opened 8 years ago Closed 8 years ago

Distinguish between Android Tegra test runs and Android Panda test runs on TBPL

Categories

(Tree Management Graveyard :: TBPL, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: cmtalbert, Assigned: emorley)

References

Details

Attachments

(2 files)

As we are getting ready to turn on Fennec tests on Panda hardware to test Android 4.0 we need to figure out how to display those results on TBPL in a way that won't be confusing.

I propose listing the OS version in the row header for each run, i.e.:
The exsting Tegra Row looks like:
Android opt B M(1 2 3 ...)

I propose we do this for the Tegra runs:
Android 2.2 opt B M(1 2 3...)

And for pandas:
Android 4.0 opt M(1 2 3...)

Note that pandas will run the same build of Fennec that Tegras run, so the panda line will only contain tests.

If we want to be consistent as we do this we should add the '2.2' designation to all the lines running tests on tegras (which would change AndroidNoIon opt and Android ARMv6 opt to AndroidNoIon 2.2 opt and Android ARMv6 2.2 opt respectively).

I think keeping it consistent makes the most sense.

Any other proposals?
I just need the buildername format for these tests.

Android on tegra is of form:

Android Tegra 250 mozilla-central opt test mochitest-3
Android Armv6 Tegra 250 mozilla-central opt test mochitest-8
etc
Assignee: nobody → bmo
Status: NEW → ASSIGNED
Flags: needinfo?(ctalbert)
OS: Windows 7 → All
Hardware: x86_64 → All
And sorry, meant to say I like the proposal - consistency makes me happy :-)
Flags: needinfo?(ctalbert) → needinfo?(catlee)
Sounds ok to me. Should we change the buildbot names as well, or can that mapping live in TBPL?
Flags: needinfo?(catlee)
(In reply to Chris AtLee [:catlee] from comment #3)
> Sounds ok to me. Should we change the buildbot names as well, or can that
> mapping live in TBPL?

As long as I have a way of differentiating them, then I'm happy for the mapping to just exist in TBPL for now (though if related cleanup is done later, wouldn't hurt to make things consistent in the buildbot-configs too).

The need info was for the buildernames for the test runs done on the pandaboards - do you know what they are?
No, I don't. AFAIK they haven't been created yet. Do you have a preference?
(In reply to Chris AtLee [:catlee] from comment #5)
> No, I don't. AFAIK they haven't been created yet. Do you have a preference?

Hmm perhaps:
Android 4.0 Panda [mozilla-central opt test mochitest-3]

And then at some point in the future (in another bug), we could change the tegras from:
Android {Armv6,no-ionmonkey} Tegra 250 mozilla-central opt test mochitest-8
to:
Android 2.2 {Armv6,no-ionmonkey} Tegra 250 mozilla-central opt test mochitest-8
...and at least the new mapping chosen here will align with that.
catlee, does the naming proposal in comment 6 sound ok to you? If so, I can add support to TBPL pre-emptively :-)
I really dislike the mismatch between the long descriptive builder names and the shorter names that are used on the build slaves as part of the directory structure.

This is what bug 586664 is all about.

So, I'd rather these be named something like 
b2g_mozilla-central_panda_opt-test-mochitest-3
(In reply to Chris AtLee [:catlee] from comment #8)
> I really dislike the mismatch between the long descriptive builder names and
> the shorter names that are used on the build slaves as part of the directory
> structure.
> 
> This is what bug 586664 is all about.
> 
> So, I'd rather these be named something like 
> b2g_mozilla-central_panda_opt-test-mochitest-3

Was this comment meant for bug 789652?
Attached patch Patch v1Splinter Review
* Displays the current Android builds as 2.2, with support for when we switch the buildernames to explicitly state 2.2.
* Adds support for the future "Android 4.0" buildernames.
* Widens the OS column so the longer OS captions fit.

I will file a separate bug for changing the current buildernames to state 'Android 2.2'. 

Whichever bug adds support for running tests on the Panda boards will need to ensure the buildername starts with "Android 4.0" (I can't find an open dependant of bug 725544 that appears to be doing this, or I'd add a note about what string is desired).
Attachment #675254 - Flags: review?(catlee)
Attached image Screenshot
In which bug are the buildernames going to be set? I've looked through the dependency tree of bug 725544 and can't see if the buildbot-configs part has been filed yet.
Blocks: 803248
Attachment #675254 - Flags: review?(catlee) → review+
Whiteboard: [needs push to production]
Blocks: 808718
In production :-)
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
No longer blocks: 808718
Depends on: 808718
Whiteboard: [needs push to production]
Blocks: 823900
Product: Webtools → Tree Management
Product: Tree Management → Tree Management Graveyard
You need to log in before you can comment on or make changes to this bug.