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 891849fa9 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits discards aadcd744d 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits discards 038d17882 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits discards 06a7d0eef 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits discards 2007c2d42 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits discards 970d64d5e 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits discards 93af6b019 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits discards 064ea1e3f 119: onsuccess: #1520: 2: Success after binutils: 8 commits discards 6568261d0 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits discards 0461d7a68 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits discards ae5e2e63f 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits discards 1786eda95 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits discards 7ed6f7e66 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits discards 3e6b10163 113: onsuccess: #1514: 2: Success after gcc: 5 commits discards 2915be850 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits discards 68248f6cb 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits discards ebbff04d8 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits discards df8dce25d 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] discards 647305c3f 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits discards 29401832a 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] discards 8971bdb8e 106: onsuccess: #1507: 2: Success after gcc: 2 commits discards 422d72ebb 105: onsuccess: #1506: 2: Success after gcc: 2 commits discards 2c8c47fe4 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits discards 6bccf2097 103: onsuccess: #1504: 2: Success after gcc: 2 commits discards 4a72835a9 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits discards b37b5ce4c 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits discards e2e3456d6 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits discards d19c4e299 99: onsuccess: #1455: 2: Success after baseline build: no new [...] discards e96be71f9 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] discards 701537efc 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits discards 300c0a968 96: onsuccess: #1452: 2: Success after gcc: 2 commits discards 6a644fa3c 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] discards 1383bb758 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] discards 7170c5df1 93: onsuccess: 2: Success after binutils/gcc: 3 commits discards 9aea4df35 92: onsuccess: 2: Success after binutils/gcc: 9 commits discards 7a87de2cb 91: onsuccess: 2: Success after binutils/gcc: 7 commits discards ac4d1e990 90: onsuccess: 2: Success after binutils/gcc: 16 commits discards 32184ceb2 89: onsuccess: 2: Success after binutils/gcc: 4 commits discards d35d7079a 88: onsuccess: 2: Success after binutils/gcc: 25 commits discards f9400d6d1 87: onsuccess: 2: Success after gcc: 4 commits discards e9f74d9df 86: onsuccess: 2: Success after binutils/gcc: 10 commits discards ac85c8c5c 85: onsuccess: 2: Success after binutils/gcc: 25 commits discards 93632ed45 84: onsuccess: 2: Success after binutils/gcc: 15 commits discards e65000b0f 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits discards 587852347 82: onsuccess: 1: Successful build after gcc: 3 commits discards 166e326b2 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] discards 120d561ca 80: force: 2: Successful build after gcc: 14 commits discards 788bc2ff0 79: onsuccess: 2: Successful build after binutils: 5 commits discards 8d68ba3dc 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits discards 5dfe52664 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 1764993ab 76: onsuccess: 2: Successful build after gcc: 12 commits discards 8c10ccde8 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards 7e03f5ee5 74: onsuccess: 2: Successful build after baseline build: no n [...] discards 6091b0d57 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] discards babb6ce9e 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards d34cb0427 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] discards ea246eb61 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards e13f94152 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards e6e93fa50 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits discards 7c1b99423 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 51fd40b30 66: onsuccess: 2: Successful build after gcc: 9 commits discards 3e284b012 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 66e28f23b 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards fd090b1e4 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards cd7564b9b 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 65416ab10 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits discards f3ff53432 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] discards a2e2845f4 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] discards a4349ae88 58: force: 2: Successful build after gcc: 6 commits discards 8969a29f5 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] discards efdeb6c1b 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 622f4e164 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 1d6ebc4e4 54: onsuccess: 2: Successful build after gcc: 5 commits discards 451548d84 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits discards e6b845bd6 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 9faa548d0 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits discards 9a1083d72 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 35fa40845 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ffb13f4f7 48: onsuccess: 2: Successful build after gcc: 4 commits discards c4955f6b2 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits discards 6ad08e198 46: onsuccess: 2: Successful build after baseline build: no n [...] discards a9fd9517f 45: onsuccess: 2: Successful build after binutils: Fix crash [...] discards 59f2c72bd 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards cb10377e8 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] discards 9b1581117 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] discards 7a5a7c95c 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] discards bd56fdf15 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits discards 7212e3b0b 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 0da0c938f 38: onsuccess: 2: Successful build after gcc: 2 commits discards 66e1576bf 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits discards ccfeaeb22 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 993a14db7 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits discards 8e1b9d9aa 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards a5172a193 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits discards 9536fcd8e 32: onsuccess: 2: Successful build after gcc: 6 commits discards 1d5a6eb4b 31: onsuccess: 2: Successful build after gcc: 6 commits discards 7ea314826 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards 203efcd71 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits discards 9ed4325c0 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits discards caf7702c6 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits discards d97715cab 26: onsuccess: binutils-gcc: 2 new ecc8b3aea 26: onsuccess: binutils-gcc: 2 new 6df96be90 27: onsuccess: 2: Successful build after binutils/gcc: 14 commits new ae62dfa71 28: onsuccess: 2: Successful build after binutils/gcc: 8 commits new fb2ea6c7e 29: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 57fd06a9a 30: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 255821763 31: onsuccess: 2: Successful build after gcc: 6 commits new f56cac85f 32: onsuccess: 2: Successful build after gcc: 6 commits new 558993fba 33: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 6bac5be48 34: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 7145100ab 35: onsuccess: 2: Successful build after binutils/gcc: 11 commits new c2696fc51 36: onsuccess: 2: Successful build after binutils/gcc: 8 commits new 2392b1f61 37: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 354fe9193 38: onsuccess: 2: Successful build after gcc: 2 commits new 4d1696a2c 39: onsuccess: 2: Successful build after binutils/gcc: 7 commits new 4728590b3 40: onsuccess: 2: Successful build after binutils/gcc: 2 commits new 395ef45f6 41: onsuccess: 2: Successful build after gcc: libcpp: Impleme [...] new a4c95db9a 42: onsuccess: 2: Successful build after gcc: LoongArch: Add [...] new 2a0d07c3f 43: onsuccess: 2: Successful build after gcc: fortran: Drop - [...] new fa2e07ccc 44: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 4535b65f0 45: onsuccess: 2: Successful build after binutils: Fix crash [...] new 046e78e9d 46: onsuccess: 2: Successful build after baseline build: no n [...] new a304a07ca 47: onsuccess: 2: Successful build after binutils/gcc: 3 commits new cd79fa22b 48: onsuccess: 2: Successful build after gcc: 4 commits new 830fe0157 49: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 7e976a8ef 50: onsuccess: 2: Successful build after binutils/gcc: 8 commits new e7a32427d 51: onsuccess: 2: Successful build after binutils/gcc: 6 commits new 4dcf00b46 52: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 741d46e27 53: onsuccess: 2: Successful build after binutils/gcc: 9 commits new 2fc4efc37 54: onsuccess: 2: Successful build after gcc: 5 commits new 7b3a871ad 55: onsuccess: 2: Successful build after binutils/gcc: 4 commits new f47f131a5 56: onsuccess: 2: Successful build after binutils/gcc: 6 commits new afc5da493 57: onsuccess: 2: Successful build after binutils: gdb: new ' [...] new 6a1c7e1e2 58: force: 2: Successful build after gcc: 6 commits new fa0074356 59: force: 1: Regression after gcc: libstdc++: Optimize opera [...] new 3590c6c25 60: onsuccess: 1: Successful build after gcc: libstdc++: Fix [...] new 1069db899 61: onsuccess: 2: Successful build after binutils/gcc: 22 commits new db8042da8 62: onsuccess: 2: Successful build after binutils/gcc: 11 commits new b7e22fe17 63: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f7db1f53f 64: onsuccess: 2: Successful build after binutils/gcc: 4 commits new df74436cc 65: onsuccess: 2: Successful build after binutils/gcc: 7 commits new f3a62ce8a 66: onsuccess: 2: Successful build after gcc: 9 commits new 0362bb1b0 67: onsuccess: 2: Successful build after binutils/gcc: 7 commits new d7422f10c 68: onsuccess: 2: Successful build after binutils/gcc: 10 commits new 5f4d05a24 69: onsuccess: 2: Successful build after binutils/gcc: 4 commits new 1dbdfc756 70: onsuccess: 2: Successful build after binutils/gcc: 3 commits new 4835d521b 71: onsuccess: 2: Successful build after gcc: libstdc++: Add [...] new b73c86f4f 72: onsuccess: 2: Successful build after binutils/gcc: 4 commits new d1fe80564 73: onsuccess: 2: Successful build after binutils: PR29494 Tr [...] new 956e2a727 74: onsuccess: 2: Successful build after baseline build: no n [...] new c653f93b2 75: onsuccess: 2: Successful build after binutils/gcc: 5 commits new 7ddb2fb38 76: onsuccess: 2: Successful build after gcc: 12 commits new 5e8916491 77: onsuccess: 2: Successful build after binutils/gcc: 3 commits new b27e7bc49 78: onsuccess: 2: Successful build after binutils/gcc: 24 commits new 7967f4b23 79: onsuccess: 2: Successful build after binutils: 5 commits new 1d04ff6f9 80: force: 2: Successful build after gcc: 14 commits new fb9049a30 81: force: 1: Regression after gcc: omp-simd-clone: Allow fix [...] new 3001c522d 82: onsuccess: 1: Successful build after gcc: 3 commits new fd923c70d 83: onsuccess: 2: Successful build after binutils/gcc: 12 commits new d6498a2f1 84: onsuccess: 2: Success after binutils/gcc: 15 commits new 16d933442 85: onsuccess: 2: Success after binutils/gcc: 25 commits new 1eb4623f5 86: onsuccess: 2: Success after binutils/gcc: 10 commits new 657298424 87: onsuccess: 2: Success after gcc: 4 commits new c5365900e 88: onsuccess: 2: Success after binutils/gcc: 25 commits new 0fc53aa45 89: onsuccess: 2: Success after binutils/gcc: 4 commits new 824c7f2ed 90: onsuccess: 2: Success after binutils/gcc: 16 commits new 70cd0ebe9 91: onsuccess: 2: Success after binutils/gcc: 7 commits new 2345057bb 92: onsuccess: 2: Success after binutils/gcc: 9 commits new d726a7d98 93: onsuccess: 2: Success after binutils/gcc: 3 commits new 25517ad1a 94: onsuccess: 2: Success after gcc: openmp: Partial OpenMP 5 [...] new 5e846caae 95: onsuccess: #1451: 2: Success after basepoints/gcc-13-2389 [...] new 79ff610c9 96: onsuccess: #1452: 2: Success after gcc: 2 commits new 94120b6d5 97: onsuccess: #1453: 2: Success after binutils/gcc: 2 commits new 09f0609df 98: onsuccess: #1454: 2: Success after basepoints/gcc-13-2393 [...] new 2c49e048b 99: onsuccess: #1455: 2: Success after baseline build: no new [...] new ae56dceb7 100: onsuccess: #1458: 2: Success after binutils/gcc: 40 commits new bd1034d8e 101: onsuccess: #1502: 2: Success after binutils/gcc: 358 commits new 914da4c1d 102: onsuccess: #1503: 2: Success after binutils/gcc: 2 commits new 6d347eb27 103: onsuccess: #1504: 2: Success after gcc: 2 commits new 42e170a2a 104: onsuccess: #1505: 2: Success after binutils/gcc: 2 commits new cea37e30b 105: onsuccess: #1506: 2: Success after gcc: 2 commits new 9e10e2563 106: onsuccess: #1507: 2: Success after gcc: 2 commits new 6b7a78d80 107: onsuccess: #1508: 2: Success after basepoints/gcc-13-271 [...] new 2dd9e65c8 108: onsuccess: #1509: 2: Success after binutils/gcc: 2 commits new 6cf173f24 109: onsuccess: #1510: 2: Success after basepoints/gcc-13-271 [...] new d46af86bd 110: onsuccess: #1511: 2: Success after binutils/gcc: 4 commits new 246f697c3 111: onsuccess: #1512: 2: Success after binutils/gcc: 2 commits new b2931d4b9 112: onsuccess: #1513: 2: Success after binutils/gcc: 4 commits new 21857fd03 113: onsuccess: #1514: 2: Success after gcc: 5 commits new 6feb1c4aa 114: onsuccess: #1515: 2: Success after binutils/gcc: 15 commits new 48eb5b730 115: onsuccess: #1516: 2: Success after binutils/gcc: 11 commits new c559869f0 116: onsuccess: #1517: 2: Success after binutils/gcc: 7 commits new 92647811a 117: onsuccess: #1518: 2: Success after binutils/gcc: 14 commits new 5065f9248 118: onsuccess: #1519: 2: Success after binutils/gcc: 11 commits new 2119fedc6 119: onsuccess: #1520: 2: Success after binutils: 8 commits new 1fe97702d 120: onsuccess: #1521: 2: Success after binutils/gcc: 4 commits new 4b24ae892 121: onsuccess: #1522: 2: Success after binutils/gcc: 7 commits new 0cbe18e71 122: onsuccess: #1523: 2: Success after binutils/gcc: 22 commits new 8b7f8220c 123: onsuccess: #1524: 2: Success after binutils/gcc: 34 commits new 7e39fc504 124: onsuccess: #1527: 2: Success after binutils/gcc: 24 commits new ff890f71d 125: onsuccess: #1528: 2: Success after binutils/gcc: 6 commits new 610429ad4 126: onsuccess: #1529: 2: Success after binutils/gcc: 8 commits new 06264941e 127: onsuccess: #1530: 2: Success after binutils/gcc: 3 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 (891849fa9) \ 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 -> 1684 bytes 02-prepare_abe/console.log.xz | Bin 2728 -> 2732 bytes 04-build_abe-binutils/console.log.xz | Bin 52380 -> 50768 bytes 05-build_abe-bootstrap/console.log.xz | Bin 466104 -> 469224 bytes 06-check_regression/console.log.xz | Bin 2884 -> 2640 bytes 07-update_baseline/console.log | 36 +++++++++++++++++----------------- 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, 33 insertions(+), 33 deletions(-)