This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_native_check_binutils/master-aarch64 in repository toolchain/ci/base-artifacts.
discards 136c7dd6982 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] discards 2ce73292955 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] discards f0db1ae243b 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] discards 36d45c2932e 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] discards a0c24f1790b 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] discards 5a9e674ff64 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] discards 631b6fd8081 214: onsuccess: #26: 1: Success after binutils: 12 commits discards 385e2337872 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] discards d5083f20a22 212: force: #24: 1: Success after binutils: 2 commits discards 95eebc834e9 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits discards bb6fd47c0c3 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards 296bc20efd1 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards 9ce599b4142 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards cc41b1a9fcf 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards 09100b178a8 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards 7f7463f786c 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards 9ee2e8ea119 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 8877a962fb7 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards 3cbf5bc2d23 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 6964c43f2d6 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards c6fa03d8375 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e1e7a4703c1 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 713ca2796af 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 8ae6ff50ea5 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards ce459d5c437 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 91f79335d91 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 716d0056c3f 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 73431d4c57e 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards bcf8a160f7a 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 334e4c77980 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards e500d5ca858 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] discards 5036f2b007f 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] discards a450bcd1b2e 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] discards cf556430ae5 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] discards 66f737c07b8 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] discards 39a25b9580c 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] discards 0ffc83ece3c 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] discards 8026dbc02e9 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] discards 8679c2dd366 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] discards 818bfc76862 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] discards ba6b23e508c 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] discards b2b37289e13 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] discards 632dffee693 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] discards 9713a002504 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] discards 8beb508d088 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] discards bb2908a6031 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] discards f30cf98095a 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] discards 45175a08ac3 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] discards b4d673c1c53 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] discards 5b3329f6158 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] discards 7e3f17d8e3f 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] discards 65be537bc61 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] discards 33dcc9fe76c 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] discards 3650b248e9f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] discards 67304e26b51 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] discards 6fd070bd38d 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] discards 64a7a6f903a 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] discards 1b3d3583d24 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] discards e5a2192eb41 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] discards 8141b59f299 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] discards e56ede8784a 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] discards bec6d08f378 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] discards d531bf4e4ca 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] discards 2b4aac4625e 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] discards 2df0b75e78f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] discards 9c35c18b718 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] discards 6885a9a9445 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] discards 8f1e7db9b29 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] discards 89445c4da6a 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] discards 279d1419351 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] discards c77293462bc 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] discards a3da735e6a3 149: onsuccess: #684: 1: Success after linux: 10 commits discards 082d5d2ad45 148: onsuccess: #683: 1: Success after glibc: 9 commits discards b59172deab3 147: onsuccess: #681: 1: Success after gcc: 6 commits discards ff7fae4ce9e 146: onsuccess: #680: 1: Success after binutils: 20 commits discards d992f2a78ab 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] discards 147d9c130e5 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] discards 804bd43236c 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] discards 295c3a6b330 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] discards 9f9156ae9eb 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] discards a82992a6514 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] discards 0bb11c278de 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] discards feb103232aa 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] discards 0652fcb9f0e 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] discards 1469de0cd64 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] discards 46dd34df8be 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] discards c7bbcd844da 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] discards 7029374993d 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] discards 6dd496268ae 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] discards dc7a23eb054 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] discards c1398896cab 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] discards 0c1e7a76e93 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] discards 19ed5d38c60 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] discards 46101649cda 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] discards 04c9c2634ee 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] discards 370d7838bce 125: onsuccess: #658: 1: Success after linux: 3224 commits discards 45781bec4b0 124: onsuccess: #657: 1: Success after glibc: 2 commits discards 8db7e2522ef 123: onsuccess: #655: 1: Success after binutils: 22 commits discards e465f6390e0 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] discards 343c8f98e4c 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] discards da1df870a16 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new ac0979791ef 120: onsuccess: #651: 1: Success after binutils/gcc/linux/g [...] new c60d424776b 121: onsuccess: #652: 1: Success after binutils/gcc/linux/g [...] new 5d7e343d90c 122: onsuccess: #653: 1: Success after binutils/gcc/linux/g [...] new 70ae864e477 123: onsuccess: #655: 1: Success after binutils: 22 commits new cb5b967bc7b 124: onsuccess: #657: 1: Success after glibc: 2 commits new 537a2817e3b 125: onsuccess: #658: 1: Success after linux: 3224 commits new 4d1e8c5a43a 126: onsuccess: #659: 1: Success after binutils/gcc/linux/g [...] new ec3d80e4449 127: onsuccess: #660: 1: Success after binutils/gcc/linux/g [...] new 879ec17e65b 128: onsuccess: #661: 1: Success after binutils/gcc/linux/g [...] new 56189f5da52 129: onsuccess: #662: 1: Success after binutils/gcc/linux/g [...] new ad615d1da46 130: onsuccess: #663: 1: Success after binutils/gcc/linux/g [...] new 696e4b9d601 131: onsuccess: #664: 1: Success after binutils/gcc/glibc/g [...] new 07b01434c14 132: onsuccess: #665: 1: Success after binutils/gcc/linux/g [...] new 74c2de29dcf 133: onsuccess: #666: 1: Success after binutils/gcc/linux/g [...] new 732c2ff61f8 134: onsuccess: #667: 1: Success after binutils/gcc/linux/g [...] new 59da88b1803 135: onsuccess: #668: 1: Success after binutils/gcc/linux/g [...] new 7f58674c332 136: onsuccess: #669: 1: Success after binutils/gcc/linux/g [...] new 3ff2bae9933 137: onsuccess: #670: 1: Success after binutils/gcc/gdb: 46 [...] new 443cf80686f 138: onsuccess: #671: 1: Success after binutils/gcc/linux/g [...] new 2d9d92fc21b 139: onsuccess: #672: 1: Success after binutils/gcc/gdb: 28 [...] new f4b4212efc1 140: onsuccess: #673: 1: Success after binutils/gcc/gdb: 26 [...] new 49eda5e29da 141: onsuccess: #674: 1: Success after binutils/gcc/gdb: 12 [...] new 3cbcd12be02 142: onsuccess: #675: 1: Success after binutils/gcc/linux/g [...] new d69278851b6 143: onsuccess: #676: 1: Success after binutils/gcc/linux/g [...] new b27db1acfd4 144: onsuccess: #677: 1: Success after binutils/gcc/linux/g [...] new cae94b84d41 145: onsuccess: #678: 1: Success after binutils/gcc/linux/g [...] new a1e5af08920 146: onsuccess: #680: 1: Success after binutils: 20 commits new 897a35ce4e5 147: onsuccess: #681: 1: Success after gcc: 6 commits new 49e993a5945 148: onsuccess: #683: 1: Success after glibc: 9 commits new 11727ba1560 149: onsuccess: #684: 1: Success after linux: 10 commits new 409b671a1ea 150: onsuccess: #685: 1: Success after binutils/gcc/glibc/g [...] new d0798f19a1d 151: onsuccess: #686: 1: Success after binutils/gcc/linux/g [...] new 331ed43525b 152: onsuccess: #687: 1: Success after binutils/gcc/linux/g [...] new fa91920a935 153: onsuccess: #688: 1: Success after binutils/gcc/linux/g [...] new b7ca4b8236e 154: onsuccess: #689: 1: Success after binutils/gcc/linux/g [...] new 94051a25f15 155: onsuccess: #690: 1: Success after binutils/gcc/linux/g [...] new 92c6133735f 156: onsuccess: #691: 1: Success after binutils/gcc/linux/g [...] new e0c48bdafb3 157: onsuccess: #692: 1: Success after binutils/gcc/linux/g [...] new 7c730c8741a 158: onsuccess: #693: 1: Success after binutils/gcc/linux/g [...] new ee9aea17bfd 159: onsuccess: #694: 1: Success after binutils/gcc/linux/g [...] new 09e1cc55758 160: onsuccess: #695: 1: Success after binutils/gcc/linux/g [...] new e3588dcaef9 161: onsuccess: #696: 1: Success after binutils/gcc/linux/g [...] new c99d0cb7944 162: onsuccess: #697: 1: Success after binutils/gcc/linux/g [...] new cf498eac1ac 163: onsuccess: #698: 1: Success after binutils/gcc/linux/g [...] new 23f91382922 164: onsuccess: #699: 1: Success after binutils/gcc/linux/g [...] new a26e98daee9 165: onsuccess: #700: 1: Success after binutils/gcc/linux/g [...] new 14d1beb814a 166: onsuccess: #701: 1: Success after binutils/gcc/linux/g [...] new 12488e8cf7f 167: onsuccess: #702: 1: Success after binutils/gcc/linux/g [...] new 11031e54b2b 168: onsuccess: #703: 1: Success after binutils/gcc/linux/g [...] new 966888d63ab 169: onsuccess: #704: 1: Success after binutils/gcc/linux/g [...] new 1c829ae9551 170: onsuccess: #705: 1: Success after binutils/gcc/glibc/g [...] new c6743c61c1c 171: onsuccess: #706: 1: Success after binutils/gcc/linux/g [...] new 019da3f76ef 172: onsuccess: #707: 1: Success after binutils/gcc/linux/g [...] new 8ada91956c6 173: onsuccess: #708: 1: Success after binutils/gcc/linux/g [...] new faf846c3992 174: onsuccess: #709: 1: Success after binutils/gcc/linux/g [...] new 56d5e41abb8 175: onsuccess: #710: 1: Success after binutils/gcc/linux/g [...] new 3d2632b0c96 176: onsuccess: #711: 1: Success after binutils/gcc/linux/g [...] new 51ff81e9409 177: onsuccess: #712: 1: Success after binutils/gcc/linux/g [...] new d8af7096426 178: onsuccess: #714: 1: Success after binutils/gcc/linux/g [...] new 81662f34b02 179: onsuccess: #715: 1: Success after binutils/gcc/linux/g [...] new 6a106e5236a 180: onsuccess: #716: 1: Success after binutils/gcc/linux/g [...] new 81edb8fa092 181: onsuccess: #717: 1: Success after binutils/gcc/linux/g [...] new 82ae35fc7d0 182: onsuccess: #718: 1: Success after binutils/gcc/linux/g [...] new d9d46f5ac9d 183: onsuccess: #719: 1: Success after binutils/gcc/gdb: 20 [...] new 9c8c58e5c1a 184: onsuccess: #720: 1: Success after binutils/gcc/linux/g [...] new 1977dd85627 185: onsuccess: #721: 1: Success after binutils/gcc/linux/g [...] new d497cfd35c5 186: onsuccess: #722: 1: Success after binutils/gcc/linux/g [...] new 139aa136c56 187: onsuccess: #723: 1: Success after binutils/gcc/linux/g [...] new 17df9834517 188: onsuccess: #724: 1: Success after binutils/gcc/linux/g [...] new beeae4dc6a8 189: onsuccess: #725: 1: Success after binutils/gcc/linux/g [...] new 4a0d9388480 190: onsuccess: #726: 1: Success after binutils/gcc/linux/g [...] new 9c47b02b1fc 191: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new cd255cb9940 192: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new ed612d36ead 193: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 86f49ac66a9 194: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new d454169b0c5 195: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new d4122b9acde 196: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 06dc79ae0d0 197: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a0533196bc2 198: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 9f43c597711 199: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new f4c10a4a35b 200: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new aac064cef3f 201: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 2be42943967 202: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 4902316cb77 203: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 4f68489e8a9 204: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new cc1c48ae204 205: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 4927e758c81 206: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 7fe2a5bd673 207: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 51618eff352 208: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new 955fec501ea 209: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 1174e76d353 210: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new 333622c042d 211: onsuccess: #23: 1: Success after gcc/linux/gdb: 43 commits new 20e68eb1065 212: force: #24: 1: Success after binutils: 2 commits new f731721f66b 213: force: #25: 1: Failure after gdb-13-branchpoint-1445-g [...] new 403a5256e42 214: onsuccess: #26: 1: Success after binutils: 12 commits new f568e0f77e6 215: onsuccess: #27: 1: Success after binutils/gcc/linux/gd [...] new a8eafbe23a8 216: onsuccess: #30: 1: Success after binutils/gcc/linux/gd [...] new 78bd8f9baea 217: onsuccess: #31: 1: Success after binutils/gcc/linux/gd [...] new 616f3b736dd 218: onsuccess: #32: 1: Success after binutils/gcc/linux/gl [...] new b8bc2ec1fe6 219: onsuccess: #33: 1: Success after binutils/gcc/linux/gd [...] new 79767a1a156 220: onsuccess: #34: 1: Success after binutils/gcc/linux/gd [...] new f3f2f3aa379 221: onsuccess: #35: 1: Success after binutils/gcc/linux/gd [...]
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 (136c7dd6982) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_binutil [...]
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 2336 -> 2048 bytes 02-prepare_abe/console.log.xz | Bin 2504 -> 2572 bytes 03-build_abe-binutils/console.log.xz | Bin 35108 -> 34892 bytes 04-build_abe-gcc/console.log.xz | Bin 202960 -> 203564 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8396 -> 8872 bytes 07-build_abe-glibc/console.log.xz | Bin 241332 -> 241428 bytes 08-build_abe-gdb/console.log.xz | Bin 34700 -> 34396 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3780 -> 3784 bytes 10-build_abe-check_binutils/console.log.xz | Bin 2100 -> 2092 bytes 11-check_regression/console.log.xz | Bin 5032 -> 4908 bytes 11-check_regression/jira-body.txt | 1 - 11-check_regression/mail-body.txt | 2 +- 11-check_regression/results.compare | 8 +++--- 11-check_regression/results.compare2 | 22 +++++---------- 12-update_baseline/console.log | 42 ++++++++++++++--------------- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 1 - mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +++++++++++------------ sumfiles/binutils.log.xz | Bin 63020 -> 62936 bytes sumfiles/binutils.sum | 2 +- sumfiles/gas.log.xz | Bin 83932 -> 84000 bytes sumfiles/gas.sum | 4 +-- sumfiles/ld.log.xz | Bin 122608 -> 122584 bytes sumfiles/ld.sum | 4 +-- 31 files changed, 61 insertions(+), 73 deletions(-) delete mode 100644 11-check_regression/jira-body.txt delete mode 100644 mail/jira-body.txt