This is an automated email from the git hooks/post-receive script.

tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gcc_bootstrap/master-arm-bootstrap in repository toolchain/ci/base-artifacts.

discards dd3d5d485d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards d54bc41fa4 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards a6540e74e0 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 4c4ef3b703 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards ba408cc93e 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 9d55875d69 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 91cc650849 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 8e912de85c 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards a462935f2c 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 22ead2dfb1 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 3f69ecb522 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 4ea1967ba3 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards b9ef79237e 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards fcac770e8e 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 6a71b14258 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards e077507374 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 52afa61c36 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards a011184c1c 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards c2c0a5d42f 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 0c918c9858 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 8fdc0dac1a 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards b27f684c80 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards a35858dafa 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards ee20e186b6 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 52cabcd1cd 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards b3731fd06c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 89ee9c5061 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards dee4745c95 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards d0dea262d9 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 951e5187bf 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 49b552b9fa 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards afa802a411 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 3d19d9c20c 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 204d5f8801 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards eec673fd3a 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards c1805934ea 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 5452e2c816 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 8b1201fd7f 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards a72b9ba4cf 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards d8967c5064 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards f7cf1e1c72 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 2662bc8a1b 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 3079e18a41 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards db28a0d831 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards ce21a2e86e 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards 6abf871286 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7e5ae6318a 87: onsuccess: 2: Success after gcc: 4 commits discards 95e881085a 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 0256b6eeaf 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 485495ffc9 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards e4cb93f7f2 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 9982f43202 82: onsuccess: 1: Successful build after gcc: 3 commits discards 610ba72399 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 35527b0e5a 80: force: 2: Successful build after gcc: 14 commits discards 81dcf03f36 79: onsuccess: 2: Successful build after binutils: 5 commits discards 32b16580fd 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 33039fbb84 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 95e9aa05d4 76: onsuccess: 2: Successful build after gcc: 12 commits discards 6d317709e6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a7a4608897 74: onsuccess: 2: Successful build after baseline build: no [...] discards 8f8980c635 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 29e00ce3dc 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards decb54d7fd 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 4080f75b9c 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 010650fbab 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards f2c5fd92b9 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 29869d0549 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 350cb89061 66: onsuccess: 2: Successful build after gcc: 9 commits discards 46803354a1 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards b11944dfc5 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 0ae9c6063e 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0679ce36b3 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards ec1ba848b9 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards c2183a454f 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards b1d932fe70 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards e7d67d89ce 58: force: 2: Successful build after gcc: 6 commits discards 36bd2bf93f 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 3d674fbdb4 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9b2177e320 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 658da3573b 54: onsuccess: 2: Successful build after gcc: 5 commits discards fae52990b0 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards a68745dc8e 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 484b040bf6 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 4cc2f686f3 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 486c89eaaf 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 9b2e994300 48: onsuccess: 2: Successful build after gcc: 4 commits discards e728ef249b 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 4aa5c3bd1f 46: onsuccess: 2: Successful build after baseline build: no [...] discards c2bad901b1 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 0b5ade5829 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 7fec3cc357 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 58dbee6240 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 0fb43e55e8 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 8326c3607a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 08f49708b5 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 29af326d00 38: onsuccess: 2: Successful build after gcc: 2 commits discards 82b820f2b3 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 666b532ae7 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards da159799d3 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 5c5b2ebb2c 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9f7383abd0 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new e6d9bbcea0 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3918d1daae 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3837d73b5d 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new c0e189cb8f 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new b258ff252b 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 722fef202e 38: onsuccess: 2: Successful build after gcc: 2 commits new 18a0b7a49d 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 3d0a468d1d 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new d8b269964d 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new 8d1447d96b 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new b28c1fb6b6 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 0daed03447 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 74b3e640f5 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new d8326d6b1d 46: onsuccess: 2: Successful build after baseline build: no [...] new 344204a97a 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new e31b0ad459 48: onsuccess: 2: Successful build after gcc: 4 commits new a760c67c01 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 1438ccbd47 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 8fb0501fb2 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 33e903f044 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 63c2eae550 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 5717b40f9d 54: onsuccess: 2: Successful build after gcc: 5 commits new f13941a381 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 205a0d122a 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new f9db8b251e 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new 56824b40e6 58: force: 2: Successful build after gcc: 6 commits new f2bbe112d8 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 4565e73c4d 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new c31db24021 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new b045792570 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 66389252f6 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 50f7614d8c 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 61e732cb06 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c5b8bbf43c 66: onsuccess: 2: Successful build after gcc: 9 commits new a9ed6dc057 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 0c1303d686 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 51df37a136 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 13ab24b81e 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new f9718d12db 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new e10422b7d7 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 5c3b7619cb 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new 50db48d791 74: onsuccess: 2: Successful build after baseline build: no [...] new ce54d7e462 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 99c787b95a 76: onsuccess: 2: Successful build after gcc: 12 commits new 4851da78f6 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 2d9fe5e1d3 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 21e1db04f8 79: onsuccess: 2: Successful build after binutils: 5 commits new c123d9f161 80: force: 2: Successful build after gcc: 14 commits new 77bbfae6fd 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 222d54b192 82: onsuccess: 1: Successful build after gcc: 3 commits new 23a786859a 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 2cb2a59b22 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 09fe54d620 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 492e129838 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 39dee8b055 87: onsuccess: 2: Success after gcc: 4 commits new 3f30ffc75f 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 89dd5f1269 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 77dc14b393 90: onsuccess: 2: Success after binutils/gcc: 16 commits new d601528e2e 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 162a90ada2 92: onsuccess: 2: Success after binutils/gcc: 9 commits new 95442d9949 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 8f3d5edc1c 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 7fe7024f03 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new ced186f271 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 43d7791a8a 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new b461e42ded 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new cdd04f6bfc 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 3d92c46de3 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 4c6670fbec 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 6849158780 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 8a38fed18d 103: onsuccess: #1504: 2: Success after gcc: 2 commits new b15c9526d3 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 11ac3c8d42 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 835d6f5e3e 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 7819f28d49 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new cce1886f64 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new eaab16ad39 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 560bf8748a 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new a4a243a65a 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 4e2ed16ba3 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 9cc3e72511 113: onsuccess: #1514: 2: Success after gcc: 5 commits new c2893c81ad 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 0ba899f841 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 8c15285fb7 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 2e7e110395 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 5532b7826e 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new c1a80262b5 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 0af15686a7 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 71cdbe37b7 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new fe54488b1a 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new a64fae428e 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new e2176a3213 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new d65a088601 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new cc53e7dd53 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new c2bcde7b20 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 23da624863 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new a4b9578bfb 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 7ec6145ba0 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new f7f2881bbb 131: onsuccess: #1534: 2: Success after gcc: 9 commits new ac3bc4bbe9 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new a1ca4d2fa2 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 80e400ad09 134: onsuccess: #1538: 2: Success after binutils: 2 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 (dd3d5d485d) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gcc_bootstrap/master-arm [...]

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 -> 1616 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2728 bytes 04-build_abe-binutils/console.log.xz | Bin 50732 -> 50776 bytes 05-build_abe-bootstrap/console.log.xz | Bin 465520 -> 462208 bytes 06-check_regression/console.log.xz | Bin 3044 -> 2484 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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 | 17 +++++++-------- 12 files changed, 32 insertions(+), 33 deletions(-)