This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, 2008-09-10 at 10:50 -0400, Masami Hiramatsu wrote: > Petr Muller wrote: > > I'm a member of Red Hat tools QA team. I've set up a regular testing > > script which, once a day, will fetch a HEAD of master git branch, build > > it, and run the testsuite, submitting logs to dejazilla. > > > > I hope this can be useful for you, please let me know, if you find it > > needless, or things you would like or do not like. > > In the case of that you test once a day, I think it would be better to > send the result only if there are some differences from previous. Makes sense. I will change the scripts so they won't submit the results if they are same as the previous day. I wonder - how much is dejazilla monitored for regressions? I mean - I can easily spot regressions "from yesterday" too as a part of that comparison, how can I give an alert? Is uploading results to dejazilla sufficient to trigger someone's alarm? > > Some first runs are already at dejazilla, and I've noticed quite a high > > number of 'UNTESTED' in my results (cca 230), in comparison to other > > results already there (cca 20). What can be the reason, and what should > > I do to make these testcases working? > > Would you run 'make installcheck'? 'make check' will skip some tests > which install some test modules. Yes, this was the reason. I modified the scripts to do installcheck instead now. Petr
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |