This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_build/master-aarch64 in repository toolchain/ci/base-artifacts.
discards bebf3e43f8 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards df3e0d3cd1 152: force: #1605: 7: Success after gcc: 9 commits discards 007d0453e7 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards c775b6f7a7 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 7663cac513 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 50f369be5d 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 2e8581914e 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 67814c8298 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 0a1d4f7471 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards adc3de6f64 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards cf9a6a0507 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards b274c637b4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 80a381a38f 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 7e0f7b0b44 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards af5d47d89c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards ce013099e6 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 1e28f70a90 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards 4203bcf32b 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 3278a84788 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 5bcf600492 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards e9e5acfad3 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 50d5aea325 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 4e01175e2b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 5c98ad1f96 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 085d52e234 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 0cfebf62d6 128: onsuccess: #1579: 7: Success after linux: 12 commits discards bbe18347d2 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 3336ba57a3 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards aa5267ab95 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 060ef40ad8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 94609b40e2 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 2deaa7835b 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 48caf50364 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 80dc671134 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 87b299e94d 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 87dc270594 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards c711fefa1a 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 90696fe10d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 951e967c94 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards a31debcfec 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards df66d0b2e7 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards b1369d2cee 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards c90e087657 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 2f8422c500 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 0728d175ba 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 1b87aff227 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 5a1a901e9f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 4b3d075fb8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 2d0aa2f079 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards e830529b3b 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 80321aeea7 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 2831dda4c1 102: force: #1551: 1: Failure after gcc: 306 commits discards f77e74136d 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards fb245099e0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards f32f52e1a9 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 2e5c857f38 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 74a00630db 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 7463a4c5d9 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1768a183e4 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 2928b76cbb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 1fa6474632 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards a43950e381 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 62ac08ab31 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards ef7c6a9f3b 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards dd97a1a3a3 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 5dfb6931d7 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards a19d6b1da7 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 59f8d73f28 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards e4f6822e54 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 77ecba4f11 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 89706d6337 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 6bc49fe127 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 0fa15d499c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 01090beebb 80: onsuccess: 7: Successful build after linux: 44 commits discards d32b0ba3a5 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards c24eaa66d7 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards f884ea7077 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 49ab0f27e6 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 192d492bdc 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 7854fd4fa8 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 90de574951 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8d775714bf 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards aabe12511b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 0888c92317 70: onsuccess: 7: Successful build after gcc: 4 commits discards ae101f2e4f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards fe4170ff5e 68: onsuccess: 7: Successful build after linux: 6 commits discards a338fd9989 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards 0d8b3f0c2a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 286d825e8e 65: onsuccess: 7: Successful build after binutils: 3 commits discards f3af2a8704 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards fbb40b14c1 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 2938c17491 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 8ab93d104f 61: onsuccess: 4: Successful build after gcc: 5 commits discards 975ed19c02 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 88ebebefeb 59: force: 7: Successful build after gcc: 3 commits discards f4c4463a6e 58: onsuccess: 7: Successful build after glibc: 2 commits discards 78f0e8095f 57: onsuccess: 7: Successful build after gcc: 7 commits discards a12191cb08 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 364da07488 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1716a17134 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards edb9ccd60c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new e47554ec66 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 43c056860c 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 7242398605 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 22157db12c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 06f3bfed4f 57: onsuccess: 7: Successful build after gcc: 7 commits new 6dba4437f8 58: onsuccess: 7: Successful build after glibc: 2 commits new 642a87b140 59: force: 7: Successful build after gcc: 3 commits new 8889209de5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 5724cf5bd2 61: onsuccess: 4: Successful build after gcc: 5 commits new 1353e72aa0 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 30e3721045 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 2d1d369039 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new d7b68b61d4 65: onsuccess: 7: Successful build after binutils: 3 commits new d738de419a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new d898094ca2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new 1547c069b6 68: onsuccess: 7: Successful build after linux: 6 commits new 912fd64c4c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 37b5b22787 70: onsuccess: 7: Successful build after gcc: 4 commits new 0203295f2a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 02aadb216d 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 75a6ac00a4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new dff83950a7 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 6b1124bda5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 7b20421b16 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 35a44a3f07 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 633750aeeb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new f463802dde 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new b71ef982ee 80: onsuccess: 7: Successful build after linux: 44 commits new 27137ac642 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 9f9469154f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 74feb20704 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b724be04ac 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 31344fdc73 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new e2c166d34d 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 89b8261d4e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new b7aec749ac 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 1233ac4b9e 89: onsuccess: 7: Success after gcc/glibc: 8 commits new ac55105442 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 623252821d 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 633533068e 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 852d51ba71 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new acb1982c28 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new df2f40cda1 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d1a68a0974 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d9ba8c0cba 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 21393194d0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 37bda5fff6 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new b32c11dd98 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 1406b6a760 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 9a050f23ce 102: force: #1551: 1: Failure after gcc: 306 commits new c01cb9d52c 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 67ec2ceb67 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new f47d360b97 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 190f4158a6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 8d25ddef82 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new d4785a4cee 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new bfdf43eb0b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 89893892ab 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 0cde3dd95b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new f065017ae0 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new d700c4026a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new d0de182cbc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 44928007a3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 8f371d992f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 8ef3abc5e8 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 6b45abaa27 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new ebf4d60975 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 337ae95125 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 0788083ee8 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new c23dbd135e 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 67b9c78dd9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new b1321f25ca 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new db871e5c98 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 98ca2d71d0 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 671958c438 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new d530175135 128: onsuccess: #1579: 7: Success after linux: 12 commits new 84cb3f644c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 91ffd0d840 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 99e04dc2b1 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 567e5ea927 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 86c2758959 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new d86d38bade 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new d7aa2185f4 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new fec6057633 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 58b3d02c0d 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 37cd6f0d19 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 88e62445aa 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 5a2138b12e 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new a32a770e64 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 564924c90b 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 155d676b99 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 2341dbe31b 144: onsuccess: #1595: 7: Success after glibc: 2 commits new fc128d8b78 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 0f7fb94741 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 904d7c1437 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 465a495f48 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new a0e7ab4aa7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 3f202981d1 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 2842bc481f 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new 274ae7a023 152: force: #1605: 7: Success after gcc: 9 commits new c7f27ffa12 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new 004a49bcd3 154: onsuccess: #1607: 1: Success after gcc: 2 commits
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 (bebf3e43f8) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_build/master-a [...]
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 1616 -> 1668 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30224 -> 30108 bytes 05-build_abe-stage1/console.log.xz | Bin 41460 -> 41044 bytes 12-check_regression/console.log.xz | Bin 3860 -> 2584 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 26 +-- 12-check_regression/mail-subject.txt | 2 +- 12-check_regression/results.regressions | 6 - 12-check_regression/trigger-bisect | 2 - 12-check_regression/trigger-notify | 0 13-update_baseline/console.log | 66 +++--- dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- jenkins/jira-status.draft | 4 - jenkins/mail-body.draft | 342 -------------------------------- jenkins/mail-recipients.draft | 1 - jenkins/mail-subject.draft | 1 - jenkins/notify.sh | 3 - mail/jira-body.txt | 2 +- mail/mail-body.txt | 26 +-- mail/mail-subject.txt | 2 +- manifest.sh | 14 +- results | 6 - 24 files changed, 62 insertions(+), 447 deletions(-) delete mode 100644 12-check_regression/results.regressions delete mode 100644 12-check_regression/trigger-bisect delete mode 100644 12-check_regression/trigger-notify delete mode 100644 jenkins/jira-status.draft delete mode 100644 jenkins/mail-body.draft delete mode 100644 jenkins/mail-recipients.draft delete mode 100644 jenkins/mail-subject.draft delete mode 100755 jenkins/notify.sh