Re: [MTT devel] complaints about github pages being generated with every PR
Howard, each commits trigger a travis build, and the deploy section of travis builds the doc and push it if the html has changed (the pdf contains timestamps, that's why we only focus on the html). bottom line, the doc will be updated to gh-pages only if it has to. If the gh-pages repo is updated at each commit and for no reason (e.g. the doc virtually did not change), then this is a bug and I will be happy to investigate it. fwiw, I manually double checked the last commits, and to me, the changes in the doc were legit. Cheers, Gilles On 10/18/2018 6:57 AM, Ralph H Castain wrote: Tell the “certain individual” to get over it :-) We’ve discussed this several times and it isn’t a simple fix. What we want is to regenerate when something actually changes in the generated files, but we don’t have a good way of doing it. I’m sure we would be happy to see a PR from that “certain individual” :-) Ralph On Oct 17, 2018, at 2:50 PM, Howard Pritchard wrote: Hi Folks, A certain individual is complaining about the fact that MTT repo currently is set to have github pages updates following every commit. I suspect fixing this requires intervention by someone with admin rights on the repo. Could we have this feature disabled? Howard ___ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel ___ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel ___ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel
Re: [MTT devel] Send results to multiple databases?
My 0.02 US$ An other approach would be to run the MTT tests, store the results in a (text ? xml ?) file, and then submit them from an internet connected machine. not only that would allow you to submit to multiple databases, but that would allow you to run the MTT test suite on an cluster with no connection/proxy to internet. I am not sure whether this is currently implemented by the perl and/or python clients. Cheers, Gilles On 12/21/2017 2:13 AM, Van Dresser, Daniel N wrote: We have not tried this with the python client but I would expect it to work. I will give it a test today and let you know the results and the syntax. Thanks, -- Noah -Original Message- From: mtt-devel [mailto:mtt-devel-boun...@lists.open-mpi.org] On Behalf Of Vallee, Geoffroy R. Sent: Wednesday, December 20, 2017 8:49 AM To: mtt-devel@lists.open-mpi.org Subject: [MTT devel] Send results to multiple databases? Hello, I am currently using the Perl client and 2 different databases: the one from the Open MPI community and a private ORNL-only database. With the current implementation of the Perl client, I cannot send the results to both databases. Is it something that is considered for the Python client? It would be extremely beneficial to me since a full test takes quite some time to run. Thanks, ___ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel ___ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel ___ mtt-devel mailing list mtt-devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/mtt-devel
