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

lilypond: update to 2.22.0 #27849

Merged
merged 2 commits into from Jan 20, 2021
Merged

lilypond: update to 2.22.0 #27849

merged 2 commits into from Jan 20, 2021

Conversation

newbluemoon
Copy link
Contributor

No description provided.

@ericonr
Copy link
Member

ericonr commented Jan 20, 2021

Not sure why tests failed in CI, would be nice to track down. I could run them successfully locally :)

@ericonr ericonr merged commit f60b617 into void-linux:master Jan 20, 2021
@newbluemoon newbluemoon deleted the lilypond branch January 20, 2021 05:31
@newbluemoon
Copy link
Contributor Author

Maybe the test fails because of some parallelism issue. The test runs multiple instances of lilypond to create some output files which are then compared to a baseline; maybe a check is run before an output file is created. I can try to disable parallelism for checking with the next update.

However, the intention of the test is to compare changes a developer made against a release version; i.e. a baseline is created regarding the release and the test checks if/how the developer’s changes deviate from that baseline.
So other than checking that lilypond runs correctly the test here is of not much use, because the baseline and what is checked against it is the same, apparently. ;)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants