On Wed, Jan 9, 2019 at 12:46 AM ronnie sahlberg <ronniesahlberg@xxxxxxxxx> wrote: > > 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." OK - thx - I know see how to do that if you do force build instead of rebuild, so that part should be ok > 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. > > > Steve French <smfrench@xxxxxxxxx> writes: > > > 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. -- Thanks, Steve
