The Job and Toolchain columns are redundant, Runtime is all we need:

I see this very often when our users are presenting BDN results at conferences|meetups etc

The Job column should remain visible when the user has set the Job id in explicit way.

/cc @stephentoub

It would be nice to have the option which specifies the list of custom DNS resolver addresses (comma-separated list). Maybe It works only on non Windows systems.

Example:

ali --resolvers="1.2.3.4,192.168.11.1:53" http:host.xz

We can borrow around here.

For different use cases, like bencheeorg/benchee_html#10 it'd be great to have statistics about statistics - what I'd call "meta statistics" - although there's probably some better real statistics name for this :)

What should be in there (that I know of so far):

• job size (how many jobs are in there)
• minimum of run times over all jobs
• maximum of run times over all jobs

This should be

There seem to be some vulnerabilities in our code that might fail easily. I suggest adding more unit tests for the following:

• Custom agents (there's only VPG and PPO on CartPole-v0 as of now. We should preferably add more to cover discrete-offpolicy, continuous-offpolicy and continuous-onpolicy)
• Evaluation for the Bandits and Classical agents
• Testing of convergence of agents as proposed i