Status

()

enhancement
P2
normal
a year ago
9 months ago

People

(Reporter: glandium, Assigned: glandium)

Tracking

(Depends on 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

a year ago
For some reason, GNU as is not happy with the assembly generated after bug 1238661 anymore on Debian armel.

OTOH, as mentioned in bug 1238661 comment 4, we actually don't need this workaround anymore, so let's just kill it.
Comment hidden (mozreview-request)
(Assignee)

Updated

a year ago
Attachment #8979154 - Flags: review?(nchen)

Comment 2

a year ago
mozreview-review
Comment on attachment 8979154 [details]
Bug 1463035 - Remove MOZ_SIGNAL_TRAMPOLINE.

https://reviewboard.mozilla.org/r/245410/#review251496
Attachment #8979154 - Flags: review?(nchen) → review+

Comment 3

a year ago
Pushed by mh@glandium.org:
https://hg.mozilla.org/integration/autoland/rev/98e368b5c4be
Remove MOZ_SIGNAL_TRAMPOLINE. r=jchen
(Assignee)

Comment 5

a year ago
WTH?
Flags: needinfo?(mh+mozilla) → needinfo?(nchen)
(Assignee)

Comment 6

a year ago
[task 2018-05-21T23:58:29.010Z] 23:58:29     INFO -  Operating system: Android
[task 2018-05-21T23:58:29.010Z] 23:58:29     INFO -                    0.0.0 Linux 2.6.29-gea477bb #1 Wed Sep 26 11:04:45 PDT 2012 armv7l

OMG why are we running tests on images using such an old kernel!?
Sounds like it might be time to switch to a newer AVD
Flags: needinfo?(nchen) → needinfo?(gbrown)
Priority: -- → P2
We went a long time (a couple of years?) where newer versions of the emulator were not compatible with aws, and it was not possible (certainly not straight-forward) to update the avd system images without updating the emulator. Now, it is possible to upgrade the emulator and avd, but last I checked, for armv7/4.3, the result was over-all slightly slower than the existing version, introduced many reftest and a few mochitest failures, and offered no known advantages over the existing setup. I need to check on that again - bug 1455485 - but first I need to figure out what's wrong with the latest emulator - bug 1463909. For geckoview, we intend to get around this nonsense by running geckoview tests on a kvm-accelerated x86 emulator running Android 7.0: bug 1460411. But little consideration has been given to updating the existing Firefox for Android test environment, beyond, "let's see how that geckoview plan works out".

I guess I'm saying: This is an inconvenient time to update the Firefox for Android test environment, and it is not easy. How important and urgent is an OS update? Also, what is the minimum target version, or how can I determine if a given Android is helpful to this bug?
Flags: needinfo?(gbrown)
(Assignee)

Updated

a year ago
Flags: needinfo?(nchen)
(In reply to Geoff Brown [:gbrown] from comment #8)
> I guess I'm saying: This is an inconvenient time to update the Firefox for
> Android test environment, and it is not easy. How important and urgent is an
> OS update? Also, what is the minimum target version, or how can I determine
> if a given Android is helpful to this bug?

I think we just need something with a newer kernel than 2.6.29. For example, the mozemulator-4.3 AVD (from `mach android-emulator` but not used in automation) has a newer 3.4.67 kernel.
Flags: needinfo?(nchen) → needinfo?(gbrown)
Thanks. Let's discuss next steps for an android upgrade in bug 1455485.
Flags: needinfo?(gbrown)
(Assignee)

Updated

a year ago
Depends on: 1455485
Duplicate of this bug: 1434526
You need to log in before you can comment on or make changes to this bug.