The civis-python smoke tests on Civis Platform run two CivisML training jobs. It's come to my attention that these CivisML jobs have confused our internal product team, since these jobs are incorrectly counted as genuine CivisML usage. This PR explicitly marks these CivisML jobs launched by civis-python smoke tests as unrelated. I've just tested this change and everything worked as expected and desired:
[x] (For Civis employees only) Reference to a relevant ticket in the pull request title
[x] Description of change in the pull request description
The civis-python smoke tests on Civis Platform run two CivisML training jobs. It's come to my attention that these CivisML jobs have confused our internal product team, since these jobs are incorrectly counted as genuine CivisML usage. This PR explicitly marks these CivisML jobs launched by civis-python smoke tests as unrelated. I've just tested this change and everything worked as expected and desired: