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

workflows/tidy: Run on ubuntu-20.04. #317

Merged
merged 1 commit into from
Jun 2, 2021

Conversation

rakuco
Copy link
Member

@rakuco rakuco commented Jun 2, 2021

Switch from macos-latest to ubuntu-20.04. There should be no user-visible
changes, but running on Linux makes it easier to test and understand.

Switch from macos-latest to ubuntu-20.04. There should be no user-visible
changes, but running on Linux makes it easier to test and understand.
@rakuco rakuco requested a review from marcoscaceres June 2, 2021 11:05
@rakuco rakuco merged commit b6b4742 into w3c:gh-pages Jun 2, 2021
@rakuco rakuco deleted the run-tidy-on-ubuntu branch June 2, 2021 11:51
rakuco added a commit to rakuco/wake-lock that referenced this pull request Jun 2, 2021
This reverts commit b6b4742. The tidy 5.6.0
package shipped in Debian (up to bullseye at the time of writing) as well as
Ubuntu (up to 21.04 at least) is built with a patch that causes the
configurations settings we pass via `-config .tidyrc` to be ignored when
running (0011-Revert-Remove-unnecessary-AdjustConfig-logic.patch).

The easiest fix is to just revert the commit and continue running tidy on
macos-latest for the time being.
@marcoscaceres
Copy link
Member

@rakuco, sorry to ping you on a totally unrelated bug, but the "[=now visible algorithm=]" ReSpec bug has been fixed... I can't remember where you pinged me about that, but you can now link to it!

If you find that bug again, let me know.

@rakuco
Copy link
Member Author

rakuco commented Jun 4, 2021

Thanks, I originally asked about it in w3c/page-visibility#47. I actually need the "external now hidden algorithm", w3c/page-visibility#72 should make it possible to reference it from this spec.

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.

None yet

2 participants