-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Travis: Issue build error when Parsedown::version isn't up-to-date #560
Conversation
The failing build doesn't seem to be related to this PR, if you want to test it you could try restarting the build. |
.travis.yml
Outdated
@@ -26,3 +26,4 @@ install: | |||
script: | |||
- vendor/bin/phpunit | |||
- vendor/bin/phpunit test/CommonMarkTestWeak.php || true | |||
- [ -z "$TRAVIS_TAG" ] || [ "$TRAVIS_TAG" == "$(php -r 'require("Parsedown.php"); echo Parsedown::version;')" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL $TRAVIS_TAG
😃
Indeed, very strange... It says "Partially Degraded Service" - see https://www.traviscistatus.com/ Can you try restarting the build? |
Hmm... maybe we should give it a few mins
I think you can usually do something like git commit --amend
git push --force to do that ;-) (new commit hash), make sure you pull your changes down first though aha (I can't restart the build from my end) |
As a collaborator you can restart builds by navigating to https://travis-ci.org/erusev/parsedown/builds/347396937, logging in and clicking the "Restart" button 😉 Anyway, it seems like there was some weird escaping issue I've never experienced before... It works now 😃 |
Weird... Maybe Travis needs some time to update the permissions? Because Collaborators definitly have the right to restart builds (I'm using it on some repos I'm a Collaborator of). You might want to try it: Simply create a tag "test" (something that isn't seen as version constraint by Packagist/composer), push the tag and wait for the notification mail that the build failed. You can delete the tag afterwards ( |
Looks like it works :) |
🎉 😄 |
As suggested in #556 (comment) 😃