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 004a49bcd3 154: onsuccess: #1607: 1: Success after gcc: 2 commits discards c7f27ffa12 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] discards 274ae7a023 152: force: #1605: 7: Success after gcc: 9 commits discards 2842bc481f 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] discards 3f202981d1 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards a0e7ab4aa7 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 465a495f48 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 904d7c1437 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards 0f7fb94741 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards fc128d8b78 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 2341dbe31b 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 155d676b99 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards 564924c90b 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards a32a770e64 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 5a2138b12e 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 88e62445aa 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 37cd6f0d19 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards 58b3d02c0d 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards fec6057633 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards d7aa2185f4 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards d86d38bade 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 86c2758959 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 567e5ea927 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards 99e04dc2b1 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 91ffd0d840 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards 84cb3f644c 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards d530175135 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 671958c438 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 98ca2d71d0 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards db871e5c98 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards b1321f25ca 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards 67b9c78dd9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards c23dbd135e 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards 0788083ee8 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 337ae95125 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards ebf4d60975 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards 6b45abaa27 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 8ef3abc5e8 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 8f371d992f 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 44928007a3 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards d0de182cbc 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards d700c4026a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards f065017ae0 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 0cde3dd95b 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 89893892ab 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards bfdf43eb0b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards d4785a4cee 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards 8d25ddef82 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 190f4158a6 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards f47d360b97 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards 67ec2ceb67 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards c01cb9d52c 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 9a050f23ce 102: force: #1551: 1: Failure after gcc: 306 commits discards 1406b6a760 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards b32c11dd98 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards 37bda5fff6 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 21393194d0 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards d9ba8c0cba 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards d1a68a0974 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards df2f40cda1 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards acb1982c28 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 852d51ba71 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 633533068e 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards 623252821d 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards ac55105442 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 1233ac4b9e 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards b7aec749ac 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards 89b8261d4e 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards e2c166d34d 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 31344fdc73 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards b724be04ac 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 74feb20704 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 9f9469154f 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 27137ac642 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b71ef982ee 80: onsuccess: 7: Successful build after linux: 44 commits discards f463802dde 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 633750aeeb 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards 35a44a3f07 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7b20421b16 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 6b1124bda5 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards dff83950a7 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 75a6ac00a4 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 02aadb216d 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 0203295f2a 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 37b5b22787 70: onsuccess: 7: Successful build after gcc: 4 commits discards 912fd64c4c 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1547c069b6 68: onsuccess: 7: Successful build after linux: 6 commits discards d898094ca2 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards d738de419a 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards d7b68b61d4 65: onsuccess: 7: Successful build after binutils: 3 commits discards 2d1d369039 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 30e3721045 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 1353e72aa0 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 5724cf5bd2 61: onsuccess: 4: Successful build after gcc: 5 commits discards 8889209de5 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 642a87b140 59: force: 7: Successful build after gcc: 3 commits discards 6dba4437f8 58: onsuccess: 7: Successful build after glibc: 2 commits discards 06f3bfed4f 57: onsuccess: 7: Successful build after gcc: 7 commits discards 22157db12c 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 7242398605 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 43c056860c 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 3f02b9baeb 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 4814e8ebe9 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ba5a02ea29 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0fd3b342f1 57: onsuccess: 7: Successful build after gcc: 7 commits new 442a1a2582 58: onsuccess: 7: Successful build after glibc: 2 commits new a1e74e687b 59: force: 7: Successful build after gcc: 3 commits new f1dfcadfaf 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 93337c3b23 61: onsuccess: 4: Successful build after gcc: 5 commits new e628353ae5 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new cd6b4a97d5 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 6f90d0b914 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new a82f34d42c 65: onsuccess: 7: Successful build after binutils: 3 commits new a9fb9ee174 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new ecb5e08d68 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new d868add1aa 68: onsuccess: 7: Successful build after linux: 6 commits new b4cac72e48 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 7ba2b53333 70: onsuccess: 7: Successful build after gcc: 4 commits new f9a5fc79a9 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 8e8fe7a9e4 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 09c8cc3f2a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4ec0a85c21 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 645c9be9d9 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new becd206a21 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 1fa90b445e 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new a791f70b22 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new abfa216951 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 9814309a85 80: onsuccess: 7: Successful build after linux: 44 commits new ba5ab8179d 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1a61f1b873 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 73f0638b1c 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e5b73c19d7 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new aa89750b4f 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 1785134ed0 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new a1b1014bb0 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 095984ba77 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new 3069a60e99 89: onsuccess: 7: Success after gcc/glibc: 8 commits new 3e62c0be7f 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new 255b0ecbc9 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new 8ad5c2f49b 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new dda8c43010 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new f279e72efe 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 7749c9aedd 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 9413415a86 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new b1819ce152 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new d6085ab9ca 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 08b70d3af8 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 41c77e18b2 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 3c74b1822f 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 389c86035e 102: force: #1551: 1: Failure after gcc: 306 commits new b5ace78c40 103: onsuccess: #1552: 1: Success after gcc: 5 commits new 4b3c992906 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new a13c8f5374 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new f601cc4e34 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 322bd49e79 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new 2e8856c592 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new c2edbbd46b 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new f63a8679d5 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 5d142520f3 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new e873a9f428 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 905eab2877 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new 66ad76d031 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new b8e5479bee 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new 8d081a8a33 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 48c8d34882 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new c8a2f5365b 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new d829680131 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new fbff942e6a 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 6e42257264 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 06ab988951 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 06c577dbe4 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new b77ec36499 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 0b4b10c64d 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new 6c125fd272 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new 2d7ea5129a 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new f14aeeae85 128: onsuccess: #1579: 7: Success after linux: 12 commits new 3a1994ae56 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new fd962234d7 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new dc3d1a6be4 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new bbdc87fec4 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 87f023a39e 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new 9ef655f5c4 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new 5ecd77450f 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new c4f3b66a36 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new 2e4a6d213c 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 1f1b0bc818 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new 96609aa3e9 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 98c239a86f 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 9f8631e8a7 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 31e8a1ce4a 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new 8f28a7ca31 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 89704cab96 144: onsuccess: #1595: 7: Success after glibc: 2 commits new 82e8f8476d 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new 3d201ad9da 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new e7909c2728 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 8c0b41f628 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new bac22a60af 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new e2d8a668b4 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new fc66285472 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...] new e40bdfe0fb 152: force: #1605: 7: Success after gcc: 9 commits new 3812cd38fe 153: force: #1606: 1: Failure after basepoints/gcc-13-3004-g [...] new af6c05a11a 154: onsuccess: #1607: 1: Success after gcc: 2 commits new 423936e935 155: onsuccess: #1608: 7: Success after gcc/linux/glibc/gdb: [...]
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 (004a49bcd3) \ 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 1668 -> 1692 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 30108 -> 30208 bytes 05-build_abe-stage1/console.log.xz | Bin 41044 -> 72628 bytes 06-clean_sysroot/console.log.xz | Bin 0 -> 328 bytes 07-build_abe-linux/console.log.xz | Bin 0 -> 8548 bytes 08-build_abe-glibc/console.log.xz | Bin 0 -> 239352 bytes 09-build_abe-stage2/console.log.xz | Bin 0 -> 202836 bytes 10-build_abe-gdb/console.log.xz | Bin 0 -> 37392 bytes 11-build_abe-qemu/console.log.xz | Bin 0 -> 31872 bytes 12-check_regression/console.log.xz | Bin 2584 -> 4180 bytes 12-check_regression/mail-body.txt | 18 ++++++----- 13-update_baseline/console.log | 42 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 + git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 20 +++++++----- mail/mail-subject.txt | 2 +- manifest.sh | 36 +++++++++++++++++----- results | 12 +++++++- 24 files changed, 91 insertions(+), 52 deletions(-) create mode 100644 06-clean_sysroot/console.log.xz create mode 100644 07-build_abe-linux/console.log.xz create mode 100644 08-build_abe-glibc/console.log.xz create mode 100644 09-build_abe-stage2/console.log.xz create mode 100644 10-build_abe-gdb/console.log.xz create mode 100644 11-build_abe-qemu/console.log.xz create mode 100644 dashboard/squad/score/results-functional.json