mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[GH-ISSUE #349] Travis-CI tests not working? #183
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#183
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @RobbKistler on GitHub (Feb 5, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/349
I don't see the output from the small-integration-test.sh tests in any Travis builds from the last 3 months. Does Travis hide the output? The raw log shows:
Except for the one build that failed:
https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/94634872
That has full output from the small-integration-test.sh
@RobbKistler commented on GitHub (Feb 5, 2016):
Ah -- it looks like Travis just squelches the output when it passes. I expected a "raw" log to contain everything.
@ggtakec or @andrewgaul can you confirm just for my peace of mind?
@ggtakec commented on GitHub (Feb 6, 2016):
@RobbKistler
github.com/s3fs-fuse/s3fs-fuse@7bfaa24d25It seems that changes about this is after this commit.
I think if you need to display detail, I will allow to add -x option in test script.
(It will be removed after test.)
@andrewgaul Do you think about this?
Regards,
@RobbKistler commented on GitHub (Feb 7, 2016):
Even before
7bfaa24there is no output unless the "make check" fails.I now understand that Travis does not display stdio from the test unless there is a failure. I verified by opening a PR with a failing test. I can see all the stdio from "make check".
I will close this issue, everything seems to be working.
@ggtakec commented on GitHub (Feb 7, 2016):
Ok, I appreciate your help.