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 a1ed2d19db 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits discards 4b1cf6b8e6 131: onsuccess: #1534: 2: Success after gcc: 9 commits discards 961ec6f0b0 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] discards f33a18bf65 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits discards 3bf5a85d4a 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits discards 83dc93b934 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits discards f7f28bc6b7 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards d8fa2ea862 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 4011e7b0c8 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards f2203fc796 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards ffcb2c15f3 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 01d15e2b84 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards d1d84eea2e 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 8e7dc8f5f3 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 381b2db663 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 4c60d35be1 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards dd384f1ea6 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 905b252153 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards c7cace4a37 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards ce8a39f930 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards a52b7dfd70 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 2e59fc5f76 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards 0db736ee3c 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards 76e320024d 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] discards 4bd82289fe 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 4b1f4c1a2e 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] discards 31e92b09dd 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 217c6c7fc4 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards bac95fef81 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 812c415d14 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 3c68baa07b 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards 591b2c26e8 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards 1900f2b7d7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards a41b521e41 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] discards 4c73909176 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] discards 6c32f40287 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 10d29d7338 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 88267cdb6f 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] discards 6d6d606771 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] discards 2c04e9cef1 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards e11ea953d0 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 7c4be3f0b3 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards 2520499fcf 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 3660357f75 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards acd74fbdb8 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards 2407fd94db 87: onsuccess: 2: Success after gcc: 4 commits discards 577c3b14f3 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards 6b1caa01dc 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 1f7c8791ea 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards f8536390b8 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards c8965c492b 82: onsuccess: 1: Successful build after gcc: 3 commits discards 63cb2503cd 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] discards a8e096b120 80: force: 2: Successful build after gcc: 14 commits discards 8b299e6a8e 79: onsuccess: 2: Successful build after binutils: 5 commits discards f96c2cf275 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 39a5cc58eb 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6d4219171e 76: onsuccess: 2: Successful build after gcc: 12 commits discards 3d3a5dc080 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards e6d465eb90 74: onsuccess: 2: Successful build after baseline build: no [...] discards 302d5b9201 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] discards cc55c26efe 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 300831b415 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards 37a13220f1 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 12e77d17d2 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 511d72b1c6 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards b1a1973d0d 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards fec638350d 66: onsuccess: 2: Successful build after gcc: 9 commits discards c3e8658644 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards ef3edda351 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 8d1402f416 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 289a40ce87 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 453174babf 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards 729a3f826e 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards 09728008f0 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] discards ff4029146c 58: force: 2: Successful build after gcc: 6 commits discards bcde870dbd 57: onsuccess: 2: Successful build after binutils: gdb: new [...] discards 821c48bc14 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 1a4f8930cf 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 18eae234da 54: onsuccess: 2: Successful build after gcc: 5 commits discards 4e72a309e5 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards 4b5e3fd3f2 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f975c36cfd 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 49c546dee5 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards d56078fa26 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 058d924680 48: onsuccess: 2: Successful build after gcc: 4 commits discards 9176f6dd6c 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards f3a3092f8e 46: onsuccess: 2: Successful build after baseline build: no [...] discards e09d87cd48 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 919a171958 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards faf00210a8 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] discards 70ba9d9fb3 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards abf1d38edc 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] discards 74bf0987ba 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 26b29cf97f 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards d942a0c0ef 38: onsuccess: 2: Successful build after gcc: 2 commits discards f557021637 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards a93e346cc4 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 71b1af8565 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 18edc15dd0 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9b8972ad83 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 95d5b2cd88 32: onsuccess: 2: Successful build after gcc: 6 commits new cb2e4a0313 32: onsuccess: 2: Successful build after gcc: 6 commits new 9f7383abd0 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 5c5b2ebb2c 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new da159799d3 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 666b532ae7 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 82b820f2b3 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 29af326d00 38: onsuccess: 2: Successful build after gcc: 2 commits new 08f49708b5 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 8326c3607a 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 0fb43e55e8 41: onsuccess: 2: Successful build after gcc: libcpp: Implem [...] new 58dbee6240 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 7fec3cc357 43: onsuccess: 2: Successful build after gcc: fortran: Drop [...] new 0b5ade5829 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new c2bad901b1 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 4aa5c3bd1f 46: onsuccess: 2: Successful build after baseline build: no [...] new e728ef249b 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 9b2e994300 48: onsuccess: 2: Successful build after gcc: 4 commits new 486c89eaaf 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 4cc2f686f3 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 484b040bf6 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new a68745dc8e 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new fae52990b0 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 658da3573b 54: onsuccess: 2: Successful build after gcc: 5 commits new 9b2177e320 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 3d674fbdb4 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 36bd2bf93f 57: onsuccess: 2: Successful build after binutils: gdb: new [...] new e7d67d89ce 58: force: 2: Successful build after gcc: 6 commits new b1d932fe70 59: force: 1: Regression after gcc: libstdc++: Optimize oper [...] new c2183a454f 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new ec1ba848b9 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new 0679ce36b3 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new 0ae9c6063e 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new b11944dfc5 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 46803354a1 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 350cb89061 66: onsuccess: 2: Successful build after gcc: 9 commits new 29869d0549 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f2c5fd92b9 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 010650fbab 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4080f75b9c 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new decb54d7fd 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new 29e00ce3dc 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 8f8980c635 73: onsuccess: 2: Successful build after binutils: PR29494 T [...] new a7a4608897 74: onsuccess: 2: Successful build after baseline build: no [...] new 6d317709e6 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 95e9aa05d4 76: onsuccess: 2: Successful build after gcc: 12 commits new 33039fbb84 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 32b16580fd 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 81dcf03f36 79: onsuccess: 2: Successful build after binutils: 5 commits new 35527b0e5a 80: force: 2: Successful build after gcc: 14 commits new 610ba72399 81: force: 1: Regression after gcc: omp-simd-clone: Allow fi [...] new 9982f43202 82: onsuccess: 1: Successful build after gcc: 3 commits new e4cb93f7f2 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new 485495ffc9 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 0256b6eeaf 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 95e881085a 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 7e5ae6318a 87: onsuccess: 2: Success after gcc: 4 commits new 6abf871286 88: onsuccess: 2: Success after binutils/gcc: 25 commits new ce21a2e86e 89: onsuccess: 2: Success after binutils/gcc: 4 commits new db28a0d831 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 3079e18a41 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 2662bc8a1b 92: onsuccess: 2: Success after binutils/gcc: 9 commits new f7cf1e1c72 93: onsuccess: 2: Success after binutils/gcc: 3 commits new d8967c5064 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP [...] new a72b9ba4cf 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-238 [...] new 8b1201fd7f 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 5452e2c816 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new c1805934ea 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-239 [...] new eec673fd3a 99: onsuccess: #1455: 2: Success after baseline build: no ne [...] new 204d5f8801 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new 3d19d9c20c 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new afa802a411 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 49b552b9fa 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 951e5187bf 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new d0dea262d9 105: onsuccess: #1506: 2: Success after gcc: 2 commits new dee4745c95 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 89ee9c5061 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-27 [...] new b3731fd06c 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 52cabcd1cd 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-27 [...] new ee20e186b6 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new a35858dafa 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new b27f684c80 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 8fdc0dac1a 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 0c918c9858 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new c2c0a5d42f 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new a011184c1c 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 52afa61c36 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new e077507374 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 6a71b14258 119: onsuccess: #1520: 2: Success after binutils: 8 commits new fcac770e8e 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new b9ef79237e 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 4ea1967ba3 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 3f69ecb522 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 22ead2dfb1 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new a462935f2c 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 8e912de85c 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 91cc650849 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 commits new 9d55875d69 128: onsuccess: #1531: 2: Success after binutils/gcc: 2 commits new ba408cc93e 129: onsuccess: #1532: 2: Success after binutils/gcc: 2 commits new 4c4ef3b703 130: onsuccess: #1533: 2: Success after basepoints/gcc-13-28 [...] new a6540e74e0 131: onsuccess: #1534: 2: Success after gcc: 9 commits new d54bc41fa4 132: onsuccess: #1535: 2: Success after binutils/gcc: 2 commits new dd3d5d485d 133: onsuccess: #1536: 2: Success after binutils/gcc: 8 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 (a1ed2d19db) \ 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 1668 -> 1672 bytes 02-prepare_abe/console.log.xz | Bin 2724 -> 2724 bytes 04-build_abe-binutils/console.log.xz | Bin 51316 -> 50732 bytes 05-build_abe-bootstrap/console.log.xz | Bin 464752 -> 465520 bytes 06-check_regression/console.log.xz | Bin 2628 -> 3044 bytes 07-update_baseline/console.log | 38 +++++++++++++++++----------------- 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, 34 insertions(+), 34 deletions(-)