Last modified: 2011-03-03 08:22:07 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T29148, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 27148 - output written to the console during a dump run should go to a local log file as well
output written to the console during a dump run should go to a local log file...
Status: RESOLVED FIXED
Product: Datasets
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Normal minor (vote)
: ---
Assigned To: Ariel T. Glenn
:
Depends on:
Blocks: 27110
  Show dependency treegraph
 
Reported: 2011-02-04 01:01 UTC by Ariel T. Glenn
Modified: 2011-03-03 08:22 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ariel T. Glenn 2011-02-04 01:01:44 UTC
A bunch of output gets reported, including startup of processes, number of revisions processed at any given time, errors encountered when retrieving revisions, etc.  Right now these all go into the ether since the whole thing runs in a screen session.  They should get written into a log file so that we can see when something dies instead of having any relevant messages long since scrolled off the virtual screen.
Comment 1 Ariel T. Glenn 2011-03-03 08:22:07 UTC
fixed in my branch and deployed; specified by command line option to worker.py.  Not included (but probably ok): debugging output from CommandManagement.py

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links