EventLogging async logEvent test fails only when all are run
Closed, DeclinedPublic
Actions

Assigned To

Authored By

	• Mattflaschen-WMF
	Mar 8 2013, 12:50 AM

Description

When the EventLogging extension is installed, the QUnit tests pass (quickly) when run in isolation in production mode:

/wiki/Special:JavaScriptTest/qunit?module=ext.eventLogging

However, when running all QUnit tests (across all modules) in production mode:

/wiki/Special:JavaScriptTest/qunit#

it hangs forever on logEvent:

Running:
ext.eventLogging: logEvent

Since it passes in isolation, it seems like a possible QUnit or testrunner issue.

Version: unspecified
Severity: normal

Details

Reference: bz45870

Event Timeline

• bzimport raised the priority of this task from to Needs Triage.Nov 22 2014, 1:28 AM

• bzimport added a project: MediaWiki-extensions-EventLogging.

• bzimport set Reference to bz45870.

• Mattflaschen-WMF created this task.Mar 8 2013, 12:50 AM

Redirecting to the "EventLogging extension" component

(In reply to comment #1)

Redirecting to the "EventLogging extension" component

I think it might have been, since I can't reproduce it. On test2, EventLogging's QUnit tests pass both when invoked in isolation and when invoked as part of a comprehensive test.

See:

[moving from MediaWiki extensions to Analytics product - see bug 61946]

Luke081515 removed a subscriber: • wikibugs-l-list.Jan 28 2016, 6:00 PM

Restricted Application added a subscriber: StudiesWorld. · View Herald TranscriptJan 28 2016, 6:00 PM

EventLogging async logEvent test fails only when all are runClosed, DeclinedPublicActions

Description

Details

Event Timeline

EventLogging async logEvent test fails only when all are run
Closed, DeclinedPublic
Actions