Hi Prakash, i think we can split process to: - build - start zfs tests && (optional) start others tests in parallel on another instance.
we are more interested in ZFS issues with OpenZFS PRs and others tests just add additional overhead and time. if you have resources and time - you can try to configure separate instance for others tests and run it in parallel with ZFS tests. just proposal. best regards, -Igor > On Oct 31, 2017, at 6:02 PM, Prakash Surya <[email protected]> wrote: > > Yes, that's due to not being able to create an AWS VM; so it's a problem with > the automation, not the code being tested. > > I've restarted the build, but the prior run passed the build and zfs test > steps, so I consider that successful. > > I may even turn off the non ZFS tests at some point, since I don't think we > get much value from running them for every PR. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <https://github.com/openzfs/openzfs/pull/483#issuecomment-340790791>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/AOi0Kx0OrJWBW7BaHO1g9SUs7JJhxGrOks5sxzaQgaJpZM4QHz23>. > > openzfs-developer | Archives > <https://openzfs.topicbox.com/groups/developer/discussions/T1dada2f5266ff7f9-M383cdd8e4e8acba71ecc92d8> > | Powered by Topicbox <https://topicbox.com/> ------------------------------------------ openzfs-developer Archives: https://openzfs.topicbox.com/groups/developer/discussions/T1dada2f5266ff7f9-M08329d581c0ac255e0cbd7dc Powered by Topicbox: https://topicbox.com
