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 ecf715a6b9 152: force: #1605: 7: Success after gcc: 9 commits discards 7d2715a2d5 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards ba83e55334 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards 1d550ee5d7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 2d73c8d584 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 7eafc6ce19 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 0f324bd7b1 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 76f40c4768 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards badd8438ac 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 4739732891 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards dcdc816217 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards 37970bb206 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 0c0a74d8b4 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards dff2e0f40a 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 6d014348b7 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards bb45bdab1b 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards d21efa685c 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards aab2a0f98f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 60f62c2568 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 173a982e88 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 8055160880 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 9ead425e96 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 1d13d39062 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 12baa81dca 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards d334768413 128: onsuccess: #1579: 7: Success after linux: 12 commits discards b002e6923e 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards b54f3e264d 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards a445c261c6 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards dd7657b641 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 75752b08cc 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 570bc7cd61 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 64c31898f4 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 050e8e1854 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards 821978ee16 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 2e7db72006 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards a65d6e1757 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 69812e5966 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 53ed9e0a46 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 10ad8e8b82 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 084317d864 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 4bcf520082 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards d83633083e 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 59612f3bd1 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards 8ec56cb2b2 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 18004e7597 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 84dbf98ba0 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 6ffc3ef12e 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 8c3bc9a513 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 7d30484615 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards 253428bee1 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 74a5396d92 102: force: #1551: 1: Failure after gcc: 306 commits discards a3213487c3 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 2771b67c4a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 816dc1c457 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards dd44c98133 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards dcf8d60475 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards ca4b96fe14 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards c6708a5d14 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 1f1bcb970c 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 0d01ba0260 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 9a9da8711d 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 1ffae52e96 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards b1af6d390e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 4edf3e6e02 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards ff7c7e62ea 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 56cff4681a 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 852dc1befd 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards ab24e77d5d 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 7ab0185e35 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 9a4a5f4d4d 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 3c9dbabc39 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards c747ae398e 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7f157f4087 80: onsuccess: 7: Successful build after linux: 44 commits discards b15521f9ea 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 5c4292e276 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards d5785b3665 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 5c9ee2bc5f 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards e383dc9892 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bfd7ebcc38 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 0abca81c3e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards beef71db7a 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards ccc02d2fd3 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards de71d56118 70: onsuccess: 7: Successful build after gcc: 4 commits discards 9f3f9d7d44 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 065cfb416b 68: onsuccess: 7: Successful build after linux: 6 commits discards a18e8e3d5e 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards da91967893 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 94f3eb6369 65: onsuccess: 7: Successful build after binutils: 3 commits discards eb777d4ac8 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards b5bb2c1b3f 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards df94b0d0e3 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards e44f03f3dd 61: onsuccess: 4: Successful build after gcc: 5 commits discards c25a3217c9 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards f41957fd70 59: force: 7: Successful build after gcc: 3 commits discards 60bc104969 58: onsuccess: 7: Successful build after glibc: 2 commits discards 8d692ad77a 57: onsuccess: 7: Successful build after gcc: 7 commits discards 3cdd5295a3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4ef90ada74 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 554e0c325b 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards c8422451f5 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 569db2fc61 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 2cbc40fd72 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new edb9ccd60c 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 1716a17134 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 364da07488 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a12191cb08 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 78f0e8095f 57: onsuccess: 7: Successful build after gcc: 7 commits new f4c4463a6e 58: onsuccess: 7: Successful build after glibc: 2 commits new 88ebebefeb 59: force: 7: Successful build after gcc: 3 commits new 975ed19c02 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 8ab93d104f 61: onsuccess: 4: Successful build after gcc: 5 commits new 2938c17491 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new fbb40b14c1 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new f3af2a8704 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 286d825e8e 65: onsuccess: 7: Successful build after binutils: 3 commits new 0d8b3f0c2a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new a338fd9989 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new fe4170ff5e 68: onsuccess: 7: Successful build after linux: 6 commits new ae101f2e4f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0888c92317 70: onsuccess: 7: Successful build after gcc: 4 commits new aabe12511b 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8d775714bf 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 90de574951 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7854fd4fa8 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 192d492bdc 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 49ab0f27e6 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new f884ea7077 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c24eaa66d7 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new d32b0ba3a5 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 01090beebb 80: onsuccess: 7: Successful build after linux: 44 commits new 0fa15d499c 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6bc49fe127 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 89706d6337 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 77ecba4f11 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new e4f6822e54 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 59f8d73f28 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new a19d6b1da7 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 5dfb6931d7 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new dd97a1a3a3 89: onsuccess: 7: Success after gcc/glibc: 8 commits new ef7c6a9f3b 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 62ac08ab31 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new a43950e381 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 1fa6474632 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 2928b76cbb 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 1768a183e4 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 7463a4c5d9 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 74a00630db 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new 2e5c857f38 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new f32f52e1a9 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new fb245099e0 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new f77e74136d 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 2831dda4c1 102: force: #1551: 1: Failure after gcc: 306 commits new 80321aeea7 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e830529b3b 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new 2d0aa2f079 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 4b3d075fb8 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 5a1a901e9f 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 1b87aff227 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 0728d175ba 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 2f8422c500 110: onsuccess: #1559: 7: Success after gcc: 4 commits new c90e087657 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new b1369d2cee 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new df66d0b2e7 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new a31debcfec 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 951e967c94 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 90696fe10d 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new c711fefa1a 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 87dc270594 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new 87b299e94d 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 80dc671134 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 48caf50364 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 2deaa7835b 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 94609b40e2 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 060ef40ad8 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new aa5267ab95 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 3336ba57a3 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new bbe18347d2 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new 0cfebf62d6 128: onsuccess: #1579: 7: Success after linux: 12 commits new 085d52e234 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new 5c98ad1f96 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 4e01175e2b 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 50d5aea325 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new e9e5acfad3 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 5bcf600492 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 3278a84788 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new 4203bcf32b 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 1e28f70a90 137: onsuccess: #1588: 7: Success after gcc: 5 commits new ce013099e6 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new af5d47d89c 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 7e0f7b0b44 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 80a381a38f 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new b274c637b4 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new cf9a6a0507 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new adc3de6f64 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 0a1d4f7471 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 67814c8298 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 2e8581914e 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 50f369be5d 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new 7663cac513 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new c775b6f7a7 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new 007d0453e7 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new df3e0d3cd1 152: force: #1605: 7: Success after gcc: 9 commits new bebf3e43f8 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...]
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 (ecf715a6b9) \ 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 1636 -> 1616 bytes 02-prepare_abe/console.log.xz | Bin 2736 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30236 -> 30224 bytes 05-build_abe-stage1/console.log.xz | Bin 72220 -> 41460 bytes 06-clean_sysroot/console.log.xz | Bin 328 -> 0 bytes 07-build_abe-linux/console.log.xz | Bin 8748 -> 0 bytes 08-build_abe-glibc/console.log.xz | Bin 239556 -> 0 bytes 09-build_abe-stage2/console.log.xz | Bin 202600 -> 0 bytes 10-build_abe-gdb/console.log.xz | Bin 37664 -> 0 bytes 11-build_abe-qemu/console.log.xz | Bin 32424 -> 0 bytes 12-check_regression/console.log.xz | Bin 3116 -> 3860 bytes 12-check_regression/jira-body.txt | 2 +- 12-check_regression/mail-body.txt | 20 +- 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 | 64 ++--- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 - 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 | 20 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +-- results | 18 +- 31 files changed, 427 insertions(+), 96 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-stage2/console.log.xz delete mode 100644 10-build_abe-gdb/console.log.xz delete mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 12-check_regression/results.regressions create mode 100644 12-check_regression/trigger-bisect create mode 100644 12-check_regression/trigger-notify delete mode 100644 dashboard/squad/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