Bugzilla

so far I am getting
````
Traceback (most recent call last):
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/mach_commands.py", line 367, in show_taskgraph
    tg = getattr(tgg, graph_attr)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 153, in full_task_graph
    return self._run_until('full_task_graph')
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 359, in _run_until
    k, v = next(self._run)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 273, in _run
    raise Exception("duplicate tasks with label " + task.label)
Exception: duplicate tasks with label test-windows7-32/opt-browsertime-tp6-profiling-firefox-amazon-e10s
```
When we get `-cold` out of browsertime tasks, they become their warm versions in terms of naming. We have to have a unique naming for each config version of the test. How do we deal with that?

I am going to submit to phab the current patch and talk there about it.

so far I am getting
````
Traceback (most recent call last):
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/mach_commands.py", line 367, in show_taskgraph
    tg = getattr(tgg, graph_attr)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 153, in full_task_graph
    return self._run_until('full_task_graph')
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 359, in _run_until
    k, v = next(self._run)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 273, in _run
    raise Exception("duplicate tasks with label " + task.label)
Exception: duplicate tasks with label test-windows7-32/opt-browsertime-tp6-profiling-firefox-amazon-e10s
```

When we get `-cold` out of browsertime tasks, they become their warm versions in terms of naming. We have to have a unique naming for each config version of the test. How do we deal with that?

I am going to submit to phab the current patch and talk there about it.

so far I am getting
````
Traceback (most recent call last):
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/mach_commands.py", line 367, in show_taskgraph
    tg = getattr(tgg, graph_attr)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 153, in full_task_graph
    return self._run_until('full_task_graph')
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 359, in _run_until
    k, v = next(self._run)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 273, in _run
    raise Exception("duplicate tasks with label " + task.label)
Exception: duplicate tasks with label test-windows7-32/opt-browsertime-tp6-profiling-firefox-amazon-e10s

```

When we get `-cold` out of browsertime tasks, they become their warm versions in terms of naming. We have to have a unique naming for each config version of the test. How do we deal with that?

I am going to submit to phab the current patch and talk there about it.

so far I am getting
```
Traceback (most recent call last):
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/mach_commands.py", line 367, in show_taskgraph
    tg = getattr(tgg, graph_attr)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 153, in full_task_graph
    return self._run_until('full_task_graph')
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 359, in _run_until
    k, v = next(self._run)
  File "/home/alexandru.ionescu/workspace/mozilla-central/taskcluster/taskgraph/generator.py", line 273, in _run
    raise Exception("duplicate tasks with label " + task.label)
Exception: duplicate tasks with label test-windows7-32/opt-browsertime-tp6-profiling-firefox-amazon-e10s
```
When we get `-cold` out of browsertime tasks, they become their warm versions in terms of naming. We have to have a unique naming for each config version of the test. How do we deal with that?

I am going to submit to phab the current patch and talk there about it.