-
-
Notifications
You must be signed in to change notification settings - Fork 22.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 CI: Test project exporting/script running in the headless editor #31013
Travis CI: Test project exporting/script running in the headless editor #31013
Conversation
I wouldn't include test projects in this repo, they should be in a dedicated Git repo which can be cloned during CI. |
@akien-mga Should we create a dedicated repository with the test project? We could reuse godot-tests, but then, we'd be cloning some data we don't use. (It's not that large right now, so it might not be an issue after all.) |
I think we can reuse godot-tests for now. |
5d8593a
to
dd7e888
Compare
dd7e888
to
a365e04
Compare
a365e04
to
e2eb3f7
Compare
e2eb3f7
to
5efd436
Compare
Thanks! |
There's something wrong with return values, seems like it's returning 0 for failed jobs with For example, I have rebased PR, it gone badly and build failed for all platforms, but Travis registered all except "Linux headless editor" as passed. Build log: https://travis-ci.org/godotengine/godot/builds/576809375
|
Seems to be a 5 year old bug that upstream doesn't care about. travis-ci/travis-ci#1066
Travis: Fix builds wrongly reporting success after #31013
Seems to be a 5 year old bug that upstream doesn't care about. travis-ci/travis-ci#1066
This makes sure regressions in the editor CLI functionality are caught early on.
Suggestions for making the test process cleaner or more complete are welcome 🙂
See #17408.