Skip to content

Don't let note fetching stderr appear in logs unless fatal#936

Merged
Eijebong merged 1 commit intotaskcluster:mainfrom
Eijebong:fix-notes-fetching-too-verbose
Apr 16, 2026
Merged

Don't let note fetching stderr appear in logs unless fatal#936
Eijebong merged 1 commit intotaskcluster:mainfrom
Eijebong:fix-notes-fetching-too-verbose

Conversation

@Eijebong
Copy link
Copy Markdown
Contributor

Without this, we let the fetch command write to the logs with a fatal: failed to fetch despite it, in fact, not being fatal. This silences it by capturing stderr instead. I also realized that because of copy/pasting I wasn't using self.run for ls-remote which is inconsistent and might fail in mysterious ways in gecko since it wasn't using self.env

@Eijebong Eijebong requested a review from a team as a code owner April 16, 2026 09:54
@Eijebong Eijebong requested a review from ahal April 16, 2026 09:54
Without this, we let the fetch command write to the logs with a `fatal:
failed to fetch` despite it, in fact, not being fatal. This silences it
by capturing stderr instead. I also realized that because of
copy/pasting I wasn't using `self.run` for ls-remote which is
inconsistent and might fail in mysterious ways in gecko since it wasn't
using `self.env`
@Eijebong Eijebong force-pushed the fix-notes-fetching-too-verbose branch from da35c4c to 3c76eb5 Compare April 16, 2026 09:57
@Eijebong Eijebong merged commit 7e26896 into taskcluster:main Apr 16, 2026
21 of 22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants