In the latest dev code, most of the widget-related Behat tests are generating PHP notices after the scenario ends and the temporary user is deleted.

The sequence of notices goes like this:

Notice: Undefined property: stdClass::$task_id in panel_context_panels_cache_get() (line 1586 of /profiles/panopoly/modules/contrib/panels/panels.module).

Notice: Undefined property: stdClass::$task in panel_context_panels_cache_get() (line 1595 of /profiles/panopoly/modules/contrib/panels/panels.module).

Notice: Undefined property: stdClass::$subtask in panel_context_panels_cache_get() (line 1595 of /profiles/panopoly/modules/contrib/panels/panels.module).

Notice: Undefined property: stdClass::$locked in panel_context_panels_cache_get() (line 1603 of /profiles/panopoly/modules/contrib/panels/panels.module).

Notice: Undefined index: page_g8utiwod_panel_context in _panel_context_panels_cache_get_page_cache() (line 1617 of /profiles/panopoly/modules/contrib/panels/panels.module).

Notice: Undefined index: changed in _panel_context_panels_cache_get_page_cache() (line 1617 of /profiles/panopoly/modules/contrib/panels/panels.module).

Notice: Undefined property: stdClass::$task_name in panel_context_panels_cache_clear() (line 1639 of /profiles/panopoly/modules/contrib/panels/panels.module).

The errors show up after the temp user has been deleted, and before the start of the user session for the next scenario.

They don't appear in the UI, and they don't happen when following the test steps manually (up to deleting the landing page), so they are probably caused somewhere in the after scenario step that deletes the user or the user's content. They don't seem to be happening after the WYSIWYG toolbar scenarios or the Linkit scenarios - these scenarios do not use the IPE or landing pages.

Comments

dsnopek’s picture

Status: Active » Postponed (maintainer needs more info)

Are these only appearing in watchdog? Or are they visible from the commandline? I don't see any like this on the command line in recent Travis builds, so maybe this is fixed now? Please let me know, thanks!