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 379f9d699b 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] discards 426f654575 139: onsuccess: #1654: 1: Success after gcc: 11 commits discards 95a99b04d1 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] discards 0c6f9c2208 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] discards 6c7e509b14 136: onsuccess: #1650: 7: Success after binutils: 2 commits discards b71e32b2ab 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] discards 009e3eb44e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] discards bbff660b8e 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] discards 5a93396530 132: onsuccess: #1645: 7: Success after linux: 23 commits discards e98bfea7ed 131: onsuccess: #1644: 7: Success after gcc: 10 commits discards d2f9a24294 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] discards a6036c4a70 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits discards db8d964812 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits discards 1f1431b8c2 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits discards fc77aa5178 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] discards 9445c115e9 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] discards 14a10e7d47 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] discards 5d14200cd3 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] discards fb538af957 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] discards 12d78a27e5 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] discards d56e1b8b3d 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] discards 2e3bb9ab0c 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] discards 6c691df7da 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] discards c7f2f1494c 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] discards 01399faddf 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] discards 1cd01a32b6 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] discards 2d14e109d6 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] discards cd7949109d 113: onsuccess: #1624: 7: Success after gcc: 6 commits discards 2e707a326d 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits discards 07fc49c8fe 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits discards 3f5d64eed6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] discards ab4e5dffb1 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] discards 1e564c4cb7 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] discards dd757de616 107: onsuccess: #1618: 7: Success after gcc: 2 commits discards e30d1cf769 106: onsuccess: #1617: 7: Success after gcc: 2 commits discards e2b03f2a01 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] discards aaa167f95c 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits discards ccdb625e69 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] discards 0dd48fe8a2 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] discards a79ae7fbb0 101: onsuccess: #1609: 7: Success after binutils: 78 commits discards 47a153d29c 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] discards 0d75edc635 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] discards 1a210ca562 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits discards d4005490a0 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] discards dfe3ac07d4 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] discards eb22b3f9ba 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] discards 4bed0d22bf 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits discards 84c022b698 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] discards 18efd4b155 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits discards a68d7f427c 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 845ad36734 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] discards 7c027da035 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits discards 83ac8214ca 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits discards 4ff9b26d9d 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits discards 6d21142870 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits discards 36d93f5f6a 85: onsuccess: 7: Success after gcc: 9 commits discards c9935adb61 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] discards b624c03b8d 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits discards 830f71533b 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits discards 68c64d1fdb 81: onsuccess: 7: Successful build after gcc: 2 commits discards b8ae366ba6 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] discards 1e4c88b923 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards adf88da519 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 8d2744eed2 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] discards 88c2396873 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards dc2bdf7db8 75: onsuccess: 7: Successful build after linux: 44 commits discards b2c89234da 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits discards 2e3a113bdd 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 1e77f42c82 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] discards ef07eba027 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] discards 29208c5849 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards ad2ea8fc9e 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 5102df2ec4 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards f2e7c4c43c 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards c12bb58dd8 66: onsuccess: 7: Successful build after gcc: 3 commits discards d525677f55 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards dc50eac6c8 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 4a55f956f7 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] discards 5a7b9364e6 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] discards 50db4066a0 61: onsuccess: 4: Successful build after gcc: 15 commits discards 590b7e1c13 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] discards 6135651b36 59: force: 7: Successful build after gcc: 2 commits discards 5b9434b299 58: onsuccess: 7: Successful build after glibc: 2 commits discards 42d632568b 57: onsuccess: 7: Successful build after gcc: 7 commits discards c40ab83bc5 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 188fb049ae 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 23d4f01aef 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits discards 4c5c3208b2 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] discards fdb1c7149a 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] discards d0bc5d5a44 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 2ea5ed4916 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards a9e6bde0dd 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] discards 00262971c3 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] discards f1c9bd1302 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards cde32dbda1 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] discards 8d75262a1c 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards bedb117833 44: onsuccess: 7: Successful build after gcc/linux: 35 commits discards 5c56634688 43: onsuccess: 7: Successful build after gcc: 2 commits discards 02e02833e4 42: onsuccess: 7: Successful build after baseline build: no [...] discards ae8310c2b7 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] discards 96ba49ddab 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 58780c226e 40: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 99c780c083 41: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4d41e38f20 42: onsuccess: 7: Successful build after baseline build: no [...] new c5310d61ab 43: onsuccess: 7: Successful build after gcc: 2 commits new 1a587c95d6 44: onsuccess: 7: Successful build after gcc/linux: 35 commits new 2dba032257 45: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8536baa9ca 46: onsuccess: 7: Successful build after binutils/linux/gdb: [...] new fef4244e0d 47: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d3a772b465 48: onsuccess: 7: Successful build after binutils/gcc/gdb: 5 [...] new a1901b7dff 49: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fa7fcc8d4d 50: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 3a02f0e33c 51: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new fab6a8d01b 52: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new c0b381d74d 53: onsuccess: 7: Successful build after binutils/gcc/gdb: 1 [...] new 34d841de94 54: onsuccess: 7: Successful build after gcc/glibc/qemu: 9 commits new e5baea65a9 55: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 0087e0c6b4 56: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 38afa28f51 57: onsuccess: 7: Successful build after gcc: 7 commits new 9ecf03ada8 58: onsuccess: 7: Successful build after glibc: 2 commits new 99b4bffc77 59: force: 7: Successful build after gcc: 2 commits new 37fbd50a40 60: force: 4: Regression after gcc: libstdc++: Optimize oper [...] new eadc20dd9f 61: onsuccess: 4: Successful build after gcc: 15 commits new 2dbbf2d209 62: onsuccess: 7: Successful build after binutils/gcc/gdb/qe [...] new b44c00886a 63: onsuccess: 7: Successful build after binutils/gcc/gdb: 2 [...] new d817d09d68 64: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 8e8b256c14 65: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new d095cbe5d5 66: onsuccess: 7: Successful build after gcc: 3 commits new 5aa91ff37f 67: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 032fd1f9f5 68: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 4df26c8787 69: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1e28877c82 70: onsuccess: 7: Successful build after binutils/gcc/gdb: 3 [...] new 66ee93f2eb 71: onsuccess: 7: Successful build after gcc: Require fgraph [...] new 35f2ff5b98 72: onsuccess: 7: Successful build after gcc/linux/glibc: 15 [...] new 54a4ff351a 73: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new e247f2f907 74: onsuccess: 7: Successful build after binutils/gdb: 2 commits new 63d1d003fa 75: onsuccess: 7: Successful build after linux: 44 commits new 8a8bb47677 76: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new 630f31e2ac 77: onsuccess: 7: Successful build after gcc/linux/glibc: 21 [...] new 7b8c479ef4 78: onsuccess: 7: Successful build after binutils/gcc/linux/ [...] new f6759a974a 79: onsuccess: 7: Successful build after binutils/gcc/glibc/ [...] new 1183f26bea 80: onsuccess: 7: Successful build after binutils/gcc/gdb: 8 [...] new 79e0e78291 81: onsuccess: 7: Successful build after gcc: 2 commits new 80de8e5fa0 82: onsuccess: 7: Success after binutils/gcc/glibc/gdb: 19 commits new 7c19fab4f1 83: onsuccess: 7: Success after binutils/gcc/linux/gdb: 69 commits new 11f0329294 84: onsuccess: 7: Success after binutils/gcc/glibc/gdb/qemu: [...] new fd24c3abd2 85: onsuccess: 7: Success after gcc: 9 commits new e35530bdfe 86: onsuccess: 7: Success after binutils/gcc/linux/gdb: 99 commits new 7f2dffa19e 87: onsuccess: 7: Success after binutils/gcc/gdb/qemu: 73 commits new af7243cfda 88: onsuccess: 7: Success after binutils/gcc/gdb: 9 commits new 896cc38b4a 89: onsuccess: 7: Success after binutils/gcc/gdb: 18 commits new f01ec1814b 90: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 1594c533f6 91: onsuccess: 7: Success after binutils/gcc/linux/gdb/qemu: [...] new 353a440752 92: onsuccess: #1526: 7: Success after gcc/linux: 33 commits new a7cdff594e 93: onsuccess: #1527: 7: Success after binutils/gcc/linux/gd [...] new 128d9224d3 94: onsuccess: #1528: 7: Success after gcc/linux: 11 commits new 5653f4b323 95: onsuccess: #1529: 7: Success after baseline build: no ne [...] new 38220cdf2e 96: onsuccess: #1532: 7: Success after binutils/gcc/linux/gd [...] new 8522e6e13f 97: onsuccess: #1533: 7: Success after binutils/gcc/glibc/gd [...] new 47b0daf038 98: onsuccess: #1534: 7: Success after gcc/glibc: 14 commits new 95163ecfb7 99: onsuccess: #1535: 7: Success after binutils/gcc/linux/gd [...] new 68319945cb 100: onsuccess: #1536: 7: Success after binutils/gcc/glibc/g [...] new c628368d32 101: onsuccess: #1609: 7: Success after binutils: 78 commits new be76d40592 102: onsuccess: #1613: 7: Success after binutils/gcc/linux/g [...] new 5769432af4 103: onsuccess: #1614: 7: Success after basepoints/gcc-13-27 [...] new 31233b5de0 104: onsuccess: #1615: 7: Success after gcc/glibc: 2 commits new 57d18b30c1 105: onsuccess: #1616: 7: Success after binutils/gcc/glibc/g [...] new 3709c923f5 106: onsuccess: #1617: 7: Success after gcc: 2 commits new c94fd7a6d3 107: onsuccess: #1618: 7: Success after gcc: 2 commits new 0a58f33dcb 108: onsuccess: #1619: 7: Success after v6.0-rc5-97-g38eddee [...] new 4fdedab7ce 109: onsuccess: #1620: 7: Success after binutils/gcc/linux/g [...] new b7b0d791a6 110: onsuccess: #1621: 7: Success after binutils/gcc/glibc/g [...] new 34d77306d4 111: onsuccess: #1622: 7: Success after binutils/gcc/gdb: 3 commits new 246c608a57 112: onsuccess: #1623: 7: Success after binutils/gcc/gdb: 3 commits new b04f710a03 113: onsuccess: #1624: 7: Success after gcc: 6 commits new 1d667e3479 114: onsuccess: #1625: 7: Success after binutils/gcc/glibc/g [...] new 0cc871bf44 115: onsuccess: #1626: 7: Success after binutils/gcc/linux/g [...] new b3a6a72dc6 116: onsuccess: #1627: 7: Success after binutils/gcc/glibc/g [...] new cf64e1ed15 117: onsuccess: #1628: 7: Success after binutils/glibc/gdb: [...] new 5faa936a8b 118: onsuccess: #1629: 7: Success after binutils/gcc/gdb: 16 [...] new c0e330499f 119: onsuccess: #1630: 7: Success after binutils/gcc/linux/g [...] new 7f0ece8047 120: onsuccess: #1631: 7: Success after binutils/gcc/gdb/qem [...] new b07148f2ba 121: onsuccess: #1632: 7: Success after binutils/gcc/gdb: 13 [...] new ca60ebfcd0 122: onsuccess: #1633: 7: Success after binutils/gcc/glibc/g [...] new 1aeb8009bf 123: onsuccess: #1634: 7: Success after binutils/gcc/linux/g [...] new 518549ead4 124: onsuccess: #1637: 7: Success after binutils/gcc/linux/g [...] new e19bc376e5 125: onsuccess: #1638: 7: Success after binutils/gcc/linux/g [...] new 0c2449ccab 126: onsuccess: #1639: 7: Success after binutils/gcc/linux/g [...] new cb8b415454 127: onsuccess: #1640: 7: Success after binutils/gdb: 6 commits new e2bab43529 128: onsuccess: #1641: 7: Success after binutils/gcc/gdb: 4 commits new 8b4d4297c2 129: onsuccess: #1642: 7: Success after gcc/linux: 24 commits new 75e005ea8e 130: onsuccess: #1643: 7: Success after binutils/gcc/linux/g [...] new 724f0118b9 131: onsuccess: #1644: 7: Success after gcc: 10 commits new e7484051d5 132: onsuccess: #1645: 7: Success after linux: 23 commits new 6e4ef2ab96 133: onsuccess: #1646: 7: Success after binutils/gcc/linux/g [...] new 02b275204e 134: onsuccess: #1647: 7: Success after binutils/gcc/gdb: 10 [...] new c4184b5bc5 135: onsuccess: #1648: 7: Success after binutils/gcc/gdb: 27 [...] new 2f0e875a18 136: onsuccess: #1650: 7: Success after binutils: 2 commits new 4a19390a68 137: force: #1652: 7: Success after basepoints/gcc-13-2870-g [...] new 13f829485e 138: force: #1653: 1: Failure after basepoints/gcc-13-2871-g [...] new c9e723a273 139: onsuccess: #1654: 1: Success after gcc: 11 commits new 2f27c0ad99 140: onsuccess: #1655: 7: Success after binutils/gcc/linux/g [...] new 0f381619e6 141: onsuccess: #1656: 7: Success after gcc: 7 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 (379f9d699b) \ 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 1664 -> 1708 bytes 02-prepare_abe/console.log.xz | Bin 2752 -> 2748 bytes 04-build_abe-binutils/console.log.xz | Bin 30460 -> 30932 bytes 05-build_abe-stage1/console.log.xz | Bin 91576 -> 92120 bytes 06-clean_sysroot/console.log.xz | Bin 332 -> 332 bytes 07-build_abe-linux/console.log.xz | Bin 8704 -> 8812 bytes 08-build_abe-glibc/console.log.xz | Bin 233548 -> 235552 bytes 09-build_abe-stage2/console.log.xz | Bin 226796 -> 223644 bytes 10-build_abe-gdb/console.log.xz | Bin 38124 -> 37320 bytes 11-build_abe-qemu/console.log.xz | Bin 32188 -> 32448 bytes 12-check_regression/console.log.xz | Bin 5092 -> 3412 bytes 12-check_regression/mail-body.txt | 12 ++++++- 13-update_baseline/console.log | 66 +++++++++++++++++------------------ dashboard/dashboard-generate.sh | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 14 ++++++-- mail/mail-subject.txt | 2 +- manifest.sh | 26 +++++++------- 19 files changed, 73 insertions(+), 53 deletions(-)