Closed Bug 657357 Opened 14 years ago Closed 14 years ago

Android unit tests not run on specified build

Categories

(Release Engineering :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 655046

People

(Reporter: jrmuizel, Assigned: armenzg)

Details

(Whiteboard: [buildduty])

This build should've produced a reftest run but did not: http://tbpl.mozilla.org/?tree=Try&rev=df930499a74c
Assignee: nobody → armenzg
Status: NEW → ASSIGNED
Is this a duplicate of bug 657110
It might be a dupe of bug 655046 but the difference in here is also that instead of specifying "all" a specific suite was indicated "reftest". Let's land the changes in bug 655046 and then retry. lsblakk on another note; do you think the unit tests did not get triggered because reftests are split into two for Android? (I believe this is separate from the issue of not sending email to the developer as I don't see the entry on buildapi) This: try: -b do -p android-r7 -u reftest -t none instead of: try: -b do -p android-r7 -u reftest-1 reftest-2 -t none ? I have used this sendchange and I will see what happens: > buildbot sendchange --master production-master01.build.mozilla.org:9009 --username jmuizelaar@mozilla.com --branch try --revision df930499a74c --comments "try: -b do -p android-r7 -u reftest-1 reftest-2 -t none" So far the sendchange did not trigger a new build.
Whiteboard: [buildduty]
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.