When you force a build, you can put in the reason for the build. I think it defaults to "forced build" but you can put any text you want there. Like I did in this build: http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/2/builds/87 "added test for large read + seal. Should fail." On Wed, Jan 9, 2019 at 4:04 AM Steve French <smfrench@xxxxxxxxx> wrote: > > The last commit (and/or fs/cifs commit) (hash e.g.) in the tree used > to kick off the tests would be VERY useful, and also if there were a > way to have a description field added for a test run that would allow > me to say the purpose of the run (e.g. "validating for-next before > sending merge request" or "testing Pavel's credit handling patch > series" etc. > > On Tue, Jan 8, 2019 at 7:05 AM Aurélien Aptel <aaptel@xxxxxxxx> wrote: > > > > Steve French <smfrench@xxxxxxxxx> writes: > > > Buildbot tests looked ok (albeit a few tests skipped due to xfstest > > > config issues such as generic/197, generic/208 etc.) for the current > > > for-next branch which includes most (first four of the five) of > > > Pavel's credit handling series (not the last one which might have a > > > problem, still checking). Commits included are 5.0-rc1 + these six in > > > for-next. Given the importance of the credit handling patches, > > > hopefully we can finish testing by the end of this week and get them > > > in ASAP. > > > > Is there a view where we can clearly see a list of commit tested and the > > result for each group? Closest I found was > > > > http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/console > > > > But it doesnt actually shows the commit msg or hash. > > > > Cheers, > > -- > > Aurélien Aptel / SUSE Labs Samba Team > > GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 > > SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany > > GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) > > > > -- > Thanks, > > Steve