driver / standard (pull_request) Successful in 15s
driver / lint (pull_request) Successful in 13s
driver / types (pull_request) Failing after 56s
driver / test (3.12) (pull_request) Failing after 46s
driver / lowest (pull_request) Failing after 20s
driver / test (3.13) (pull_request) Failing after 47s
driver / build (pull_request) Successful in 27s
driver / security (pull_request) Failing after 1m4s
CI / driver (pull_request) Failing after 2m18s
driver / publish (pull_request) Skipped
napalm-linux now brings napalm-device-types' POSIX scheduled jobs, with Debian's paths. On QTS they are wrong: the crontab that survives a boot is /etc/config/crontab (admin's, no user field), crond runs a copy of it, and a change made only through crontab is gone after the next boot. BusyBox crond reads no /etc/crontab, cron.d, run-parts or anacron, and there is no systemd. QtsScheduledJobsMixin reads /etc/config/crontab as admin's and the other users' crontabs from crond's spool in one round trip, and writes the file first, then loads it and restarts crond. The firmware's own lines are platform by a conservative command list and only run, until a real box shows whether QTS leaves one switched off alone. An application's job is marked lines in admin's crontab; a run is bounded without timeout, which QTS's BusyBox cannot be relied on to have. Requires napalm-device-types 4.26.0 and napalm-linux 0.16.0. Closes #17