-
-
Notifications
You must be signed in to change notification settings - Fork 481
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 Build Errors (In Progress) #58
Comments
Reverted all commits to last commit from this morning, all seems ok now. Travis did report issues of "Apt failures" earlier today which is probably what caused this. Those using auto update should get working copy of latest globalblacklist.conf shortly or you can try force an update to make sure you didn't get the empty file version that occured earlier today. |
Will check this again in the morning on my test repo before doing any more updates. |
@itoffshore No updates until Travis fixes their docker containers. Bash has been totally messed up in their latest updates to Travis. Any "n" character in the output of any echo or printf statements or even variable name is being seen by Travis as a https://blog.travis-ci.com/2017-06-21-trusty-updates-2017-Q2-launch |
⬛ oh dear - one step forward 2 steps back |
Yip, something has gone horribly wrong with Travis. Hope they respond to me
soon.
…On 29 June 2017 at 19:18:40, Stuart Cardall ***@***.***) wrote:
⬛️ oh dear - one step forward 2 steps back
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#58 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJgARd4MXivQf0k4lIkKFNp0znMxEtx0ks5sI9xwgaJpZM4OH_Zk>
.
|
@itoffshore, finally found the culprit pushing out new generator scripts tomorrow and updates will commence. |
@itoffshore we are back online, did some major changes to scripts, all tested and working again. Can you believe in the end a simple IFS="\n" in the generate script caused all the headaches. In the end it led to some much better and cleaner scripting, so all good in the end 😄 |
Travis CI decided to stop playing nice today and started failing on generating the globalblacklist.conf file. Relates to cat and sed errors which did not exist before, perhaps something has changed in Travis CI without users knowing about it?
At the moment a globalblacklist.conf file being generated with no bad bot or referrer information printed into it.
Working on the issue right now, will have working blocker back on track shortly.
The text was updated successfully, but these errors were encountered: