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

Write non-OK harness statuses to a log file #150

Closed
wants to merge 2 commits into from

Conversation

foolip
Copy link
Member

@foolip foolip commented Feb 16, 2023

No description provided.

@foolip foolip force-pushed the non-ok-harness-statuses branch 3 times, most recently from 1ff6967 to 7bfe62c Compare February 16, 2023 14:28
@foolip
Copy link
Member Author

foolip commented Feb 16, 2023

I've triggered https://github.com/web-platform-tests/results-analysis/actions/runs/4195848233 to test this. If that pushes a non-ok-harness-statuses.txt file to the non-ok-harness-statuses-test branch it worked.

@foolip
Copy link
Member Author

foolip commented Feb 16, 2023

The remaining step after this will be a setup similar to web-platform-tests/interop#288 that copies this file into the interop repo, and sends PRs if it changes.

Copy link
Contributor

@DanielRyanSmith DanielRyanSmith left a comment

Choose a reason for hiding this comment

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

The logic looks good to me barring some comments

.github/workflows/update_gh_pages.yml Outdated Show resolved Hide resolved
.github/workflows/update_gh_pages.yml Outdated Show resolved Hide resolved
@foolip
Copy link
Member Author

foolip commented Feb 15, 2024

Abandoning this, we could never agree on the best approach in the interop team, so the status quo stands.

@foolip foolip closed this Feb 15, 2024
@foolip foolip deleted the non-ok-harness-statuses branch February 15, 2024 05:28
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