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 e19dc3d295 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] discards b4a9416e62 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] discards 76123cfe37 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] discards 5c28a506e6 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] discards aad7879eb3 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] discards 9c3f5c6c46 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] discards 9ff41cbf60 144: onsuccess: #1595: 7: Success after glibc: 2 commits discards 6b914a2ac4 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] discards c0491206dc 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] discards dbfd26ee42 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits discards 504d71d5df 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits discards 46f0eba61d 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] discards 4115fadad1 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] discards e04a6fe2a0 137: onsuccess: #1588: 7: Success after gcc: 5 commits discards c4ecc7d5a3 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] discards 729a91c88b 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] discards 6ec201adbb 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] discards 78f8fcaa9a 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] discards 2a15581337 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] discards fb5865ce69 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] discards 875a917acb 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits discards f4175f2140 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] discards 93623b2000 128: onsuccess: #1579: 7: Success after linux: 12 commits discards 9eb5dd02b9 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits discards 31eda81b71 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits discards 6cf0b5a4aa 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits discards 750c588471 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits discards eb77b36443 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] discards 42b6482aa3 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] discards aa8c73a2ab 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] discards 6f275adfd2 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] discards f1f3493ee2 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] discards b935c1eb89 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits discards 90e8cebb1b 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] discards 66ee97dee1 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] discards 4d0a802fe0 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] discards 4eaa9f63c4 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] discards 7a1434469a 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] discards 4f25974fc3 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] discards 34abed9c36 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] discards 4a29ea1fe5 110: onsuccess: #1559: 7: Success after gcc: 4 commits discards abd2fe3b78 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits discards 4338f78beb 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] discards c220db1c74 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] discards 087c145baf 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] discards 6626fd9ab5 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] discards fe1872db29 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] discards e10ad07e67 103: onsuccess: #1552: 1: Success after gcc: 5 commits discards 6eb14d96f2 102: force: #1551: 1: Failure after gcc: 306 commits discards a7b484a5e3 101: onsuccess: #1547: 7: Success after binutils: 82 commits discards 2ed851d00b 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] discards cfa4ed2f1e 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits discards 9d53b1f4c5 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] discards 58f75eaf48 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits discards 9b9c8c488f 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 47215ee23c 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 175392d033 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits discards 66a66dd7b1 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 55c7430a45 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits discards e1527ec993 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits discards 10faab4f4e 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits discards 1188a5032f 89: onsuccess: 7: Success after gcc/glibc: 8 commits discards 25c9b14dd5 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits discards f0463e5422 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits discards 316bde4182 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits discards 72050842db 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 5288c73379 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 86abc121ca 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards da58c21c6a 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 4db26b6cac 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 759e63b4f4 80: onsuccess: 7: Successful build after linux: 44 commits discards 8f28027165 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 6f4cd10498 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] discards ebb7d1d870 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8be3a73027 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards 69d1fbeaeb 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards e5cf0f6be3 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 597d6e267f 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cca67bfb27 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards b0fe21063d 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 52273cdc86 70: onsuccess: 7: Successful build after gcc: 4 commits discards a85864339f 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 891348c50a 68: onsuccess: 7: Successful build after linux: 6 commits discards 56310234dc 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] discards a35f01138e 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] discards 2138e19228 65: onsuccess: 7: Successful build after binutils: 3 commits discards f3cef8d6ab 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 1fc5772a04 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 37abe245d4 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 6492a3a9b9 61: onsuccess: 4: Successful build after gcc: 5 commits discards 5a32f5167e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards d3b0621f15 59: force: 7: Successful build after gcc: 3 commits discards 7aa5a5cf2d 58: onsuccess: 7: Successful build after glibc: 2 commits discards 17c279db1e 57: onsuccess: 7: Successful build after gcc: 7 commits discards 2278b88f0f 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e3bc225115 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 824ce943c3 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits discards b21ae178c0 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards a79b17200a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] discards 123b90c766 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 39bba0e279 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ef7bee3575 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 226302a3bf 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 9ec1c43462 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 4 [...] new 0e7c8b5f5b 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 90fdb66513 54: onsuccess: 7: Successful build after gcc/glibc: 7 commits new 98a20171fd 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c5d3576f53 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 55a246c6e7 57: onsuccess: 7: Successful build after gcc: 7 commits new 5f40222e1e 58: onsuccess: 7: Successful build after glibc: 2 commits new 88db660b26 59: force: 7: Successful build after gcc: 3 commits new a57cb323d0 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 83f10cdfb0 61: onsuccess: 4: Successful build after gcc: 5 commits new b828b3452d 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 0b78cd01eb 63: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new a1abc5f1e5 64: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new 27686d6861 65: onsuccess: 7: Successful build after binutils: 3 commits new 9fbf25df55 66: onsuccess: 7: Successful build after gcc: libstdc++: Som [...] new 1fe834cd6b 67: onsuccess: 7: Successful build after glibc: Revert "Dete [...] new d55010b20a 68: onsuccess: 7: Successful build after linux: 6 commits new 5ce5d5a068 69: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 58de55f17a 70: onsuccess: 7: Successful build after gcc: 4 commits new 76701ca976 71: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new a149c01a47 72: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new bd67ad851e 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 6a0955eb8c 74: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new f74a2b6ef8 75: onsuccess: 7: Successful build after gcc: Require fgraph [...] new e28e6d3109 76: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 7b759549e3 77: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 5638125268 78: onsuccess: 7: Successful build after gcc: rs6000: Allow [...] new 7b19e7100c 79: onsuccess: 7: Successful build after binutils/gdb: 2 commits new d33cf4142f 80: onsuccess: 7: Successful build after linux: 44 commits new c2caad1508 81: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 55a30c519c 82: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 145d5508d0 83: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d7254bb482 84: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 7b30354374 85: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new bc6195a315 86: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 20 commits new 232058de5a 87: onsuccess: 7: Success after binutils/gcc/linux/gdb: 68 commits new 1f6b059bbe 88: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 43 commits new e2869a20ae 89: onsuccess: 7: Success after gcc/glibc: 8 commits new b24e5cc3b5 90: onsuccess: 7: Success after binutils/gcc/gdb: 12 commits new ba3bcd10b7 91: onsuccess: 7: Success after binutils/gcc/linux/gdb: 88 commits new b9d83ed9f0 92: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 74 commits new 2615b2c521 93: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 30897d3979 94: onsuccess: 7: Success after binutils/gcc/gdb: 15 commits new 8cca2314e3 95: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new d3fa9867f8 96: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a4184703ef 97: onsuccess: #1491: 7: Success after gcc/linux: 32 commits new ef6ecaf861 98: onsuccess: #1492: 7: Success after binutils/gcc/linux/gd [...] new 330ceda1fd 99: onsuccess: #1493: 7: Success after gcc/linux: 11 commits new 6ed84ffc2a 100: onsuccess: #1496: 7: Success after binutils/gcc/linux/g [...] new 8d0fa414ca 101: onsuccess: #1547: 7: Success after binutils: 82 commits new 02230fdd00 102: force: #1551: 1: Failure after gcc: 306 commits new 6aa5d3bebf 103: onsuccess: #1552: 1: Success after gcc: 5 commits new e65f9f8ff1 104: onsuccess: #1553: 7: Success after binutils/gcc/linux/g [...] new af7331b397 105: onsuccess: #1554: 7: Success after v6.0-rc5-97-g38eddee [...] new 75f4a6566b 106: onsuccess: #1555: 7: Success after binutils/gcc/linux/g [...] new 2e1b3d21f2 107: onsuccess: #1556: 7: Success after binutils/gcc/glibc/g [...] new b07f0518d7 108: onsuccess: #1557: 7: Success after basepoints/gcc-13-27 [...] new 64927a7fca 109: onsuccess: #1558: 7: Success after binutils/gcc/gdb: 5 commits new 9df72ebac7 110: onsuccess: #1559: 7: Success after gcc: 4 commits new 8cad3c3879 111: onsuccess: #1560: 7: Success after binutils/gcc/glibc/g [...] new 42dfeddcce 112: onsuccess: #1561: 7: Success after binutils/gcc/linux/g [...] new 8213365e01 113: onsuccess: #1562: 7: Success after binutils/gcc/glibc/g [...] new ba88e8714e 114: onsuccess: #1563: 7: Success after binutils/glibc/gdb: [...] new 8dd3f38022 115: onsuccess: #1564: 7: Success after binutils/gcc/gdb: 16 [...] new c90af8913e 116: onsuccess: #1565: 7: Success after binutils/gcc/linux/g [...] new 9db61768b4 117: onsuccess: #1566: 7: Success after binutils/gcc/gdb/qem [...] new 5fd789224c 118: onsuccess: #1567: 7: Success after binutils/gcc/gdb: 4 commits new d732be2b5f 119: onsuccess: #1568: 7: Success after binutils/gcc/glibc/g [...] new 84a06927bd 120: onsuccess: #1569: 7: Success after binutils/gcc/linux/g [...] new 583b0c649c 121: onsuccess: #1572: 7: Success after binutils/gcc/linux/g [...] new 9698537d32 122: onsuccess: #1573: 7: Success after binutils/gcc/linux/g [...] new 6288e2cce9 123: onsuccess: #1574: 7: Success after binutils/gcc/linux/g [...] new 3d4ce51975 124: onsuccess: #1575: 7: Success after binutils/gdb: 6 commits new 9abd141a06 125: onsuccess: #1576: 7: Success after binutils/gcc/gdb: 4 commits new ae644e93f6 126: onsuccess: #1577: 7: Success after gcc/linux: 24 commits new dba3e196c0 127: onsuccess: #1578: 7: Success after binutils/gcc/gdb: 3 commits new b2271cbace 128: onsuccess: #1579: 7: Success after linux: 12 commits new 54410d9cb6 129: onsuccess: #1580: 7: Success after basepoints/gcc-13-28 [...] new dffb6f758d 130: onsuccess: #1581: 7: Success after gcc/linux: 32 commits new 88665a430d 131: onsuccess: #1582: 7: Success after binutils/gcc/linux/g [...] new 979ab643bf 132: onsuccess: #1583: 7: Success after binutils/gcc/gdb: 10 [...] new 5017c91b22 133: onsuccess: #1584: 7: Success after binutils/gcc/gdb: 26 [...] new d2f21714ab 134: onsuccess: #1585: 7: Success after binutils/gcc/glibc/g [...] new ba0ee51b89 135: onsuccess: #1586: 7: Success after binutils/gcc/linux/g [...] new b95956b86e 136: onsuccess: #1587: 7: Success after binutils/gcc/gdb: 13 [...] new beb610b2e4 137: onsuccess: #1588: 7: Success after gcc: 5 commits new 5fbffd9dbe 138: onsuccess: #1589: 7: Success after binutils/gcc/linux/g [...] new d91cc228e5 139: onsuccess: #1590: 7: Success after binutils/gcc/linux/g [...] new 849f5388bc 140: onsuccess: #1591: 7: Success after binutils/gcc/gdb: 3 commits new 7009a7a28b 141: onsuccess: #1592: 7: Success after binutils/gcc/gdb: 9 commits new 9aa86bae33 142: onsuccess: #1593: 7: Success after binutils/gcc/glibc/g [...] new a7b005c9b0 143: onsuccess: #1594: 7: Success after binutils/gcc/linux/g [...] new 0154ea4689 144: onsuccess: #1595: 7: Success after glibc: 2 commits new d77060e6c4 145: onsuccess: #1596: 7: Success after binutils/gcc/gdb: 32 [...] new a5ad82a442 146: onsuccess: #1597: 7: Success after binutils/gcc/linux/g [...] new 8909ac7b91 147: onsuccess: #1598: 7: Success after binutils/gcc/linux/g [...] new 41a39edda3 148: onsuccess: #1599: 7: Success after binutils/gcc/glibc/g [...] new e28184ae51 149: onsuccess: #1600: 7: Success after binutils/gcc/gdb: 22 [...] new 692a41d4ab 150: onsuccess: #1601: 7: Success after binutils/gcc/linux/g [...] new ee68299923 151: onsuccess: #1603: 7: Success after gdb-12-branchpoint-2 [...]

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 (e19dc3d295) \ 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 1672 -> 1688 bytes 02-prepare_abe/console.log.xz | Bin 2748 -> 2708 bytes 04-build_abe-binutils/console.log.xz | Bin 30388 -> 30176 bytes 05-build_abe-stage1/console.log.xz | Bin 72780 -> 72928 bytes 07-build_abe-linux/console.log.xz | Bin 8656 -> 8780 bytes 08-build_abe-glibc/console.log.xz | Bin 239916 -> 239704 bytes 09-build_abe-stage2/console.log.xz | Bin 203196 -> 203112 bytes 10-build_abe-gdb/console.log.xz | Bin 37712 -> 37692 bytes 11-build_abe-qemu/console.log.xz | Bin 32012 -> 32092 bytes 12-check_regression/console.log.xz | Bin 4492 -> 2964 bytes 13-update_baseline/console.log | 62 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 29 +++++++--------- 17 files changed, 48 insertions(+), 53 deletions(-)