{"push_id":631850797,"size":9,"distinct_size":9,"ref":"refs/heads/dh-test-vectors","head":"71d8f6c91e6c3d38fe8b4c3511c817671d9a462c","before":"bae69585cd583ea953154c1ac309db8303538af1","commits":[{"sha":"cd19ca3fe5ceed8648cf1eee5b46d0259ed48cda","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"thread: Add a function to pop and call all registered cleanup handlers","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/cd19ca3fe5ceed8648cf1eee5b46d0259ed48cda"},{"sha":"cce874c3678ed382cb77540313a7f7f54636c4d5","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"unit-tests: Invoke all registered thread cleanup handlers on test failure\n\nIf a test fails in a timeout or a test failure, longjmp() is used to restore\nthe thread context and handle test failure. However, there might be unreleased\nresources, namely locks, which prevent the library to clean up properly after\nfinishing the test.\n\nBy using thread cleanup handlers, we can release any test subject internal or\ntest specific external resources on test failure. We do so by calling all\nregistered cleanup handlers.","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/cce874c3678ed382cb77540313a7f7f54636c4d5"},{"sha":"d315d8d670627beae33a8c59ce9d5e2b93e9d3be","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"crypto-factory: Add enumerator method to support individual transform testing","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/d315d8d670627beae33a8c59ce9d5e2b93e9d3be"},{"sha":"24262d7ac98c33b8d8f19fcbd9fc5d710dfc1695","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"enum-names: Fail gracefully when passing a NULL value as enum names","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/24262d7ac98c33b8d8f19fcbd9fc5d710dfc1695"},{"sha":"80f0f277b6fae7484967b31f6f4927e28033d31d","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"transform: Add a getter for the enum_names for a specific transform type","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/80f0f277b6fae7484967b31f6f4927e28033d31d"},{"sha":"12c2502c04704adf2e1addbe6792b60ac9ba860a","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"unit-tests: Use progressive testing of transforms with test vectors\n\nThis allows us to show which transform from which plugin failed. Also, we use\nthe new cleanup handler functionality that allows proper deinitialization on\nfailure or timeout.","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/12c2502c04704adf2e1addbe6792b60ac9ba860a"},{"sha":"4fb03be6e612995ef313e4d6e594b18be8f8f6f1","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"crypto-factory: Remove obsolete transform testing functions","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/4fb03be6e612995ef313e4d6e594b18be8f8f6f1"},{"sha":"0eaf9c2830805532a154a42db303490626fe4278","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"unit-tests: Set test verbosity just after test suite loading\n\nWe see any plugin startup messages during suite configuration, where\ninitialization is called once to query plugin features. No need to be verbose\nand show these messages once again in the first test.","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/0eaf9c2830805532a154a42db303490626fe4278"},{"sha":"71d8f6c91e6c3d38fe8b4c3511c817671d9a462c","author":{"email":"54669547a225ff20cba8b75a4adca540eef25858@revosec.ch","name":"Martin Willi"},"message":"kernel-netlink: Don't mangle verbosity during test initialization\n\nWe now properly manage thread verbosity in the test framework, and don't need\nto silence thread spawning messages.","distinct":true,"url":"https://api.github.com/repos/strongswan/strongswan/commits/71d8f6c91e6c3d38fe8b4c3511c817671d9a462c"}]}