Bug 212622 – REGRESSION(r217572): run-webkit-tests should abort if the TCP ports for the servers are already in use.

• Component: Tools / Tests
• Status: NEW

[Carlos Alberto Lopez Perez]

It seems run-webkit-tests not longer (since r217572) aborts if there is any other process (for example, from other user) already listening on the TCP port the http/websocket/wpt helper servers needs.

If the TCP port is already listening it simply assumes those servers are already running (perhaps from a previous run-webkit-test iteration).

This can cause hard-to-diagnose problems, for example if the user is running other service than the webkit-test servers on this ports.

I think it should abort if it can't start itself the server on the designed TCP port.

[Carlos Alberto Lopez Perez]

Created attachment 400776 [details]
Patch

[Jonathan Bedard]

Comment on attachment 400776 [details]
Patch

I'm not against this, but I'm curious what people who make more use of these servers than myself things. Does Youenn have an opinion?

[youenn fablet]

I sometimes have the HTTP servers up and running so that I can debug in a browser. I find it useful that WTR can run in parallel.

But I can see why this could cause issues.
@Carlos, can you detail a bit the problems you encountered?

[Jonathan Bedard]

Another possibility is that we save a sort of status file (much like Postgres does) so we can keep track of our own web servers, but not generic ones running on the same ports.

[Carlos Alberto Lopez Perez]

(In reply to youenn fablet from comment #3)
> @Carlos, can you detail a bit the problems you encountered?

We have some shared remote servers for building, developing and testing and I found random timeouts and failures when running WebKit layout tests on them. Investigating the issue, I found that it was because I was running the layout tests at the same time than other mate.
Previously if this situation happened, run-webkit-tests aborted with a loud warning (so it was easy to spot the issue).

[youenn fablet]

(In reply to Carlos Alberto Lopez Perez from comment #5)
> (In reply to youenn fablet from comment #3)
> > @Carlos, can you detail a bit the problems you encountered?
> 
> We have some shared remote servers for building, developing and testing and
> I found random timeouts and failures when running WebKit layout tests on
> them. Investigating the issue, I found that it was because I was running the
> layout tests at the same time than other mate.
> Previously if this situation happened, run-webkit-tests aborted with a loud
> warning (so it was easy to spot the issue).

I see, so multiple checkouts but a single server actually running.
Would a console message warning stating that servers are already running be sufficient?

[Carlos Alberto Lopez Perez]

(In reply to youenn fablet from comment #6)
> (In reply to Carlos Alberto Lopez Perez from comment #5)
> > (In reply to youenn fablet from comment #3)
> > > @Carlos, can you detail a bit the problems you encountered?
> > 
> > We have some shared remote servers for building, developing and testing and
> > I found random timeouts and failures when running WebKit layout tests on
> > them. Investigating the issue, I found that it was because I was running the
> > layout tests at the same time than other mate.
> > Previously if this situation happened, run-webkit-tests aborted with a loud
> > warning (so it was easy to spot the issue).
> 
> I see, so multiple checkouts but a single server actually running.
> Would a console message warning stating that servers are already running be
> sufficient?

Yes, I guess it will be sufficient.