In the code comments for is_test_running, the only requester information that is actually iterated on is REQUESTINFO, so the semicolon-separated string with job information in it. It seemed to be much easier to treat that simply as a unique identifier than as a string we actually parse.
When the subdictionaries are being recursed through, the requester key is not even considered.
Yes.
In the code comments for is_test_running, the only requester information that is actually iterated on is REQUESTINFO, so the semicolon-separated string with job information in it. It seemed to be much easier to treat that simply as a unique identifier than as a string we actually parse.
When the subdictionaries are being recursed through, the requester key is not even considered.
Let me know if you have any further questions.