Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cron jobs must not print anything to stdout/stderr #1289

Open
fedora-copr-github-bot opened this issue Nov 17, 2022 · 1 comment
Open

cron jobs must not print anything to stdout/stderr #1289

fedora-copr-github-bot opened this issue Nov 17, 2022 · 1 comment
Labels

Comments

@fedora-copr-github-bot
Copy link
Collaborator

fedora-copr-github-bot commented Nov 17, 2022

Original issue: https://pagure.io/copr/copr/issue/1289
Opened: 2020-02-25 07:26:49
Opened by: praiskup

If something is printed to stdout/stderr, whole infra team is notified via email.

That said, .. we should change the simple printing to logging, and keep stdout
stderr clean.


praiskup commented at 2020-02-25 08:28:25:

No, the mail goes to root, which goes to root@fedoraproject.org (per
previous discussion with @kevin).


praiskup commented at 2020-02-26 15:18:29:

For now applied this:
https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=a6f03027a19a2b21571bf19762eae6aa4427f746


praiskup commented at 2021-04-19 10:27:15:

the ansible.git hashes were recalculated after push-force, so the link above doesn't work ... I've set MAILTO=praiskup@redhat.com to not bother fedora infra.

So the problem still exists, we should minimize the cron job output and perhaps start sending the leftovers to copr-team@.

@praiskup
Copy link
Member

Changed to 'copr-team@' for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Someday in future
Development

No branches or pull requests

2 participants