674855 - Android reftests permaorange after ndk changes

Status: RESOLVED DUPLICATE of bug 674837

(Release Engineering :: General, defect)

Description

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

After bug 657723 was deployed we started having 2 issues:

1. a bunch of Android builds started failing on configure. This may be expected due to the change I guess

2. Reftests R1 and R2 are now permaorange. This happens on all trees and is confusing people (I see retriggered reftests on try, useless backouts and such).

For now they should probably be hidden from all trees till someone figures out what differs from before.

Comment 1

[Marco Bonardo [:mak] (Away Apr 25 - May 5)]

may be due to bug 674837, Glandium is going to push to try and check

Comment 2

[Mike Hommey [:glandium]]

(In reply to comment #0)
> After bug 657723 was deployed we started having 2 issues:
> 
> 1. a bunch of Android builds started failing on configure. This may be
> expected due to the change I guess

It is, unfortunately. Though the bots were supposed to have been clobbered.

> 2. Reftests R1 and R2 are now permaorange. This happens on all trees and is
> confusing people (I see retriggered reftests on try, useless backouts and
> such).

Most likely, that's because of bug 674837. Verifying on try:
http://tbpl.mozilla.org/?tree=Try&rev=0ef7009173cf

Comment 3

[[e-mail] (:bhearsum)]

Glandium sez this is a dupe