-
Related to #227 (''Stop all testing and submit what you have now''), but instead of stopping MTT, we will be tweaking it's run-time options midway through a run. The use cases I have in mind are:
- Ch…
-
MTT can progress for quite a long time before encoutering a fatal error in one of it's modules. It should warn about an upcoming error of this kind, that is, do a quick `eval "use Foo.pm;` on each of …
-
Trim out unneeded !JavaScript in the MTT reporter emails. E.g., there does not seem to be a reason to have !JavaScript functions that provide pop-up select menus in the email (as I assume most clients…
-
Add more test suites from ompi-tests to the MTT sample INI file (i.e., make sure they work, submit results back to the database, etc.). Here's two to add:
- cxx-test-suite: should be a simple configu…
-
Occasionally there are MTT database submission errors (see #375). For each error, an email is sent to the user who submitted the MTT data to the server. This is a good thing ... to a point. There n…
-
## Problem
When visiting https://heaps.io/ for the first time, one of the first things I noticed was a grammar error (bolded below) in the lead paragraph:
> Heaps.io is a mature cross platform g…
-
We could use `Cmdliner` instead of [the manual parsing of CLI argument](https://github.com/Zilliqa/scilla/blob/55f1b64dba4db9096acea243e0e71aaa3029d3aa/src/base/RunnerUtil.ml#L207).
This will allow…
-
If results to a query go to a second page, the results on the second page seem unreliable. See mtt-devel mail archives:
http://www.open-mpi.org/community/lists/mtt-devel/2012/05/0589.php
-
-