This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_build/master-aarch64 in repository toolchain/ci/base-artifacts.

discards c48771ff2a 104: force: #522: 6: Success after gcc: 24 commits discards 637f40e07f 103: onsuccess: #520: 6: Success after binutils: 10 commits discards 7e9012ebe2 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] discards bd13d0d077 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] discards 4c7a2bfde8 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] discards 87b6d75254 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] discards b4108e9177 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] discards 7d9053db34 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] discards 8bea3e51d1 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] discards fb7b85c64e 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] discards 62578ed81f 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] discards 10a0e53211 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] discards 55a55e55ba 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] discards 1af392bd3a 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] discards 417c4e60cd 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] discards e2cf55c67d 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] discards 73b8eec50e 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] discards f3edc75ee4 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] discards c27093b87c 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] discards 3e86ebf335 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] discards 7caf027a3c 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] discards e38a559948 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] discards 1ff5cc2dff 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] discards 70947b528f 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] discards dfa4fa25fa 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] discards ec995d1247 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] discards b1509a1b3a 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] discards b09c887cf1 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] discards 8b4d3daa12 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] discards 95e192c94b 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] discards 0a5798987a 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] discards 04d6985166 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] discards 4b3c15944b 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] discards 666c61c9f6 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] discards 499420fd26 70: onsuccess: #486: 5: Success after gdb: 7 commits discards a8e7f7e4d0 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] discards f1dcd0c687 68: force: #484: 6: Success after gdb: 6 commits discards c6bd3d1d10 67: onsuccess: #483: 6: Success after linux: 384 commits discards 4abf329784 66: onsuccess: #482: 6: Success after glibc: 2 commits discards 0aec8c752c 65: onsuccess: #480: 6: Success after gcc: 12 commits discards b3d5380341 64: onsuccess: #479: 6: Success after binutils: 14 commits discards 4826dcd308 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] discards dd8ee2604e 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] discards 2cd1d73b64 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] discards 8f638c106b 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gli [...] discards f8c58cc15b 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] discards d766fce4da 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] discards 0dde4bc4b9 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] discards dad349a20a 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] discards ac7c63004c 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] discards 9def62bb42 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] discards 0f5be40a54 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] discards b13519b73f 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits discards 6c2edee571 51: onsuccess: #465: 1: Success after gcc: 10 commits discards 558ecbecc3 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb0 [...] discards 60e0322a10 49: force: #463: 6: Success after gcc: 18 commits discards b3347347dc 48: onsuccess: #461: 6: Success after binutils: 10 commits discards b3039a2763 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gdb [...] discards c535cec401 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gdb [...] discards fe90abd2b9 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gli [...] discards d7397ab886 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gli [...] discards 2e7ee4eb8c 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] discards 98e4c56406 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] discards 665061138b 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gdb [...] discards 845d36567a 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gli [...] discards c9d05c618c 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gdb [...] discards 2eafd3464f 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] discards 8dded8531f 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gdb [...] discards 0d38177430 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gdb [...] discards 2517ca000d 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gli [...] discards 2d726a6d07 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gli [...] discards 68c273f005 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gdb [...] discards d2d76ad704 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gli [...] discards aedfd8549e 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gli [...] discards 8c12d965c8 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gli [...] discards d21f53136d 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gdb [...] discards 5201bad000 28: onsuccess: #440: 6: Success after binutils/gcc/linux/gli [...] discards 1060bbaf38 27: onsuccess: #439: 6: Success after binutils/gcc/linux/gli [...] discards a6e23e7c13 26: onsuccess: #438: 6: Success after binutils/gcc/linux/gdb [...] discards f5b704be49 25: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] discards 41ea3b47de 24: onsuccess: #436: 6: Success after binutils/gcc/linux/gdb [...] discards de21431ff9 23: onsuccess: 6: Success after binutils/gcc/linux/gdb: 125 commits discards ce1180a6b4 22: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards f49d01904c 21: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] discards ca2bfe21ad 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 6b55c39085 19: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 0f09a2910b 18: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 256ff9fd5e 17: onsuccess: 6: Successful build after binutils/gcc/glibc/ [...] discards a5f72be2ab 16: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 7176367a02 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards a01a35a9bf 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 5f2f3104b6 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards e778742737 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 11fc58e60b 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards 9d5f7616f5 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] discards e2cedde49a 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] discards babefdb731 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] discards 0d8c71c6ca 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 147afa11c7 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards 0e9e81bf1c 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 discards a882aaf253 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 3f5dcb9a0c 4: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 24a7cc9981 5: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new f929a53fc0 6: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new 747d5af537 7: onsuccess: binutils-gcc-linux-glibc-gdb: 6 new b47a965bbb 8: onsuccess: 6: Successful build after binutils/gcc/glibc/g [...] new ce44479c3c 9: onsuccess: 6: Successful build after binutils/gcc/linux/g [...] new 1970f42d8e 10: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 869947d138 11: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new ca9a7ae4cb 12: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 76a17059cd 13: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 0a027030c5 14: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new b4fa7684e5 15: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new bed3761b89 16: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 4bc7a03a1a 17: onsuccess: 6: Successful build after binutils/gcc/glibc/ [...] new ac2c00b4de 18: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 540d13bc85 19: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 470a6a805e 20: onsuccess: 6: Successful build after binutils/gcc/linux/ [...] new 37d00092d6 21: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new d7bd7bb4c9 22: onsuccess: 6: Success after binutils/gcc/linux/glibc/gdb [...] new cdbca0999d 23: onsuccess: 6: Success after binutils/gcc/linux/gdb: 125 commits new b433565a4f 24: onsuccess: #436: 6: Success after binutils/gcc/linux/gdb [...] new 95df15ef3e 25: onsuccess: #437: 6: Success after binutils/gcc/linux/gdb [...] new d47cf42fe9 26: onsuccess: #438: 6: Success after binutils/gcc/linux/gdb [...] new 81e25bafe7 27: onsuccess: #439: 6: Success after binutils/gcc/linux/gli [...] new 9f262e0786 28: onsuccess: #440: 6: Success after binutils/gcc/linux/gli [...] new 26b840a0ea 29: onsuccess: #441: 6: Success after binutils/gcc/glibc/gdb [...] new 061d887d5e 30: onsuccess: #442: 6: Success after binutils/gcc/linux/gli [...] new 88299b41a5 31: onsuccess: #443: 6: Success after binutils/gcc/linux/gli [...] new 80b926af50 32: onsuccess: #444: 6: Success after binutils/gcc/linux/gli [...] new 3e16bc8aa2 33: onsuccess: #445: 6: Success after binutils/gcc/linux/gdb [...] new fadf90d11b 34: onsuccess: #446: 6: Success after binutils/gcc/linux/gli [...] new 82c990bbaa 35: onsuccess: #447: 6: Success after binutils/gcc/linux/gli [...] new e0c98223a2 36: onsuccess: #448: 6: Success after binutils/gcc/glibc/gdb [...] new 596f8a774e 37: onsuccess: #449: 6: Success after binutils/gcc/glibc/gdb [...] new 84f58ba332 38: onsuccess: #450: 6: Success after binutils/gcc/linux/gli [...] new fdd211c86b 39: onsuccess: #451: 6: Success after binutils/gcc/glibc/gdb [...] new 2288000fa9 40: onsuccess: #452: 6: Success after binutils/gcc/linux/gli [...] new 1abe33ebc0 41: onsuccess: #453: 6: Success after binutils/gcc/glibc/gdb [...] new b683f7163d 42: onsuccess: #454: 6: Success after binutils/gcc/linux/gli [...] new 3ecc9e9df6 43: onsuccess: #455: 6: Success after binutils/gcc/linux/gli [...] new 002c1208d3 44: onsuccess: #456: 6: Success after binutils/gcc/linux/gli [...] new 6ea5d401f2 45: onsuccess: #457: 6: Success after binutils/gcc/linux/gli [...] new e35d14fdc5 46: onsuccess: #458: 6: Success after binutils/gcc/linux/gdb [...] new cf1e183416 47: onsuccess: #459: 6: Success after binutils/gcc/linux/gdb [...] new 51e773031c 48: onsuccess: #461: 6: Success after binutils: 10 commits new 691f9a6973 49: force: #463: 6: Success after gcc: 18 commits new 10a34cf794 50: force: #464: 1: Failure after basepoints/gcc-13-2887-gb0 [...] new c8f833d10e 51: onsuccess: #465: 1: Success after gcc: 10 commits new 3702dac9b7 52: onsuccess: #466: 1: Success after binutils/gcc: 25 commits new cd8e7c689f 53: onsuccess: #467: 6: Success after binutils/gcc/linux/gli [...] new d4df2d7ec2 54: onsuccess: #468: 6: Success after binutils/gcc/linux/gli [...] new 29b1086d8e 55: onsuccess: #469: 6: Success after binutils/gcc/linux/gli [...] new 4fed8d01de 56: onsuccess: #470: 6: Success after binutils/gcc/linux/gli [...] new b569722211 57: onsuccess: #471: 6: Success after binutils/gcc/linux/gdb [...] new af072368b4 58: onsuccess: #472: 6: Success after binutils/gcc/linux/gli [...] new 3070c84d40 59: onsuccess: #473: 6: Success after binutils/gcc/linux/gli [...] new d9efc99b6f 60: onsuccess: #474: 6: Success after binutils/gcc/linux/gli [...] new 2f705f510c 61: onsuccess: #475: 6: Success after binutils/gcc/linux/gli [...] new ecf44ff485 62: onsuccess: #476: 6: Success after binutils/gcc/linux/gli [...] new d1c1b08d5c 63: onsuccess: #477: 6: Success after binutils/gcc/linux/gli [...] new 8b7f13a808 64: onsuccess: #479: 6: Success after binutils: 14 commits new c456e15a4a 65: onsuccess: #480: 6: Success after gcc: 12 commits new 23506aa4bf 66: onsuccess: #482: 6: Success after glibc: 2 commits new dee09f2418 67: onsuccess: #483: 6: Success after linux: 384 commits new 4d9f8062b3 68: force: #484: 6: Success after gdb: 6 commits new d0c779aac1 69: force: #485: 5: Failure after gdb-12-branchpoint-2153-gb [...] new bf0892bb32 70: onsuccess: #486: 5: Success after gdb: 7 commits new b5afa700dd 71: onsuccess: #487: 6: Success after binutils/gcc/linux/gli [...] new 8586e4f68b 72: onsuccess: #488: 6: Success after binutils/gcc/linux/gdb [...] new 758d532955 73: onsuccess: #489: 6: Success after binutils/gcc/linux/gli [...] new 8cd82c160d 74: onsuccess: #490: 6: Success after binutils/gcc/linux/gli [...] new b467d7a896 75: onsuccess: #491: 6: Success after binutils/gcc/linux/gli [...] new 902baeefbc 76: onsuccess: #492: 6: Success after binutils/gcc/linux/gdb [...] new 31800a7176 77: onsuccess: #493: 6: Success after binutils/gcc/linux/gli [...] new 478ebea776 78: onsuccess: #494: 6: Success after binutils/gcc/linux/gdb [...] new c8c226f27d 79: onsuccess: #495: 6: Success after binutils/gcc/linux/gli [...] new 8c1568e773 80: onsuccess: #496: 6: Success after binutils/gcc/glibc/gdb [...] new 44fb2d5eac 81: onsuccess: #497: 6: Success after binutils/gcc/linux/gli [...] new 97dd127848 82: onsuccess: #498: 6: Success after binutils/gcc/linux/gdb [...] new 9b59923e6a 83: onsuccess: #499: 6: Success after binutils/gcc/linux/gdb [...] new 8b9392a10d 84: onsuccess: #500: 6: Success after binutils/gcc/linux/gdb [...] new 48c79b97a3 85: onsuccess: #501: 6: Success after binutils/gcc/linux/gli [...] new 921046c67b 86: onsuccess: #502: 6: Success after binutils/gcc/linux/gli [...] new 770f6556ae 87: onsuccess: #503: 6: Success after binutils/gcc/linux/gli [...] new 39b956b0c4 88: onsuccess: #504: 6: Success after binutils/gcc/linux/gli [...] new 5bf2f47e7d 89: onsuccess: #505: 6: Success after binutils/gcc/linux/gli [...] new 142f8fbed8 90: onsuccess: #506: 6: Success after binutils/gcc/linux/gdb [...] new 71fb1b82ec 91: onsuccess: #507: 6: Success after binutils/gcc/linux/gli [...] new 1cd5756461 92: onsuccess: #508: 6: Success after binutils/gcc/linux/gli [...] new e1aafeea20 93: onsuccess: #509: 6: Success after binutils/gcc/linux/gli [...] new b9484abf6d 94: onsuccess: #510: 6: Success after binutils/gcc/linux/gli [...] new 9708bf91af 95: onsuccess: #511: 6: Success after binutils/gcc/linux/gli [...] new e39be3293f 96: onsuccess: #512: 6: Success after binutils/gcc/linux/gli [...] new b71d13eb5c 97: onsuccess: #513: 6: Success after binutils/gcc/linux/gdb [...] new cd32162e2c 98: onsuccess: #514: 6: Success after binutils/gcc/linux/gdb [...] new 074291cc62 99: onsuccess: #515: 6: Success after binutils/gcc/linux/gli [...] new 176549ce7d 100: onsuccess: #516: 6: Success after binutils/gcc/linux/gl [...] new 3a0b7c5971 101: onsuccess: #517: 6: Success after binutils/gcc/linux/gl [...] new 72fa83d6e4 102: onsuccess: #518: 6: Success after binutils/gcc/linux/gl [...] new 76497e70ff 103: onsuccess: #520: 6: Success after binutils: 10 commits new 8550835ac1 104: force: #522: 6: Success after gcc: 24 commits new e0275b1839 105: force: #523: 1: Failure after basepoints/gcc-13-3918-gb [...]

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (c48771ff2a) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_build/master- [...]

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 102 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: 01-reset_artifacts/console.log.xz | Bin 1688 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2700 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 38360 -> 39188 bytes 05-build_abe-gcc/console.log.xz | Bin 213448 -> 209520 bytes 06-clean_sysroot/console.log.xz | Bin 312 -> 0 bytes 07-build_abe-linux/console.log.xz | Bin 9684 -> 0 bytes 08-build_abe-glibc/console.log.xz | Bin 243264 -> 0 bytes 09-build_abe-gdb/console.log.xz | Bin 38164 -> 0 bytes 10-check_regression/console.log.xz | Bin 2960 -> 3688 bytes 10-check_regression/jira-body.txt | 2 +- 10-check_regression/mail-body.txt | 20 +- 10-check_regression/mail-subject.txt | 2 +- 10-check_regression/results.regressions | 10 + 10-check_regression/trigger-bisect | 2 + 10-check_regression/trigger-notify | 0 11-update_baseline/console.log | 38 +-- dashboard/dashboard-generate.sh | 2 +- .../squad-vs-first/score/results-functional.json | 1 - git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 + jenkins/mail-body.draft | 303 +++++++++++++++++++++ jenkins/mail-recipients.draft | 1 + jenkins/mail-subject.draft | 1 + jenkins/notify.sh | 3 + mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 21 +- results | 18 +- 29 files changed, 390 insertions(+), 64 deletions(-) delete mode 100644 06-clean_sysroot/console.log.xz delete mode 100644 07-build_abe-linux/console.log.xz delete mode 100644 08-build_abe-glibc/console.log.xz delete mode 100644 09-build_abe-gdb/console.log.xz create mode 100644 10-check_regression/results.regressions create mode 100644 10-check_regression/trigger-bisect create mode 100644 10-check_regression/trigger-notify delete mode 100644 dashboard/squad-vs-first/score/results-functional.json create mode 100644 jenkins/jira-status.draft create mode 100644 jenkins/mail-body.draft create mode 100644 jenkins/mail-recipients.draft create mode 100644 jenkins/mail-subject.draft create mode 100755 jenkins/notify.sh