For the new test D17, the SUT relies upon a CRL published by the DCDT root CA "CN=dcdt31prod.sitenv.org_ca_root".
It looks like this CA is publishing a new CRL every second (or possibly "on demand"), but the CRL is always stale, listing a nextUpdate time a few minutes in the past.
From RFC5280:
5.1.2.5. Next Update
This field indicates the date by which the next CRL will be issued.
The next CRL could be issued before the indicated date, but it will
not be issued any later than the indicated date.
So, the nextUpdate time should be a time in the future. Presented with a stale CRL, a SUT would conclude that the revocation status is indeterminate for any cert issued by that CA.
I would suggest that, since these are essentially static CRLs, you could use a CRL nextUpdate time 24 hours in the future (or at least far enough in the future that a SUT can reliably retrieve it before it becomes stale).
For reference, here are some nextUpdate times from today:
CRL retrieved at / nextUpdate time
8/28/16 11:06:42 PDT / 8/28/16 11:04:27 PDT
8/28/16 11:06:58 PDT / 8/28/16 11:04:43 PDT
8/28/16 11:07:15 PDT / 8/28/16 11:04:59 PDT
Thank you,
Luis