Lucas Meneghel
Lucas Meneghel
A few changes to make it easier to run tests located inside the tests/ dir, and a few other fixes.
Implement support for parameterized jobs - Say SleepTest declares that it support SleepTime parameter and then tester can say in CLI (or rpc) $ .... job create --param='SleeptTime:20' -t SleepTest...
Definitions: - Testgrid: the infrastructure used to run our tests in our lab. It's composed of test runner(s), RPC server(s), database(s), infrastructure for provisioning, etc. - Autotest user: submits jobs...
Disclaimer: I'm by no means a specialist in the fine art of writing user stories, just thought I'd write how I envision this functionality to work. My final goal is...
@nacc, If you'd have time, could you write a mini doc on setting up LDAP authentication on the wiki? It seems like the sysadmin doc session on the wiki is...
This would greatly benefit our ability to test fixes found by downstream packagers. We don't know yet how hard it will be to do it, let's work on it.
We already have rudimentary debian packages, but they are just basically API providers, all else must be worked on.
Allow to schedule jobs based on machine hardware capabilities, for example: Number of CPUS Available Memory Virtualization support among others
A 'machine reserve' mode is a known feature for other testing systems, where you may provision one bare metal machine with the OS of choice and use the installed machine...
@ldoktor pointed out here https://github.com/autotest/autotest-client-tests/pull/1 That the setup() stage of a client module is being skipped. I'm not aware of any reason why this would be happening, but we need...