Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Masterticket: Clean up the error log

Description

The release should have no entries in the error log, if a fresh installation is done an connects to a server. The error log should stay clean after:

  • Browsing through all the preference options.

  • Chatting with one contact.

  • Entering a conference room and chatting in this room.

  • Changing the presence status

Sub tasks should be created for every identified issue.

Environment

None

Attachments

1
100% Done
Loading...

Activity

Show:

wroot March 27, 2014 at 10:24 PM

I don't think it is a Blocker (or even Major) issue. I don't believe you can get rid of errors forever. I see a few new errors in my logs now. Some parts have been updates (LaF, Smack, FMJ, other libraries, new patches, etc.), so there will be new errors.

All subtasks are closed, so will close the masterticket too. Reopen if needed. Or maybe better file a new ticket for new kind of errors.

Wolf P. June 14, 2011 at 9:18 AM

is clean in SPARK-INSTALL4J-403

moving ticket to 2.7.0

Walter Ebeling March 17, 2011 at 7:44 PM

Done for RC2 cut off. Moves to 2.6.0

Walter Ebeling March 15, 2011 at 9:02 AM

New error log entries after landing of Smack 3.2 trunk

Wolf P. March 11, 2011 at 12:40 PM

All good to go

Fixed

Details

Priority

Assignee

Reporter

Fix versions

Created February 27, 2011 at 6:01 PM
Updated March 27, 2014 at 10:24 PM
Resolved March 27, 2014 at 10:24 PM