Tango
Tango copied to clipboard
autolab
Standalone RESTful autograding service
## Description - This PR adds the option to specify allowed outgoing IPs on a per-job level. ## Motivation and Context - Adds a security option for autograding containers. -...
I have encountered a couple of situations in testing where the preallocator's machines datastructure got out of sync. There were machine ids in the list that no longer had an...
From Chaskiel re: an error that recently occured on CMU prod The error was triggered by an operating system error (an LDAP lookup failed when tango ssh'd to the docker...
The follow two bugs, combined, prevent pending jobs from being executed: * When number of jobs is larger than number of vms in free pool, jobManager dies. * When jobManager...
Some autograding scripts require environment variables to be passed in. For example, if the username of the user who submitted the job is needed in the autodriver's environment `localDocker` vmms:...
We're testing out a new autograder image on AutoLab, but after making a submission and the autograder spinning up, the launched job simply runs forever. ### Expected Behavior I would...
### Expected Behavior Offer a way to preserve the job list before Tango exits. ### Actual Behavior Currently, the completed job list is cleared when Tango restarts.
Jobs can pick which VMMS they want to run on. Some can run on Tashi and some on Distributed Docker.
If volumes directory is not created and config is `*`, then it should be automatically created.
There are potential concurrency issues in parts of the codebase that results in execution traces which causes Tango to behave anomalously. See: https://github.com/autolab/Tango/issues/138 (was replicable until very recently, but we...
