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: Sun, 15 Oct 2023 18:51:06 +0000 (GMT)	[thread overview]
Message-ID: <20231015185106.155E43858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:f59981d56406c2284e42ca5f33c0f971f10f8e9b

commit f59981d56406c2284e42ca5f33c0f971f10f8e9b
Author: Eric Gallager <egallager@gcc.gnu.org>
Date:   Sun Oct 15 14:50:48 2023 -0400

    Update linux.yaml
    
    docbuilding is annoying

Diff:
---
 .github/workflows/linux.yaml | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/.github/workflows/linux.yaml b/.github/workflows/linux.yaml
index 7c0e09cd2d8..abc707f07c2 100644
--- a/.github/workflows/linux.yaml
+++ b/.github/workflows/linux.yaml
@@ -109,9 +109,8 @@ jobs:
         if: success()
         run: |
           cd ../build
-          echo "make dvi-fixincludes" && time make dvi-fixincludes
-          echo "make pdf" && time make pdf
-          echo "make html" && time make html
+          echo "make pdf" && (time make pdf-fixincludes) && echo "pdfs done"
+          echo "make html" && (time make html) && echo "html done"
 
       - name: Make
         if: success()
@@ -124,8 +123,8 @@ jobs:
         if: success()
         run: |
           cd ../build
-          echo "make info" && time make info
-          echo "make dvi" && time make dvi
+          echo "make info" && (time make info) && echo "info done"
+          echo "make dvi" && (time make dvi) && echo "dvi done"
 
       - name: Debug failure
         if: failure()

             reply	other threads:[~2023-10-15 18:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-15 18:51 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-16  2:23 Eric Gallager
2023-10-15 20:04 Eric Gallager
2023-10-15 19:35 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=20231015185106.155E43858D32@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).