TypeError: killAndGetStackNoScreenshot() takes exactly 4 arguments (5 given) (File "/Users/cltbld/talos-slave/test/build/tests/mochitest/automation.py", line 901, in killAndGetStack)

RESOLVED FIXED in mozilla23

Status

RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: emorley, Assigned: jdm)

Tracking

Trunk
mozilla23
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
Caused by bug 597064.

https://tbpl.mozilla.org/php/getParsedLog.php?id=22812793&tree=Mozilla-Central#error0

{
02:42:49     INFO -  INFO | runtests.py | Received unexpected exception while running application
02:42:49     INFO -  Traceback (most recent call last):
02:42:49     INFO -    File "/Users/cltbld/talos-slave/test/build/tests/mochitest/runtests.py", line 770, in runTests
02:42:49     INFO -      onLaunch=onLaunch)
02:42:49     INFO -    File "/Users/cltbld/talos-slave/test/build/tests/mochitest/automation.py", line 1111, in runApp
02:42:49     INFO -      status = self.waitForFinish(proc, utilityPath, timeout, maxTime, startTime, debuggerInfo, symbolsPath)
02:42:49     INFO -    File "/Users/cltbld/talos-slave/test/build/tests/mochitest/automation.py", line 969, in waitForFinish
02:42:49     INFO -      self.killAndGetStack(proc.pid, utilityPath, debuggerInfo)
02:42:49     INFO -    File "/Users/cltbld/talos-slave/test/build/tests/mochitest/automation.py", line 901, in killAndGetStack
02:42:49     INFO -      self.killAndGetStackNoScreenshot(self, processPID, utilityPath, debuggerInfo)
}
(Assignee)

Comment 1

6 years ago
Created attachment 747947 [details] [diff] [review]
Remove incorrect self argument from killAndGetStack.
Attachment #747947 - Flags: review?(ted)
Comment on attachment 747947 [details] [diff] [review]
Remove incorrect self argument from killAndGetStack.

Review of attachment 747947 [details] [diff] [review]:
-----------------------------------------------------------------

Oops.
Attachment #747947 - Flags: review?(ted) → review+
You need to log in before you can comment on or make changes to this bug.