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 22:50:05 +0000 (GMT) [thread overview] Message-ID: <20231016225005.E2C5E3858D33@sourceware.org> (raw) https://gcc.gnu.org/g:ea929b66a84e26cf9d5a4ab256d780cf17c57591 commit ea929b66a84e26cf9d5a4ab256d780cf17c57591 Author: Eric Gallager <egallager@gcc.gnu.org> Date: Mon Oct 16 18:49:44 2023 -0400 Update linux.yaml try seeing if there are more ways to upload logfiles Diff: --- .github/workflows/linux.yaml | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/.github/workflows/linux.yaml b/.github/workflows/linux.yaml index d1b0fbfa4369..ead4304f5112 100644 --- a/.github/workflows/linux.yaml +++ b/.github/workflows/linux.yaml @@ -117,10 +117,14 @@ jobs: run: | if test -r build.log; then grep -i "error:" build.log; \ elif test -r ../build/build.log; then grep -i "error:" ../build/build.log; \ - else \ + elif test -e ../build/Makefile; then \ sudo apt install remake; \ cd ../build; \ remake -dpPw --trace=full; \ + elif test -d ../build; then \ + cd ../build && ls; \ + else \ + pwd && ls; \ fi - name: Make docs (post-build) @@ -154,9 +158,13 @@ jobs: if test -e warning.log; then make mail-report-with-warnings.log; else make mail-report.log; fi if test -x "$(which Mail)"; then \ if test -x mail-report-with-warnings.log; then \ + echo "attempting to send mail-report-with-warnings.log"; \ ./mail-report-with-warnings.log; \ + stat mail-report-with-warnings.log; \ elif test -x mail-report.log; then \ + echo "attempting to send mail-report.log"; \ ./mail-report.log; \ + stat mail-report.log; \ elif test -e testsuite_output.log; then \ echo "TODO: figure out a way to send testsuite_output.log"; \ else \ @@ -165,3 +173,13 @@ jobs: else \ echo "Warning: \"Mail\" program is missing, so skipping emailing of testresults!"; \ fi + + - name: Upload a Build Artifact + uses: actions/upload-artifact@v3.1.3 + with: + # Artifact name + name: logfiles + # A file, directory or wildcard pattern that describes what to upload + path: | + ./*.log + ../build/*.log
next reply other threads:[~2023-10-16 22:50 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-16 22:50 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 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 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=20231016225005.E2C5E3858D33@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).