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-arm in repository toolchain/ci/base-artifacts.

discards 0bde070e44 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 839c93c2f8 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 1646cbe3a7 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards ab6dba211e 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards 8783b7f77a 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 690779ce48 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards 74d9534d7b 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards b74a248cc9 132: onsuccess: #1645: 7: Success after linux: 23 commits discards c81172014d 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards 6412b33c86 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards 0a7ca91820 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards b5287473ca 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 62bd2ebf5a 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards b49ea9488a 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards be41f4f1d0 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 57eec21e5e 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 94c6798513 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards db9bf539b7 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 83be75f892 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards 4118304303 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 6dd0357d84 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 82f481d000 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards d7aeb6c46a 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards e3d8bc535d 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 57a116ad9e 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards d72c427c28 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards 1ed4ac3f18 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 97d618463b 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 9bf1f57308 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 1799c13146 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards 441e4e925f 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards b8f06c5c2f 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards b747bde666 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards 70ab2a6318 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards fca8875921 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards 7d710628e0 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards 6edd9d394b 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 97a3b1d2bb 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards a1562428af 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 628f846296 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 66fc620153 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 4414991846 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards 3ecc604aef 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards 0b064b616d 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards 8ba3b29cfd 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 63ddaa2a8b 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 4160f69ca5 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards b60cc96ef2 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards 29f7074486 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 69d766d463 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 189c37a709 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards f84d79ce0f 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 4a48f33765 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 4398d84d30 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 4e21ff23bc 85: onsuccess: 7: Success after gcc: 9 commits discards f45ca93657 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards 517c57b7e3 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 27947495fc 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 8990d7560b 81: onsuccess: 7: Successful build after gcc: 2 commits discards 2585f17396 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 8704dd3d23 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5c5bb7a8b8 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f6ec9306df 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 5d82a60abc 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 740401e888 75: onsuccess: 7: Successful build after linux: 44 commits discards 07a3e7bcbb 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 18eb379e39 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 108adf5730 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards baecfc7449 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards bf9acf5fe0 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards 02685e82f2 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 009bc6494c 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 62644db99f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c18d254193 66: onsuccess: 7: Successful build after gcc: 3 commits discards b9509c3b14 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 172c1663de 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 443ae173c1 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 580e6aa8e2 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 931fb8a2ca 61: onsuccess: 4: Successful build after gcc: 15 commits discards 5bff65994e 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 034780e14e 59: force: 7: Successful build after gcc: 2 commits discards cfcd36e400 58: onsuccess: 7: Successful build after glibc: 2 commits discards d18f2b999a 57: onsuccess: 7: Successful build after gcc: 7 commits discards a90e20aca3 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards d1563542cc 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 36d3829112 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 444319a0a5 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards 4156b052a4 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards dbf4a3fc1b 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 26ef69da22 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 560d496fd4 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards e1687f7664 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards 4f05c258d6 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f12c821c63 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 5ab5033ae2 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a23ed9b52d 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards e76923cf20 43: onsuccess: 7: Successful build after gcc: 2 commits discards a57bf52576 42: onsuccess: 7: Successful build after baseline build: no [...] discards 398c67a87e 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 91ede2fcd5 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards e91f05ace1 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 046c6534dc 39: onsuccess: 7: Successful build after binutils/gcc/gdb: 6 [...] new 96ba49ddab 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ae8310c2b7 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 02e02833e4 42: onsuccess: 7: Successful build after baseline build: no [...] new 5c56634688 43: onsuccess: 7: Successful build after gcc: 2 commits new bedb117833 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 8d75262a1c 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new cde32dbda1 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new f1c9bd1302 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 00262971c3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new a9e6bde0dd 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 2ea5ed4916 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d0bc5d5a44 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fdb1c7149a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 4c5c3208b2 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 23d4f01aef 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new 188fb049ae 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c40ab83bc5 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 42d632568b 57: onsuccess: 7: Successful build after gcc: 7 commits new 5b9434b299 58: onsuccess: 7: Successful build after glibc: 2 commits new 6135651b36 59: force: 7: Successful build after gcc: 2 commits new 590b7e1c13 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new 50db4066a0 61: onsuccess: 4: Successful build after gcc: 15 commits new 5a7b9364e6 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new 4a55f956f7 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new dc50eac6c8 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d525677f55 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new c12bb58dd8 66: onsuccess: 7: Successful build after gcc: 3 commits new f2e7c4c43c 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 5102df2ec4 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new ad2ea8fc9e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 29208c5849 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new ef07eba027 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 1e77f42c82 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 2e3a113bdd 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new b2c89234da 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new dc2bdf7db8 75: onsuccess: 7: Successful build after linux: 44 commits new 88c2396873 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8d2744eed2 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new adf88da519 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 1e4c88b923 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new b8ae366ba6 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 68c64d1fdb 81: onsuccess: 7: Successful build after gcc: 2 commits new 830f71533b 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new b624c03b8d 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new c9935adb61 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new 36d93f5f6a 85: onsuccess: 7: Success after gcc: 9 commits new 6d21142870 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 4ff9b26d9d 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new 83ac8214ca 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 7c027da035 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new 845ad36734 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new a68d7f427c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 18efd4b155 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new 84c022b698 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 4bed0d22bf 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new eb22b3f9ba 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new dfe3ac07d4 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new d4005490a0 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 1a210ca562 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 0d75edc635 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 47a153d29c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new a79ae7fbb0 101: onsuccess: #1609: 7: Success after binutils: 78 commits new 0dd48fe8a2 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new ccdb625e69 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new aaa167f95c 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new e2b03f2a01 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new e30d1cf769 106: onsuccess: #1617: 7: Success after gcc: 2 commits new dd757de616 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 1e564c4cb7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new ab4e5dffb1 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new 3f5d64eed6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 07fc49c8fe 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 2e707a326d 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new cd7949109d 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 2d14e109d6 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 1cd01a32b6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new 01399faddf 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new c7f2f1494c 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 6c691df7da 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new 2e3bb9ab0c 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new d56e1b8b3d 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new 12d78a27e5 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new fb538af957 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 5d14200cd3 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 14a10e7d47 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new 9445c115e9 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new fc77aa5178 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new 1f1431b8c2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new db8d964812 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new a6036c4a70 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new d2f9a24294 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new e98bfea7ed 131: onsuccess: #1644: 7: Success after gcc: 10 commits new 5a93396530 132: onsuccess: #1645: 7: Success after linux: 23 commits new bbff660b8e 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 009e3eb44e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new b71e32b2ab 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 6c7e509b14 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 0c6f9c2208 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 95a99b04d1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new 426f654575 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 379f9d699b 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/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 (0bde070e44) \ 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 1684 -> 1664 bytes 02-prepare_abe/console.log.xz | Bin 2744 -> 2752 bytes 04-build_abe-binutils/console.log.xz | Bin 30324 -> 30460 bytes 05-build_abe-stage1/console.log.xz | Bin 60336 -> 91576 bytes 06-clean_sysroot/console.log.xz | Bin 0 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 0 -> 8704 bytes 08-build_abe-glibc/console.log.xz | Bin 0 -> 233548 bytes 09-build_abe-stage2/console.log.xz | Bin 0 -> 226796 bytes 10-build_abe-gdb/console.log.xz | Bin 0 -> 38124 bytes 11-build_abe-qemu/console.log.xz | Bin 0 -> 32188 bytes 12-check_regression/console.log.xz | Bin 2904 -> 5092 bytes 12-check_regression/mail-body.txt | 20 ++++---- 13-update_baseline/console.log | 66 +++++++++++++------------- dashboard/dashboard-generate.sh | 2 +- dashboard/squad/score/results-functional.json | 1 + git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 22 +++++---- mail/mail-subject.txt | 2 +- manifest.sh | 38 +++++++++++---- results | 12 ++++- 26 files changed, 106 insertions(+), 71 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