Date: Thu, 28 Feb 2019 10:05:15 -0800 From: "Enji Cooper (yaneurabeya)" <yaneurabeya@gmail.com> To: Alan Somers <asomers@freebsd.org> Cc: "freebsd-testing@freebsd.org" <freebsd-testing@freebsd.org>, Ed Maste <emaste@freebsd.org>, Julio Merino <jmmv@freebsd.org>, "Jonathan T. Looney" <jtl@freebsd.org> Subject: Re: atf-c++ vs GoogleTest vs share/mk Message-ID: <39472FE6-1A00-4938-9629-4AB741E45004@gmail.com> In-Reply-To: <A6D8F747-37B6-4EC9-ADE6-823E529EF226@gmail.com> References: <CAOtMX2h_tJHH=mX8wVrMLQNeCsN%2B_D4Jw35KyuiHUcQniNweWg@mail.gmail.com> <C9F53820-7817-4FEC-A20C-ACA35819E763@gmail.com> <CAOtMX2jCi9ZUVdCLVE8kMRcrdwAmSbLPJTmHdhf3pJyyWR=k-A@mail.gmail.com> <A6D8F747-37B6-4EC9-ADE6-823E529EF226@gmail.com>
index | next in thread | previous in thread | raw e-mail
> On Feb 27, 2019, at 12:53, Enji Cooper <yaneurabeya@gmail.com> wrote: … > I will look into how Googletest currently handles segfaults, etc, and raise that as a point of concern with the upstream project if need be, as I don’t know how exactly this is handled in exceptional cases. One thing to note as well (to potentially adjust expectations for readers) is that Kyua handling ATF crashes and cleaning up requires a deeper understanding of the ATF interface in Kyua. It’s a best effort, e.g., if the program crashes while cleaning up, it can leave orphan directories behind or not fully clean up the system (I’ve seen this happen before and I have also triggered scenarios like this). This is to be expected, but I just wanted to be explicit about the fact that the interface does not aim for a perfect solution—it’s a good enough one for general cases. This aligns with other test frameworks I’ve used in the past. Cheers, -Enjihome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39472FE6-1A00-4938-9629-4AB741E45004>