Github user bzz commented on the issue:
    @1ambda can you please create a new JIRA issue with `flaky-test` label and 
link those 2 CI failures there? It would be great if we could improve this to 
be deterministic and avoid network call by mocking, in subsequent PRs.
    As for useless console output - `/testing/` 
with it's native dependencies build logs seems like a very good candidate to 
redirect output to `/dev/null` 

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

Reply via email to