Periodic automated testing can fail a package because of a dependency but doesn't update failed dependency status

[bcurran3]

Periodic automated testing can fail a package because of a dependency but doesn't update the failed dependency status.

EXAMPLE:
Recent periodic re-testing of deprecated package https://chocolatey.org/packages/btsync/2.3.6.20170529 failed due to it's dependency replacement package https://chocolatey.org/packages/resilio-sync-home failing as a dependency. BUT https://chocolatey.org/packages/resilio-sync-home didn't get updated in the database with a "red dot." Yes, https://chocolatey.org/packages/resilio-sync-home will later get re-tested and fail, but why do the work again when the result is already known?

[AdmiringWorm]

IMO, deprecated packages should probably be exempted from the periodic running of the validator, especially considering they most likely wouldn't be updated anyhow.

[bcurran3]

I would most certainly agree with that!