public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: ci_notify@linaro.org Cc: gdb-testers@sourceware.org Subject: [Linaro-TCWG-CI] 0 commits in gdb: FAIL: 5 regressions: 1 progressions on arm Date: Thu, 15 Feb 2024 00:16:48 +0000 (UTC) [thread overview] Message-ID: <1730394100.16588.1707956210745@jenkins.jenkins> (raw) [-- Attachment #1: Type: text/plain, Size: 2471 bytes --] Dear contributor, our automatic CI has detected problems related to your patch(es). Please find some details below. If you have any questions, please follow up on linaro-toolchain@lists.linaro.org mailing list, Libera's #linaro-tcwg channel, or ping your favourite Linaro toolchain developer on the usual project channel. We appreciate that it might be difficult to find the necessary logs or reproduce the issue locally. If you can't get what you need from our CI within minutes, let us know and we will be happy to help. In gdb_check master-arm after: | 0 commits in gdb FAIL: 5 regressions: 1 progressions regressions.sum: === gdb tests === Running gdb:gdb.arch/arm-disp-step.exp ... FAIL: gdb.arch/arm-disp-step.exp: continue to breakpoint: continue to test_pop_pc_3_check FAIL: gdb.arch/arm-disp-step.exp: continue until exit at arm-disp-step Running gdb:gdb.base/step-over-syscall.exp ... FAIL: gdb.base/step-over-syscall.exp: clone: displaced=on: check_pc_after_cross_syscall: single step over clone final pc FAIL: gdb.base/step-over-syscall.exp: fork: displaced=on: check_pc_after_cross_syscall: single step over fork final pc FAIL: gdb.base/step-over-syscall.exp: vfork: displaced=on: check_pc_after_cross_syscall: single step over vfork final pc ... and 1 more entries progressions.sum: === gdb tests === Running gdb:gdb.base/startup-with-shell.exp ... FAIL: gdb.base/startup-with-shell.exp: startup_with_shell = off; run_args = *.unique-extension: first argument not expanded You can find the failure logs in *.log.1.xz files in - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/1702/artifact/artifacts/00-sumfiles/ The full lists of regressions and progressions as well as configure and make commands are in - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/1702/artifact/artifacts/notify/ The list of [ignored] baseline and flaky failures are in - https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/1702/artifact/artifacts/sumfiles/xfails.xfail The configuration of this build is: CI config tcwg_gdb_check master-arm -----------------8<--------------------------8<--------------------------8<-------------------------- The information below can be used to reproduce a debug environment: Current build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-precommit/1702/artifact/artifacts Reference build : https://ci.linaro.org/job/tcwg_gdb_check--master-arm-build/817/artifact/artifacts
next reply other threads:[~2024-02-15 0:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-15 0:16 ci_notify [this message] 2024-02-15 12:48 ` Thiago Jung Bauermann
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=1730394100.16588.1707956210745@jenkins.jenkins \ --to=ci_notify@linaro.org \ --cc=gdb-testers@sourceware.org \ --cc=linaro-toolchain@lists.linaro.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).