{"push_id":1453776382,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"659f9fc1a3cb1b5907081c041ca36ae1a70de07c","before":"7a52889c69e6f70695425d888e068c8f610dcb20","commits":[{"sha":"eb128698bc159392b3364dbdd40c6b472135338f","author":{"name":"Michael Petlan","email":"69225dcd726024b1195e775a6d31a18bc59de2e7@redhat.com"},"message":"base_list/test_basic.sh: updated regexps to handle the named events\n\nSince perf has come with event naming similar to the events we know\nfrom OProfile, we need to accept them in the perf-list output.\n\nThe format is not very parser-friendly,  as we are used to in perf.\nCurrently it looks like the following:\n\nEvent group:\n  event.name1\n       [Some description]\n  event.name2\n       [Some very long description that breaks into\n        two lines]\n  event.name3\n       [a = b]\n\nIt is pretty possible, that the description breaks into three lines\nin future, however, that would really chew up the power of our reg.\nexpressions,  so currently, we expect lines containing \\[.* or \\].*\nas the event description.","distinct":true,"url":"https://api.github.com/repos/rfmvh/perftool-testsuite/commits/eb128698bc159392b3364dbdd40c6b472135338f"},{"sha":"659f9fc1a3cb1b5907081c041ca36ae1a70de07c","author":{"name":"Michael Petlan","email":"69225dcd726024b1195e775a6d31a18bc59de2e7@redhat.com"},"message":"base_archive/test_basic.sh: check bzcat status; fix dso checking\n\n(1) In case no archive is created, the `bzcat | tar` chain fails.\nWe need to get rid of their error messages (for lesser verbosity\nlevels) but also preserve the status of the operation.\n\n(2) The dso log files were swapped, due to their incorrect order.","distinct":true,"url":"https://api.github.com/repos/rfmvh/perftool-testsuite/commits/659f9fc1a3cb1b5907081c041ca36ae1a70de07c"}]}
{"actor":{"display_login":"rfmvh"}}