Bug 1768092 Comment 8 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to Steve Fink [:sfink] [:s:] from comment #6)
> (In reply to Greg Mierzwinski [:sparky] from comment #4)
> > :sfink, can you try this command: `./mach raptor -t sunspider --browsertime`
> > 
> > I think the issue here is that raptor thinks you want to run the test through the webextension but that is no longer supported for the most part.
> 
> That's what I ended up doing. I naively thought that I should start with the seemingly most basic form of the command, but for what I want to do, I need `--browsertime` anyway.
> 
> Should the webext mechanism be removed, or at least the local run portion of it? Or fail unless you pass `--yes-i-know-its-deprecated-run-it-anyway`?

As you noticed, there are still some tests which still use it unfortunately. There's still a couple outstanding issues we need to work out before we can turn off or port those tests. I've made a patch that resolves the issue for me locally but we'll likely have some discussions before going further with it. It's possible that we get rid of those cpu/memory/power tests in the near future allowing us to make a patch to fully disable webext.
(In reply to Steve Fink [:sfink] [:s:] from comment #6)
> (In reply to Greg Mierzwinski [:sparky] from comment #4)
> > :sfink, can you try this command: `./mach raptor -t sunspider --browsertime`
> > 
> > I think the issue here is that raptor thinks you want to run the test through the webextension but that is no longer supported for the most part.
> 
> That's what I ended up doing. I naively thought that I should start with the seemingly most basic form of the command, but for what I want to do, I need `--browsertime` anyway.
> 
> Should the webext mechanism be removed, or at least the local run portion of it? Or fail unless you pass `--yes-i-know-its-deprecated-run-it-anyway`?

As you noticed, there are still some tests which use it unfortunately. There's still a couple outstanding issues we need to work out before we can turn off or port those tests. I've made a patch that resolves the issue for me locally but we'll likely have some discussions before going further with it. It's possible that we get rid of those cpu/memory/power tests in the near future allowing us to make a patch to fully disable webext.
(In reply to Steve Fink [:sfink] [:s:] from comment #6)
> (In reply to Greg Mierzwinski [:sparky] from comment #4)
> > :sfink, can you try this command: `./mach raptor -t sunspider --browsertime`
> > 
> > I think the issue here is that raptor thinks you want to run the test through the webextension but that is no longer supported for the most part.
> 
> That's what I ended up doing. I naively thought that I should start with the seemingly most basic form of the command, but for what I want to do, I need `--browsertime` anyway.
> 
> Should the webext mechanism be removed, or at least the local run portion of it? Or fail unless you pass `--yes-i-know-its-deprecated-run-it-anyway`?

As you noticed, there are still some tests which use it unfortunately. There's still a couple outstanding issues we need to work out before we can turn off or port those tests. I've made a patch that resolves the issue for me locally but we'll likely have some discussions before going further with it. It's possible that we get rid of those cpu/memory/power tests in the very near future allowing us to make a patch to fully disable webext.

Back to Bug 1768092 Comment 8