From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [ISSUE] Travis CI times out and build fails
Date: Mon, 04 Nov 2019 17:11:08 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16113@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]
New issue by reback00 on void-packages repository
https://github.com/void-linux/void-packages/issues/16113
Description:
### System
(Not relevant)
### Expected behavior
Being able to pass the build of my [`textadept`](https://github.com/void-linux/void-packages/pull/15627) package and packages by others (which are failing without any reason) without problems.
### Actual behavior
Build fails [randomly](https://github.com/void-linux/void-packages/pull/15627#issuecomment-549231300) even if I push the same code.
I went through the PRs done by others. It seems builds longer than 10 minutes are sure to fail: [https://imgur.com/03flUd7](https://imgur.com/03flUd7)
The only recent build that passed (while writing this) was `rxvt-unicode` and `anydesk` which turned out Green _probably_ because the build completed in less than 10 minutes. This is my basic understanding, I'm not sure about that.
### Steps to reproduce the behavior
Force pushing my package `textadept` does not pass the build.
Pushing almost any package which takes more than 10 minutes to build, should raise this issue.
next reply other threads:[~2019-11-04 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-04 16:11 voidlinux-github [this message]
2019-11-04 16:18 ` voidlinux-github
2019-11-05 23:55 ` voidlinux-github
2019-11-05 23:55 ` [ISSUE] [CLOSED] " voidlinux-github
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16113@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).