Turn on ADT_ENABLE (Comment: #1)
This will:
- place outgoing requests to debci in data/output/debci_requests.input
- expect to find debci results in data/state/debci.json
For the first point, our debci instance will need to
For the second point, it looks like that data should be coming from http://autopkgtest.kali.org/data/status/kali-rolling/amd64/packages.json; the ideal solution seems to modify /srv/repo.kali.org/bin/run-britney so it retrieves that file before starting britney, although cron'ing that fetch could also be considered an option.
Without implementing any of those 2 points, it should however be safe to deploy this commit right away: outgoing test requests will accumulate in the input file without ever being honored by debci, and the lack of a debci.json result file will just generate a log message (see britney2/britney2/policies/autopkgtest.py#L221).