[Webkit-unassigned] [Bug 64189] garden-o-matic should be able to determine which revisions caused a given failure

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Jul 8 12:22:53 PDT 2011


--- Comment #2 from Adam Roben (:aroben) <aroben at apple.com>  2011-07-08 12:22:53 PST ---
(In reply to comment #1)
> aroben: To fill you in on a discussion that dglazkov and I had this morning:
> 1) We think that being able to go back in time (like in TestFailures) and find the root cause of a test failure is important in order to figure out the best way to deal with a failure.
> 2) Having the tool hosted on a web site is also important so that the gardener can give links to folks.

These both make sense to me.

> Both those thoughts push us more towards the TestFailures design point, which means we might want to integrate sooner rather than later.


> To access the local server (to preform backend actions), we're currently thinking about using XMLHttpRequest and CORS.  If you have the local server running, you'll see the actions and if you don't have it running, you'll see the "read only" view.

So TestFailures would send an XHR to your local server? How would that work? I didn't think the local server was publicly-addressable. Maybe you meant the local server would XHR TestFailures, but then I don't know what "If you have the local server running, you'll see the actions" means.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list