Re: [OMPI devel] MTT / Open MPI Visibility of New Failures

We are putting a pin in this for now. Amazon had an idea they wanted to run with and report back. Once they have more info then we'll try to setup another meeting. On Tue, Jul 11, 2017 at 3:20 PM, Josh Hursey wrote: > In the Open MPI face-to-face meeting we had a long

Re: [OMPI devel] MTT / Open MPI Visibility of New Failures

i think we should only run minimal tests *by default* for each PR then we can have jenkins interpret some specific bot commands (for example :bot:test:ibm/collective) so additional tests can be performed *on demand* Cheers, Gilles - Original Message - Thanks for the idea. For

Re: [OMPI devel] MTT / Open MPI Visibility of New Failures

Thanks for the idea. For IBM's internal CI that's similar to what we do (but I don't think we take advantage of the XML report - I'll mention that to our CI folks) - we run MTT for every internal PR. It takes a few hours per PR to complete though. I don't know how acceptable that is for the

Re: [OMPI devel] MTT / Open MPI Visibility of New Failures

Josh and all, an other or complementary idea is to use MTT from jenkins and with the junit plugin. iirc, the python client can generate a junit xml report, and fwiw, i made a simplistic proof of concept in the perl client. the idea is the junit jenkins plugins display a summary of all tests (ok,

[OMPI devel] MTT / Open MPI Visibility of New Failures

In the Open MPI face-to-face meeting we had a long discussion about how to better harness MTT such that new failures are identified and the community alerted to their existence. The current manual way is not working. Our ultimate goal here is to know if we are making forward progress, and if