Closed Bug 860831 Opened 11 years ago Closed 10 years ago

fix the taloserror handling when we process a crash

Categories

(Testing :: Talos, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jmaher, Unassigned)

References

Details

from tbpl logs:
0x662e3000 - 0x66333fff  libnssckbi.so (deleted)  ???

    main()
  File "run_tests.py", line 328, in main
    run_tests(parser)
  File "run_tests.py", line 277, in run_tests
    talos_results.add(mytest.runTest(browser_config, test))
  File "/builds/panda-0821/talos-data/talos/ttest.py", line 404, in runTest
    self.cleanupAndCheckForCrashes(browser_config, profile_dir, test_config['name'])
  File "/builds/panda-0821/talos-data/talos/ttest.py", line 170, in cleanupAndCheckForCrashes
    raise talosCrash()
TypeError: __init__() takes exactly 2 arguments (1 given)
this would make a good first bug.
Can I take up this bug?
this might not even be a bug anymore- yes, please take a look at this and see if it still happens.  You can get talos running and kill the process to invoke a crash.  I believe on linux it is 'kill -ABRT <pid>'
QA Contact: vaibhavmagarwal
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.