Talos shouldn't extract its data into the source tree

NEW
Unassigned

Status

enhancement
a year ago
a year ago

People

(Reporter: standard8, Unassigned)

Tracking

Version 3
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [PI:June])

According to bug 1435346 and bug 1435342 it looks like running Talos locally is extracting its tp5n dataset (and possibly others?) into the source tree.

This makes it harder for developer tools to work properly as seen in those bugs - we have to add extra ignores.
Whiteboard: [PI:February]
ideally in ~/.mozilla/talos/
maybe in objdir would be better.  We also have problems with the .develop files
Whiteboard: [PI:February] → [PI:March]
I did some work here and got stuck- one direction we are taking is a new tool 'raptor' that would get the benchmarks and tp6 pageset at a start- that is the majority of the uses of large datasets (but not all)- ideally that would use the objdir in setting up when running locally- we should have that done in April.  Remaining work would be:
* tp5, damp, tp5o_scroll, tps - all using the tp5 pageset
* manifest files that are edited to run against localhost (dynamically done with ./mach talos-test)

I believe the main work here is setting up a objdir/testing/talos/... directory where we can symlink/copy the talos bits during the build (like we do for reftest, mochitest, xpcshell, etc.) and then run the tests from there.
Whiteboard: [PI:March] → [PI:April]
Whiteboard: [PI:April] → [PI:May]
Whiteboard: [PI:May] → [PI:June]
You need to log in before you can comment on or make changes to this bug.