{"action":"created","issue":{"url":"https://api.github.com/repos/gabime/spdlog/issues/63","labels_url":"https://api.github.com/repos/gabime/spdlog/issues/63/labels{/name}","comments_url":"https://api.github.com/repos/gabime/spdlog/issues/63/comments","events_url":"https://api.github.com/repos/gabime/spdlog/issues/63/events","html_url":"https://github.com/gabime/spdlog/issues/63","id":62817594,"number":63,"title":"travis-ci unit tests","user":{"login":"ido","id":85574,"avatar_url":"https://avatars.githubusercontent.com/u/85574?v=3","gravatar_id":"","url":"https://api.github.com/users/ido","html_url":"https://github.com/ido","followers_url":"https://api.github.com/users/ido/followers","following_url":"https://api.github.com/users/ido/following{/other_user}","gists_url":"https://api.github.com/users/ido/gists{/gist_id}","starred_url":"https://api.github.com/users/ido/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ido/subscriptions","organizations_url":"https://api.github.com/users/ido/orgs","repos_url":"https://api.github.com/users/ido/repos","events_url":"https://api.github.com/users/ido/events{/privacy}","received_events_url":"https://api.github.com/users/ido/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-18T22:24:32Z","updated_at":"2015-03-18T23:53:49Z","closed_at":null,"body":"@gabime:\r\nWould you consider writing some unit/regression tests and a `.travis.yml` file so that they run on each git push?  I had to fix a few minor bugs last time I did a `git subtree pull`.  I'd especially like to see the `bench` program run on each `git push` on travis-ci so we can easily see if a commit introduces any performance regressions.\r\n\r\nHere is an example C++11 project `.travis.yml` file you could base yours off of, if you've never used travis-ci before, it's super straightforward to get started:\r\nhttps://github.com/zaphoyd/websocketpp/blob/master/.travis.yml\r\n\r\nI do not have time to do this myself right now or I'd submit this as a pull request.  If I have time this summer, I'll add some performance/unit tests as well, but maybe you could start with lightly modified versions of the example or bench programs that output the max message rate/sec, time to log 1,000,000 entries with each of the various logging methods (sync st file, async mt file, async st file, etc.)?  Then move on to unit tests of the public API?\r\n\r\nIf you don't have time, thanks again for taking your time to write this library in the first place. :-)"},"comment":{"url":"https://api.github.com/repos/gabime/spdlog/issues/comments/83227129","html_url":"https://github.com/gabime/spdlog/issues/63#issuecomment-83227129","issue_url":"https://api.github.com/repos/gabime/spdlog/issues/63","id":83227129,"user":{"login":"gabime","id":6052198,"avatar_url":"https://avatars.githubusercontent.com/u/6052198?v=3","gravatar_id":"","url":"https://api.github.com/users/gabime","html_url":"https://github.com/gabime","followers_url":"https://api.github.com/users/gabime/followers","following_url":"https://api.github.com/users/gabime/following{/other_user}","gists_url":"https://api.github.com/users/gabime/gists{/gist_id}","starred_url":"https://api.github.com/users/gabime/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gabime/subscriptions","organizations_url":"https://api.github.com/users/gabime/orgs","repos_url":"https://api.github.com/users/gabime/repos","events_url":"https://api.github.com/users/gabime/events{/privacy}","received_events_url":"https://api.github.com/users/gabime/received_events","type":"User","site_admin":false},"created_at":"2015-03-18T23:53:49Z","updated_at":"2015-03-18T23:53:49Z","body":"Why modify the output? It already provides most of needed info.."}}