TestSadTab.test_*_web_process_crashed fail with oxide 1.9

Bug #1493825 reported by Olivier Tilloy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
webbrowser-app (Ubuntu)
High
Olivier Tilloy

Bug Description

With the publication of oxide 1.9, the following two autopilot tests started failing on my arale:

  webbrowser_app.tests.test_sad_tab.TestSadTab.test_close_tab_web_process_crashed
  webbrowser_app.tests.test_sad_tab.TestSadTab.test_reload_web_process_crashed

Indeed, when I manually try to crash a renderer process with "kill -11 $pid", nothing happens.
"kill -6 $pid" (SIGABRT) does the job though, so it’s an easy fix.

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package webbrowser-app - 0.23+15.10.20150913-0ubuntu1

---------------
webbrowser-app (0.23+15.10.20150913-0ubuntu1) wily; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.
  * Resync trunk. added: po/mr.po

  [ Olivier Tilloy ]
  * Allow saving canvas images from the context menu.
  * Handle HTTP authentication requests by showing an authentication
    dialog. (LP: #1422534)
  * Remove the workaround for bug #1471181 now that oxide 1.9 has been
    released with a proper fix. (LP: #1471181)
  * Set the 'visible' property of actions instead of 'enabled' to ensure
    the visibility of the corresponding entries in the drawer menu
    matches. (LP: #1495297)
  * Use SIGABRT instead of SIGSEGV to crash a renderer process in tests.
    (LP: #1493825)
  * Use the new WebContext.userAgentOverrides API (new in Oxide 1.9).
    (LP: #1410753)

  [ Ugo Riboni ]
  * Handle HTTP authentication requests by showing an authentication
    dialog. (LP: #1422534)

 -- Olivier Tilloy <email address hidden> Sun, 13 Sep 2015 21:25:02 +0000

Changed in webbrowser-app (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers