Closed Bug 2049686 Opened 4 months ago Closed 4 months ago

Update docker for Android CaR

Categories

(Testing :: Performance, defect, P1)

defect

Tracking

(firefox154 fixed)

RESOLVED FIXED
154 Branch
Tracking Status
firefox154 --- fixed

People

(Reporter: kshampur, Assigned: kshampur)

References

Details

(Whiteboard: [fxp][operational][1d])

Attachments

(1 external file)

Similar to Bug 2047831, the issue might be the same

Fixes android-custom-car toolchain builds failing because
v8_context_snapshot_generator couldn't load libx11.so.6 at runtime.

The generator is a host x64 binary that runs during the Android
cross-compile. The linux64 docker image already had a full set of x11
runtime libs; the android one didn't. Rather than add just the one
missing lib, this patch brings the android image up to the same set as
linux64.

Attachment #9600337 - Attachment description: WIP: Bug 2049686 - Update docker for Android CaR r?#perftest → Bug 2049686 - Update docker for Android CaR r?#perftest

kshampur could this have been missclassified as an p1/s1(incident level). If so, could you change it and do you still need tracking ?

Flags: needinfo?(kshampur)

(In reply to Dianna Smith [:diannaS] from comment #3)

kshampur could this have been missclassified as an p1/s1(incident level). If so, could you change it and do you still need tracking ?

Hi Dianna, our team uses priority and severity fields for our own internal task tracking in the Testing :: Performance component. We were under the impression that Testing components were not being monitored by RelMan/ or anyone outside the team.

Could you share more context on your question? In the meantime, for this specific bug, it blocks all Android CaR tests with no workaround available, which per the severity definitions does seem to fit S1 https://wiki.mozilla.org/BMO/UserGuide/BugFields#bug_severity unless we should be going about this differently?

Flags: needinfo?(kshampur)

Hey! The tracking flags for 154 and 153 were set to ? which gets sent to our queue for tracking for releases. (this might of have been automatic for S1/P1) I think if those had not been set, it would be okay.

Status: ASSIGNED → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch

(In reply to Dianna Smith [:diannaS] from comment #5)

Hey! The tracking flags for 154 and 153 were set to ? which gets sent to our queue for tracking for releases. (this might of have been automatic for S1/P1) I think if those had not been set, it would be okay.

Thanks for the context! I didn't catch that and didn't even realize it gets set. Is this default behaviour? Eitherway I'll communicate this to my team to clear those tracking flags going forward in case it happens (or some other solution)

Good to know it was that rather than the severity/priority ratings themselves. Sorry you got pulled into this due to that!

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: