public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Eric Gallager <egallager@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/egallager/heads/CI)] Update linux.yaml Date: Mon, 16 Oct 2023 02:23:23 +0000 (GMT) [thread overview] Message-ID: <20231016022323.C87653858D32@sourceware.org> (raw) https://gcc.gnu.org/g:59eb82bfdc1ce4a1e8c5f576e4cbd0b7878f5dfc commit 59eb82bfdc1ce4a1e8c5f576e4cbd0b7878f5dfc Author: Eric Gallager <egallager@gcc.gnu.org> Date: Sun Oct 15 22:21:59 2023 -0400 Update linux.yaml last build timed out; let's see if we can fix that... Diff: --- .github/workflows/linux.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/.github/workflows/linux.yaml b/.github/workflows/linux.yaml index 7b9d9741782..1ab67a82b57 100644 --- a/.github/workflows/linux.yaml +++ b/.github/workflows/linux.yaml @@ -21,6 +21,7 @@ jobs: build: name: ${{ matrix.name }}-build runs-on: ubuntu-latest + timeout-minutes: 720 strategy: matrix: include: @@ -36,7 +37,7 @@ jobs: - name: Install dependencies run: | sudo apt-get -qq update - sudo apt install -y gcc-multilib build-essential flex zlib1g-dev gnat gdc expect dejagnu libc-dev libc-devtools texlive findutils + sudo apt install -y gcc-multilib build-essential flex zlib1g-dev gnat gdc expect dejagnu libc-dev libc-devtools texlive findutils binutils autogen gettext - name: Install dependencies for aarch64 if: success() && contains(matrix.target, 'aarch64') @@ -109,6 +110,7 @@ jobs: cd ../build if test -x "$(which nproc)"; then echo "nproc says that we can use $(nproc) build jobs"; else echo "error: missing nproc!" >&2 && exit 1; fi time (make -j"$(nproc)" | tee build.log) + if test -e build.log; then stat build.log && wc -l build.log; fi - name: Debug failure if: failure() @@ -148,6 +150,6 @@ jobs: if test -x /usr/bin/x86_64-linux-gnu-gcc; then /usr/bin/x86_64-linux-gnu-gcc -v; elif test -x ../build/gcc/xgcc; then ../build/gcc/xgcc --v; fi cd ../build if test -e build.log; then make warning.log; fi - time make -k check + time (make -k -j"$(nproc)" check RUNTESTFLAGS="compile.exp dg-torture.exp execute.exp old-deja.exp" | tee testsuite_output.log) if test -e warning.log; then make mail-report-with-warnings.log; else make mail-report.log; fi if test -x mail-report-with-warnings.log; then ./mail-report-with-warnings.log; elif test -x mail-report.log; then ./mail-report.log; fi
next reply other threads:[~2023-10-16 2:23 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-16 2:23 Eric Gallager [this message] -- strict thread matches above, loose matches on Subject: below -- 2023-10-28 17:48 Eric Gallager 2023-10-17 0:19 Eric Gallager 2023-10-16 22:50 Eric Gallager 2023-10-16 21:55 Eric Gallager 2023-10-16 21:55 Eric Gallager 2023-10-16 21:03 Eric Gallager 2023-10-16 8:50 Eric Gallager 2023-10-16 8:31 Eric Gallager 2023-10-16 8:27 Eric Gallager 2023-10-16 5:29 Eric Gallager 2023-10-16 3:57 Eric Gallager 2023-10-15 20:04 Eric Gallager 2023-10-15 19:35 Eric Gallager 2023-10-15 18:51 Eric Gallager 2023-10-15 11:03 Eric Gallager 2023-10-15 10:38 Eric Gallager 2023-10-15 9:35 Eric Gallager 2023-10-15 9:23 Eric Gallager 2023-10-15 9:16 Eric Gallager 2023-10-15 9:09 Eric Gallager 2023-10-15 9:09 Eric Gallager
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=20231016022323.C87653858D32@sourceware.org \ --to=egallager@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).