Bug 141928

Summary: Merge run-launcher into run-minibrowser
Product: WebKit Reporter: Carlos Alberto Lopez Perez <clopez>
Component: Tools / TestsAssignee: Csaba Osztrogonác <ossy>
Status: RESOLVED FIXED    
Severity: Normal CC: andersca, cgarcia, commit-queue, dbates, ddkilzer, glenn, mcatanzaro, ossy, sam
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Patch darin: review+

Carlos Alberto Lopez Perez
Reported 2015-02-23 15:08:44 PST
The script Tools/Scripts/run-minibrowser don't works for the EFL or GTK ports. I think this script should gain both a --gtk and --efl switches to execute the minibrowser from this two ports.
Attachments
Patch (10.68 KB, patch)
2015-04-27 08:01 PDT, Csaba Osztrogonác
darin: review+
Csaba Osztrogonác
Comment 1 2015-02-23 23:52:24 PST
Yes, it seems it is Mac only now. But run-launcher already works, you can copy/paste the logic from it.
Carlos Garcia Campos
Comment 2 2015-02-24 01:15:24 PST
What is it used for? will it replace run-launcher eventually?
Carlos Alberto Lopez Perez
Comment 3 2015-02-24 03:26:29 PST
I didn't knew about run-launcher. Until now I'm executing the minibrowser manually like: Tools/jhbuild/jhbuild-wrapper --gtk run WebKitBuild/Release/bin/MiniBrowser What is the difference between run-launcher and run-minibrowser ? Should we merge both ?
Csaba Osztrogonác
Comment 4 2015-02-24 04:39:05 PST
It seems run-launcher is used only EFL and GTK nowadays, run-webkit-tests calls it after tests (efl.py, gtk.py) And run-minibrowser seems to be Mac only script now. I'd prefer merging run-launcher to run-minibrowser.
Michael Catanzaro
Comment 5 2015-02-24 06:59:24 PST
Be sure to update the build-webkit script as well; it instructs users to use run-launcher without any arguments when the build is complete, but that just prints a message saying your OS is unsupported, so this would be a good time to fix that.
Csaba Osztrogonác
Comment 6 2015-04-27 08:01:03 PDT
Created attachment 251741 [details] Patch additionally removing obsolete FIXMEs
Csaba Osztrogonác
Comment 7 2015-04-27 08:20:04 PDT
Comment on attachment 251741 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=251741&action=review > Tools/Scripts/webkitpy/port/efl.py:-132 > - # FIXME: We should find a way to share this implmentation with Gtk, > - # or teach run-launcher how to call run-safari and move this down to WebKitPort. It is only a oneliner, there is no need to try to share it with GTK. > Tools/Scripts/webkitpy/port/efl.py:-135 > - # FIXME: old-run-webkit-tests also added ["-graphicssystem", "raster", "-style", "windows"] > - # FIXME: old-run-webkit-tests converted results_filename path for cygwin. Just some comment, why can we remove them: - -graphicssystem raster -style windows are Qt crufts - cygwin: I can't remember if we ever supported Windows.
Darin Adler
Comment 8 2015-04-27 09:02:21 PDT
Comment on attachment 251741 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=251741&action=review > Tools/Scripts/webkitpy/port/efl.py:131 > + self._run_script("run-minibrowser", ["file://%s" % results_filename]) This is not the right way to construct a URL from a local file name. Isn’t there some python library function that can turn a filename into a URL that can handle things like "%" characters? > Tools/Scripts/webkitpy/port/gtk.py:202 > + self._run_script("run-minibrowser", ["file://%s" % results_filename]) Ditto.
Csaba Osztrogonác
Comment 9 2015-04-27 11:15:31 PDT
webkitpy.common.system.path.abspath_to_uri does it, win.py already use it in its show_results_html_file. The results is same, but I'll change it before landing.
Csaba Osztrogonác
Comment 10 2015-04-27 11:20:54 PDT
Note You need to log in before you can comment on or make changes to this bug.