Closed Bug 538519 Opened 15 years ago Closed 14 years ago

automate winmo talos

Categories

(Release Engineering :: General, defect)

ARM
Windows Mobile 6 Professional
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: mozilla, Assigned: mozilla)

References

Details

Dependent on jmaher's work, but we should have enough tools to at least get Ts going at first.

This bug tracks the whole thing, however.
Blocks: 538521
I've got wip at http://hg.mozilla.org/users/asasaki_mozilla.com/winmo-custom and http://hg.mozilla.org/users/asasaki_mozilla.com/winmo-configs .

I haven't successfully run these yet -- my touchpros are offline again (this seems to happen a lot).

Questions:

1) what goes in /tests/talos on device?  Anything?  I've got references to it but the cleanup.py/install.py files nuke it and don't put anything there.
2) what was the magical incantation to extract the exe via 7z ?  I've tried various things without any luck.
Depends on: 541196
The above questions are resolved and the tests seem to be running happily, other than the error in bug 541196 comment 3, which points to fennec not exiting correctly via the shutdown script.
Depends on: 541278
Status update:
The shutdown script issue is two things.

1) bug 541278: winmo devices can't access bm-foopy
2) the timeout on pageloads appears to be bumped up to very, very long. Despite the fact that the devices can't get to bm-foopy (noticed this quickly on Opera), on Fennec it'll keep trying 10 minutes later.

Fixing bug 541278 should get things working, hopefully.
Winmo Ts appears to be running on staging with Joel's latest talos tarball.  Uploading my patches here shortly.
Is winmo ts still running?  Can we mark this bug closed or are we waiting on the other tests tp4, etc..?
Latest wip are in the above repos.
Blocks: 554087
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.