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

Intentionally break the CI build to test TravisBuddy #1

Closed
wants to merge 6 commits into from

Conversation

apjanke
Copy link
Owner

@apjanke apjanke commented Jan 16, 2019

This is a dummy PR to test our new TravisBuddy integration.

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 17e3cef0-19c8-11e9-b6ef-27c2ed554f09

@TravisBuddy
Copy link

Hey @apjanke,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: ab539d70-19cb-11e9-b6ef-27c2ed554f09

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: a29afd80-19cc-11e9-b6ef-27c2ed554f09

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 017900b0-19d0-11e9-b6ef-27c2ed554f09

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 37e76850-19dd-11e9-b6ef-27c2ed554f09

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 468f2b20-19df-11e9-b6ef-27c2ed554f09

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: eea4d040-19e3-11e9-be88-4fff0e4b7d25

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 47ad6830-19e6-11e9-be88-4fff0e4b7d25

@TravisBuddy
Copy link

Travis tests have failed

Hey @apjanke,
Please read the following log in order to understand the failure reason.
It'll be awesome if you fix what's wrong and commit the changes.

TravisBuddy Request Identifier: 2a5659c0-19e8-11e9-be88-4fff0e4b7d25

@apjanke apjanke closed this Jan 17, 2019
@apjanke apjanke deleted the test-travis-buddy branch January 17, 2019 01:05
@TravisBuddy
Copy link

Hey @apjanke,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: a89ff280-19f4-11e9-be88-4fff0e4b7d25

@TravisBuddy
Copy link

Hey @apjanke,
Something went wrong with the build.

TravisCI finished with status errored, which means the build failed because of something unrelated to the tests, such as a problem with a dependency or the build process itself.

View build log

TravisBuddy Request Identifier: ca6a0090-19f4-11e9-be88-4fff0e4b7d25

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