Don't actually print anomalies in TTRR

[samestep]

This PR disables the bulk of the output for test time regression reporting, since it's obscuring more important signal (especially in cases where shards are shifting around).

Test plan:

python test/test_testing.py

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit c141d9f (more details on the Dr. CI page):

---

• 1/2 failures possibly* introduced in this PR
  • 1/1 non-scanned failure(s)
• 1/2 tentatively recognized as flaky ❄️
  • Click here to rerun these jobs

---

❄️ 1 failure tentatively classified as flaky

but reruns have not yet been triggered to confirm:

pytorch_cpp_doc_build (1/1)

Step: "Doc Build and Push" (full log | diagnosis details | 🔁 rerun) ❄️

Mar 16 19:08:02 E: Unable to correct problems, you have held broken packages.

Mar 16 19:08:02 Building dependency tree...
Mar 16 19:08:02 Reading state information...
Mar 16 19:08:02 Some packages could not be installed. This may mean that you have
Mar 16 19:08:02 requested an impossible situation or if you are using the unstable
Mar 16 19:08:02 distribution that some required packages have not yet been created
Mar 16 19:08:02 or been moved out of Incoming.
Mar 16 19:08:02 The following information may help to resolve the situation:
Mar 16 19:08:02 
Mar 16 19:08:02 The following packages have unmet dependencies:
Mar 16 19:08:02  doxygen : Depends: libclang1-3.8 (>= 3.2) but it is not going to be installed
Mar 16 19:08:02 E: Unable to correct problems, you have held broken packages.


Exited with code exit status 100

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

[facebook-github-bot]

@samestep has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[ezyang]

Is there any way to get the anomalies now, then?

[samestep]

Is there any way to get the anomalies now, then?

@ezyang Not for PRs, but on master all the data is uploaded to S3 so it can be analyzed by other scripts such as tools/test_history.py.

[janeyx99]

:( Sad that this is getting disabled, but I do agree the sharding with the regression reporting is noisy. I hope we can add back some sort of regression reporting (maybe GitHub comment?) that is more visible and not as obscuring for other logs.

[facebook-github-bot]

@samestep merged this pull request in c0fafcc.