Hide normal builds of servers reporting crossruby#646
Merged
Conversation
The crossruby host accidentally ran normal master/4.0-3.3 builds, so its logs appeared in both tables. Skip non-cross reports from a server while it has crossruby reports. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The crossruby host accidentally ran normal
masterand 4.0-3.3 builds, so its logs appear in both the normal table and the crossruby table on rubyci.org. The reports view now skips non-cross reports from any server that currently has crossruby reports, so only the crossruby table shows that host. Other servers are unaffected, and if the accidental runs stop the filter naturally disengages once the crossruby reports age out.Generated with Claude Code