Skip to content

Conversation

@dustymabe
Copy link
Member

Otherwise only info level messages will go to the console of the machine.

We were digging into a new instance of [1] and found that we weren't really getting debug messages on the console of the machine (which means no new clues as to why the tests are timing out). Turns out this is why we weren't getting those new debug messages we thought we would get.

[1] coreos/fedora-coreos-tracker#1796

Otherwise only `info` level messages will go to the console
of the machine.

We were digging into a new instance of [1] and found that we
weren't really getting debug messages on the console of the
machine (which means no new clues as to why the tests are
timing out). Turns out this is why we weren't getting those
new debug messages we thought we would get.

[1] coreos/fedora-coreos-tracker#1796
@dustymabe dustymabe enabled auto-merge (rebase) November 1, 2024 20:31
Copy link
Member

@ravanelli ravanelli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@dustymabe dustymabe merged commit ea1ad34 into coreos:main Nov 1, 2024
5 checks passed
@dustymabe dustymabe deleted the dusty-testiso-debug branch November 1, 2024 22:30
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.

4 participants