Closed Bug 1074162 Opened 11 years ago Closed 11 years ago

Reduce iterations or disable b2gperf tests running in CI

Categories

(Firefox OS Graveyard :: Performance, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davehunt, Unassigned)

References

Details

Attachments

(3 files)

The Gaia make test-perf jobs have been running with 30 iterations in CI for some weeks now. It would seem to be a good time to reduce the number of iterations for the b2gperf jobs, or perhaps disable them entirely. It was my understanding that once make test-perf was reliably providing results that we would stop running b2gperf. If there are no objections I will reduce the number of iterations to 5 for all b2gperf jobs and leave it that way for 1-2 weeks before disabling these jobs. Another 1-2 weeks after that, I will delete the jobs in Jenkins.
Not sure who the best person to needinfo on this is. Geo: do you have any thoughts/concerns?
Flags: needinfo?(gmealer)
I have no objections; I support this.
No objections here. AFAIK, we aren't really looking at the b2gperf results at this point.
Flags: needinfo?(gmealer)
Thanks. I've reduced the iterations to 5 and will disable these jobs entirely in two weeks time unless there are any objections.
Flags: needinfo?(dave.hunt)
I've now disabled the b2gperf jobs and will delete them in two weeks time unless there are any objections.
I've now deleted these jobs and attached their configuration files to the bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(dave.hunt)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: