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 1008ae9026 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits discards b19b85984d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits discards a432206a91 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits discards 08118e22a5 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits discards b295598339 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits discards a51e61b7d6 140: onsuccess: #1545: 1: Success after gcc: 7 commits discards 6defc9fec6 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits discards 902a812ee0 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits discards b3bf804c10 137: onsuccess: #1542: 1: Success after gcc: 4 commits discards 4892af99a8 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] discards b0289eef0e 135: force: #1540: 2: Success after gcc: 23 commits discards 7cf0632137 134: onsuccess: #1538: 2: Success after binutils: 2 commits discards 940b326fd2 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits discards 3b21bbc36e 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 311dff2f9d 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 25a3eafc40 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards d50d69df6a 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards d17853eb7a 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 9ae584c84c 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards 9fafe3d275 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards 99198d6b09 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 9869e93cc9 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards d4446a9351 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 51b506434b 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 9f41f5c1b2 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 4c638b221a 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards a6b217ad02 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 42f474eb54 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 51ca5f14f9 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards bbc6922d43 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 41165c04de 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 8c5acdb23f 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 0b7e179396 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards ba7bb7c121 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards ee8b70dbb7 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards e591fe8a03 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 826e704351 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 53fe16f06d 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 7fe683f38c 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 63fb2994be 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 5940289390 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards f82e0d5681 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 0a483367d8 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 625a4d54c1 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 929d1d07b7 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 89858fb943 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards 67345f00f9 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards bdb82ccd81 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards cac97a60a1 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 47e0ad8f1d 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 5346c23b6e 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards aa15ac5978 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards a74bdf2ee0 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards c215daa329 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 606726f2f2 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards ef3566c8f2 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards a56e017864 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards e0406187df 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 7baa5547bf 87: onsuccess: 2: Success after gcc: 4 commits discards ba82fc5bfc 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards d7a2858538 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1a13cdd30c 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards 7195d91775 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 633cafa317 82: onsuccess: 1: Successful build after gcc: 3 commits discards 53b056092c 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards 31f2aa500c 80: force: 2: Successful build after gcc: 14 commits discards d4d961c305 79: onsuccess: 2: Successful build after binutils: 5 commits discards 137c0618c0 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards b3eb998a35 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 3962942472 76: onsuccess: 2: Successful build after gcc: 12 commits discards b119b8019e 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 980bd232cd 74: onsuccess: 2: Successful build after baseline build: no [...] discards 338f47b194 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards 3688a2a0c0 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 011aa66f8f 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 3af998297d 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 2cacaa3123 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 83fcd6595a 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards a9561b32fa 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 8c94a3bfdc 66: onsuccess: 2: Successful build after gcc: 9 commits discards 88e827ea8d 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 98512795d2 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards bf7792f53a 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 6ebc0e678c 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 50a084f395 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 8a18d0ff57 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards b23567c402 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards 60727f43ec 58: force: 2: Successful build after gcc: 6 commits discards e14d5d94d0 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 01352dfdd0 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 060fbe79ce 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9beff6f3e9 54: onsuccess: 2: Successful build after gcc: 5 commits discards 257f8ba30b 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 8be81dddc4 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards db814157a9 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards cd4715d929 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 9149c4bd51 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards b18875c449 48: onsuccess: 2: Successful build after gcc: 4 commits discards 0a8e4ad195 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9f80016f1e 46: onsuccess: 2: Successful build after baseline build: no [...] discards d101dfc6d2 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f5e956d7b0 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new f06107854e 46: onsuccess: 2: Successful build after baseline build: no [...] new 239f8c0512 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3da05e9175 48: onsuccess: 2: Successful build after gcc: 4 commits new e2495f68cb 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 83eddf11a3 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new f79c8d70db 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4b760cc8a7 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new d147881e61 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new cc73a78799 54: onsuccess: 2: Successful build after gcc: 5 commits new 19a2efdc05 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3bc42c93e1 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 037288407b 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new fa009c0ef8 58: force: 2: Successful build after gcc: 6 commits new 116a753939 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new 6ef718264a 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 8a494e9f20 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 392bf791aa 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new fee6cd200e 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6d8c5e01ba 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f36693b53c 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new cbeab6460c 66: onsuccess: 2: Successful build after gcc: 9 commits new b4d9034503 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new c01862b176 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 5735eaa664 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d3c3f50d56 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 8684c09049 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new cd263b02a7 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new aae8b94592 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new ae2ffdc240 74: onsuccess: 2: Successful build after baseline build: no [...] new 430a59e0f1 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new fc376564b7 76: onsuccess: 2: Successful build after gcc: 12 commits new a338166289 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 3e4ff4899b 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new f19d575de5 79: onsuccess: 2: Successful build after binutils: 5 commits new 4863026dac 80: force: 2: Successful build after gcc: 14 commits new 4db71b7e97 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 40ece67c42 82: onsuccess: 1: Successful build after gcc: 3 commits new 2f40a33273 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 8fb8bfaf6e 84: onsuccess: 2: Success after binutils/gcc: 15 commits new f223322a34 85: onsuccess: 2: Success after binutils/gcc: 25 commits new eef808f40b 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 4fb48c6823 87: onsuccess: 2: Success after gcc: 4 commits new b571f486b2 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 5baaa4cc9f 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 1405440be1 90: onsuccess: 2: Success after binutils/gcc: 16 commits new e562d49a14 91: onsuccess: 2: Success after binutils/gcc: 7 commits new d5191d5d4e 92: onsuccess: 2: Success after binutils/gcc: 9 commits new c59064a16b 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 1cb957ff2b 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new 4a36b90045 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 88d1b02848 96: onsuccess: #1452: 2: Success after gcc: 2 commits new d8c28618cd 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 5bd25c4176 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new 2db304dedb 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 7ffb66bdad 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new dfd0bb1126 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new dd87795340 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new e563ccee47 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 049f749e2d 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new 45522236d3 105: onsuccess: #1506: 2: Success after gcc: 2 commits new bf9432455e 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 54dc6bdb3b 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new 3d0a9e7a8e 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 498858025b 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new 597c1968c0 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 3429488967 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new 86a85e079d 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new f2e2dc612a 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 26a5718443 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 79b81d6bf6 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new 38f772af45 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new ae605b17b3 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 05be128bc2 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 0bd5eb0a34 119: onsuccess: #1520: 2: Success after binutils: 8 commits new fd27040209 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new f7582a7051 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 5bbce4350a 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new e852636613 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new c778c74646 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new e16470338d 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new b9518c9f59 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new d760991ab4 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new d31ba60f5f 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new 72b2875d76 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 25da18b00d 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new 4bc4a5484a 131: onsuccess: #1534: 2: Success after gcc: 9 commits new c2596e907a 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new 33cf5d36a7 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 commits new 60e63550c0 134: onsuccess: #1538: 2: Success after binutils: 2 commits new 2988329f78 135: force: #1540: 2: Success after gcc: 23 commits new 65210d164f 136: force: #1541: 1: Failure after basepoints/gcc-13-2871-g [...] new 21cee9c2f6 137: onsuccess: #1542: 1: Success after gcc: 4 commits new c127f12fe2 138: onsuccess: #1543: 1: Success after binutils/gcc: 18 commits new d4b3aa2950 139: onsuccess: #1544: 1: Success after binutils/gcc: 9 commits new cd33ca8892 140: onsuccess: #1545: 1: Success after gcc: 7 commits new 6e487b535d 141: onsuccess: #1546: 1: Success after binutils/gcc: 6 commits new 54776a566b 142: onsuccess: #1547: 1: Success after binutils/gcc: 9 commits new 0902c51bb7 143: onsuccess: #1548: 1: Success after binutils/gcc: 3 commits new 6723a8524d 144: onsuccess: #1549: 1: Success after binutils/gcc: 9 commits new 729315b960 145: onsuccess: #1550: 1: Success after binutils/gcc: 8 commits new 18750231c6 146: onsuccess: #1551: 1: Success after binutils/gcc: 5 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 (1008ae9026) \ 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 1660 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2740 bytes 04-build_abe-binutils/console.log.xz | Bin 51624 -> 51552 bytes 05-build_abe-bootstrap/console.log.xz | Bin 112108 -> 113416 bytes 06-check_regression/console.log.xz | Bin 2948 -> 2748 bytes 07-update_baseline/console.log | 40 +++++++++++++++++----------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 18 +++++++-------- 13 files changed, 35 insertions(+), 35 deletions(-)