I also reran (directly on the buildbot) the subtests which seemed a bit slower in that run earlier today - and most looked fine with possible exception of test 112 which seems about 20% slower than I would have expected. generic/001 163s generic/024 12s generic/100 278s generic/112 319s generic/117 141s generic/124 49s generic/129 530s generic/133 454s generic/198 3s generic/247 95s generic/249 2s generic/285 8s generic/286 30s generic/310 311s generic/406 4s generic/432 3s generic/524 16s Ran: generic/001 generic/024 generic/100 generic/112 generic/117 generic/124 generic/129 generic/133 generic/198 generic/247 generic/249 generic/285 generic/286 generic/310 generic/406 generic/432 generic/524 Passed all 17 tests On Tue, Mar 5, 2019 at 5:45 PM Steve French <smfrench@xxxxxxxxx> wrote: > > Moved the xfstest git branch back to December 6th (just before the > testcase problem patch Xiaoli pointed out) - and cherrypicked tests > 524 and 528. Looks like current for-next worked fine > (http://smb3-test-rhel-75.southcentralus.cloudapp.azure.com/#/builders/4/builds/111). > Will kick off the cifs-testing bucket later today. > > -- > Thanks, > > Steve -- Thanks, Steve
