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_gcc/master-aarch64 in repository toolchain/ci/base-artifacts.

discards 70c90fd2e44 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] discards 0be3119bf2e 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] discards a1d30d36841 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] discards c5f8ecccc65 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] discards 4f39e57dc7f 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] discards c6a8faa8a47 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] discards a73ab44a643 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] discards ae2eb7d023c 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] discards 3096966845c 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] discards f660a0761fc 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 1dfaf4b1357 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 46bb73efbb1 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards e2ba479e95f 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards e88a7772182 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 8703393d6e3 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards d378abc5250 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards 602a5cb86c4 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards a6585005bc1 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards ed8ebad5d73 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards f15f9b1655b 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards c4dc31b2f33 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards 16aec4efe26 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards beb3f600360 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 9ec78ec9885 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards 8eb693939a3 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards 81cc23e7a70 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 488b8e2faa9 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards e2d1dc6f9fc 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 6b050bc40e4 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards e820c83914d 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards 693415cb464 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards 2bb789c4ff3 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 3e119696413 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 6536bda1370 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 5dded805d97 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 19bfc325240 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 4f131cbe6a2 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 4f961c08229 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 3f09e35e2ec 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 424cad60937 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards ba9e373971e 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 828551ad315 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards 781914b3eee 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards 4b071039391 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards a79aac27e7c 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 64ef754c41b 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 2402e1b00cd 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards a157be169c5 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 1347c4cfb32 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards a9618718e8b 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards 3995eebe51f 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards dd0ab66cd95 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 8d0a6c4bdb3 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 08e5b90db90 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards e4057d10d4a 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards 5230d30a0c7 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 408a7ec0ae6 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 51e3df69586 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards 09bd5a0dcdc 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards dd6514f31d2 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards 2ad11d2bd8f 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards 29861806368 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards 7e962a10fb4 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards 34d57cc55a3 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 9c99e6b6416 152: onsuccess: #903: 1: Success after linux: 22 commits discards 597bddef481 151: onsuccess: #902: 1: Success after glibc: 8 commits discards 2e5f6a6676c 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 2e3fb7316bd 149: onsuccess: #899: 1: Success after binutils: 15 commits discards 67eee476656 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards c60efb3d31a 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 2b224bb2b6b 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 123cf354bb7 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 73bcbf546bd 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards e24a8501a53 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards d5233fd50a7 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 918031c11f7 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards d03f0992220 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards a37e76f0614 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 919868ce244 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards d3d0e03cc75 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards fdb4f687cfb 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 437d3c11b7f 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 8ee99ca1ce8 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards 5da685f53e4 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards c2acc8b7960 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 18978993849 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards c67f6c81caa 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards 8dc8820d522 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 17b1791f22c 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 9cfd97cc066 127: onsuccess: #874: 1: Success after linux: 219 commits discards b5ea0719085 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 4aca6cdc089 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 269d07748ed 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 0c7a76c38df 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards a355178a51b 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 99fa8b52b33 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 045c2fc634b 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 175af3b6ab3 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards 42bde7837e7 118: onsuccess: #863: 1: Success after linux: 12 commits discards 0d566b8d81a 117: onsuccess: #861: 1: Success after binutils: 18 commits discards fca174bb94c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 0277e9b48cb 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 765988e0c00 117: onsuccess: #861: 1: Success after binutils: 18 commits new 5649990f2f6 118: onsuccess: #863: 1: Success after linux: 12 commits new 117846bc1a6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new 7ab02d6f344 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new dcb06c2d879 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 0e32ac8d0dd 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new ffb09ba5e36 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new f9f1e60f12a 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new d1fba6d05a6 125: onsuccess: #871: 1: Success after binutils: 26 commits new ae1411e9d32 126: onsuccess: #873: 1: Success after glibc: 2 commits new fdef2a41fd6 127: onsuccess: #874: 1: Success after linux: 219 commits new 14e4096389c 128: onsuccess: #876: 1: Success after binutils: 12 commits new d21ddb240ed 129: onsuccess: #878: 1: Success after linux: 3008 commits new c92b8c9487c 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 2a55bb145a2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 4da108c5048 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new bb8ea5a73aa 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 5eddae7c0e0 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new d0a85546c22 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new 943cf01ba00 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new cd6b4e1db6c 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new f260f5880a1 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new f9d3908a89d 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 2910dfd40e8 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new d0a83df708f 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new ff79216d0db 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new dbe23f1ddc9 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new 05fee0c474c 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 004379dae22 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 69d16fcc334 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new eb91382204c 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new d67c0df7e89 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 71abfaf707d 149: onsuccess: #899: 1: Success after binutils: 15 commits new df7bde75281 150: onsuccess: #900: 1: Success after gcc: 11 commits new 1b903196928 151: onsuccess: #902: 1: Success after glibc: 8 commits new e818c859931 152: onsuccess: #903: 1: Success after linux: 22 commits new 9c721d6e82b 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new a4ee98b8a35 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 53bb1212170 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 8af4e763767 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 597be74ebbc 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new de6b77be860 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new f4c2bcc85e1 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new 02ba42856f3 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new c653d420a7f 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new fc9b5c60d08 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 6ab628de2bd 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 827b2001463 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new e5c92cf47a5 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 48d3ecde3b0 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 4a6507a26cd 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new c1559781aa3 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 97098cfb98f 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new 1b4a91e5805 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new a41c73da526 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new dc806860238 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new 69dda0663f1 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 38bbd879da9 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new eb1718e0ae4 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new 01b64eee1b6 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new c4d073bcc4d 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new 3b95095739e 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new 286b6c19dd0 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 563b6909cab 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new d1978591ab9 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 98f1b97b858 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 2417a409e96 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new dc31dceefa7 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 9b010da1b7e 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new 012393dd4e9 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new e6831c2e6c9 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new c5eb6941032 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 93e52502e3f 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new ff055f181f1 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new 75dac2f8d29 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 1bddda13fdc 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new 0c38546e327 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new b6730b04c83 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 5b9c26b0d6b 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 12ecfcbb653 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a13b1dc0d6f 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 423c8190c31 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new 91cf4dbd71f 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new f7f6a298a90 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new f033481b54b 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 10693dba76f 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new a1925757d05 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 5d28eef5708 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new 387f4c84a3a 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new 9d4db0a8952 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 291811ee914 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 2a599865a60 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...] new 98cd24da694 209: onsuccess: #14: 1: Success after binutils/gcc/linux/gl [...] new 3c495bdab7c 210: onsuccess: #15: 1: Success after binutils/gcc/linux/gd [...] new 6cd7d7f2e2f 211: onsuccess: #16: 1: Success after binutils/gcc/linux/gl [...] new 9ee2e6d355e 212: onsuccess: #17: 1: Success after binutils/gcc/linux/gd [...] new 0f2924b75f0 213: onsuccess: #18: 1: Success after binutils/gcc/linux/gl [...] new ffd63558fce 214: onsuccess: #19: 1: Success after binutils/gcc/linux/gl [...] new 0dfbbcb2a59 215: onsuccess: #20: 1: Success after binutils/gcc/linux/gl [...] new ebe6e532d70 216: onsuccess: #21: 1: Success after binutils/gcc/linux/gd [...] new 29083c1810d 217: onsuccess: #22: 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 (70c90fd2e44) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_check_gcc/mas [...]

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 1784 -> 1812 bytes 02-prepare_abe/console.log.xz | Bin 3436 -> 2476 bytes 03-build_abe-binutils/console.log.xz | Bin 39272 -> 35460 bytes 04-build_abe-gcc/console.log.xz | Bin 205432 -> 203444 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8536 -> 8564 bytes 07-build_abe-glibc/console.log.xz | Bin 246684 -> 241712 bytes 08-build_abe-gdb/console.log.xz | Bin 39036 -> 34944 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3812 -> 3792 bytes 10-build_abe-check_gcc/console.log.xz | Bin 9572 -> 9144 bytes 11-check_regression/console.log.xz | Bin 6112 -> 5416 bytes 11-check_regression/results.compare | 26 +- 11-check_regression/results.compare2 | 220 +- 12-update_baseline/console.log | 58 +- 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 | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 34 +- sumfiles/g++.log.sep.xz | Bin 67848 -> 88156 bytes sumfiles/g++.log.xz | Bin 3694464 -> 3689380 bytes sumfiles/g++.sum | 39 +- sumfiles/g++.sum.sep | 12657 +++++++++++++++++++------------- sumfiles/gcc.log.sep.xz | Bin 86276 -> 64488 bytes sumfiles/gcc.log.xz | Bin 3207656 -> 3257984 bytes sumfiles/gcc.sum | 6 +- sumfiles/gcc.sum.sep | 6614 ++++++++++------- sumfiles/gfortran.log.sep.xz | Bin 21328 -> 173784 bytes sumfiles/gfortran.log.xz | Bin 1086252 -> 1074456 bytes sumfiles/gfortran.sum | 2 +- sumfiles/gfortran.sum.sep | 4165 +++++++---- sumfiles/libatomic.log.xz | Bin 2304 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235544 -> 235400 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2696 -> 2688 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.sep.xz | Bin 19096 -> 13108 bytes sumfiles/libstdc++.log.xz | Bin 444864 -> 453548 bytes sumfiles/libstdc++.sum.sep | 257 +- 44 files changed, 15089 insertions(+), 9011 deletions(-)