search

Wordseer / wordseer

The WordSeer text analysis tool, written in Flask.
http://wordseer.berkeley.edu/
40 stars 16 forks source link

Implemented logging #106

Closed abendebury closed 10 years ago

abendebury commented 10 years ago

Fixes #98.

keien commented 10 years ago

Why does Travis fail on this?

abendebury commented 10 years ago

It fails the same unit test that fails in removing-readerwriter (this has been branched from removing-readerwriter).

keien commented 10 years ago

did you want to merge this into removing-readerwriter then?

abendebury commented 10 years ago

I'll merge in the latest commit from removing-readerwriter and then we should be getting passing tests.

keien commented 10 years ago

does this mean we can merge in everything that branched from removing-readerwriter into master?

abendebury commented 10 years ago

No, that would be very difficult. Let's merge these things into removing-readerwriter, then we can merge that into master.

keien commented 10 years ago

sounds good, i'll merge this one then

keien commented 10 years ago

Where do the logs go? Can we put them into a log directory at the root unless there's a better place you can think of?

abendebury commented 10 years ago

That's fine, changing the log location is as easy as changing one line in logging.json. Right now they just go into wordseer.log at the root directory.

keien commented 10 years ago

Also, is it possible to generate separate log files for each run?

abendebury commented 10 years ago

No, unless you manually remove/rename the log file between runs.