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-arm in repository toolchain/ci/base-artifacts.
discards 7b5b37d556 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits discards 69571f0718 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] discards 513a06ec84 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] discards b4450f078c 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] discards 2408de5c76 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] discards d41abc135e 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] discards 5359424b13 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] discards 43ab2554b3 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] discards aa797acde3 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] discards 5ef4e39fa4 104: onsuccess: #558: 1: Success after binutils: 3 commits discards d794b270b3 103: onsuccess: #555: 1: Success after binutils: 4 commits discards a801d83529 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] discards 34fb1c0c82 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] discards 6269bf2fe7 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] discards 8e9cae2b12 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] discards 9e29562ed1 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] discards 63862247c4 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] discards ab8abb0895 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] discards 0dde7c3ba9 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] discards 108a150b0b 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] discards 909d6fe85a 93: onsuccess: #544: 1: Success after linux: 34 commits discards 849558613a 92: onsuccess: #543: 1: Success after glibc: 4 commits discards b9142d4f54 91: onsuccess: #539: 1: Success after linux: 27 commits discards 500f118f52 90: onsuccess: #538: 1: Success after glibc: 10 commits discards 6eeedcad2d 89: onsuccess: #536: 1: Success after binutils: 27 commits discards e4f5d80302 88: onsuccess: #534: 1: Success after linux: 12 commits discards d36b538845 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] discards 933770982f 86: onsuccess: #532: 1: Success after gcc: 16 commits discards c2c678b5f7 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] discards f378a6823e 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] discards 71f99c8c9a 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] discards 714516965b 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] discards 90f8f05396 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] discards fd8cab1be0 80: onsuccess: #524: 1: Success after linux: 9 commits discards 394ef4a30f 79: onsuccess: #523: 1: Success after gcc: 25 commits discards 4c8c7c833e 78: onsuccess: #522: 1: Success after binutils: 10 commits discards 96ac1942d5 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] discards ad3624d03c 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] discards 218b98ba5a 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] discards 32e7cca528 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] discards d467645549 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] discards 5d2a3b2fcd 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits discards fe9904709a 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] discards a34ba7413a 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] discards a9c13c4530 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] discards cd0e98332a 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] discards 8ad51daf88 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] discards e0271dab09 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] discards 03d9056f1a 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] discards 2c75c545ee 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] discards 646df1482c 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] discards 821e5b3f9c 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] discards 85c5e3e846 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] discards 283b0f5ab0 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] discards a91f83b1ce 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] discards d446a68d19 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] discards b26a35b583 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] discards d6a33ecfee 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] discards 98e492538c 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] discards a7ef8db185 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] discards d64094cdd9 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] discards fe5d4324ef 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] discards 0c5da81852 51: onsuccess: #493: 1: Success after binutils: 13 commits discards 5896abe026 50: onsuccess: #490: 1: Success after binutils: 6 commits discards 27ba5eabb4 49: onsuccess: #487: 1: Success after binutils: 11 commits discards 3752e029e9 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] discards a97adccea9 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] discards 652ee12038 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] discards 8f12e8194d 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] discards 399a76ab7e 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] discards aacf6acc33 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] discards 721336ded0 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] discards d7b08aa09d 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] discards 8ca9dbb71a 40: onsuccess: #476: 1: Success after linux: 69 commits discards cbffc75a7a 39: onsuccess: #474: 1: Success after binutils: 8 commits discards 2f619784ca 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] discards 86fc42edad 37: onsuccess: #470: 1: Success after binutils: 3 commits discards 39e6ac7216 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] discards 6adf3ffa9f 35: onsuccess: #467: 1: Success after glibc: 2 commits discards 9a9c5d7d99 34: onsuccess: #465: 1: Success after binutils: 11 commits discards e430e5d682 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] discards f4fa79f75f 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] discards 4f99d8b277 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] discards 09185a8ff3 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] discards dd3e43382e 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] discards 31a3865983 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] discards 19f3498642 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] discards 3fa1ba8fe4 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] discards 1b030984c2 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] discards 806d908c15 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] discards f8ed3dff32 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits discards 3386f7c482 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 17d0a1824b 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] discards 82f08f41c0 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards ca982c368d 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 37611deea6 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 138cb3731f 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 66f9840fed 16: onsuccess: 1: Successful build after binutils: 5 commits discards 42cea438f8 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 110e34a069 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] discards 1d7af38af1 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 65f4f58ba2 13: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 5ace759358 14: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 71e25225b1 15: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1ca65d117b 16: onsuccess: 1: Successful build after binutils: 5 commits new 49012c1cee 17: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6a682eaa88 18: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 1f68129484 19: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 6458922eb4 20: onsuccess: 1: Successful build after binutils/gcc/linux/ [...] new 946d499c75 21: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 0f9137d2dc 22: onsuccess: 1: Success after binutils/gcc/linux/glibc/gdb [...] new 90d2f0b0ae 23: onsuccess: 1: Success after binutils/gcc/linux/gdb: 211 commits new f03b3206f7 24: onsuccess: #453: 1: Success after binutils/gcc/linux/gdb [...] new 7b8b095fe9 25: onsuccess: #455: 1: Success after binutils/gcc/linux/gli [...] new 0ec95e3e0a 26: onsuccess: #456: 1: Success after binutils/gcc/linux/gli [...] new af9ae217bb 27: onsuccess: #457: 1: Success after binutils/gcc/linux/gli [...] new 2e206d84f0 28: onsuccess: #458: 1: Success after binutils/gcc/linux/gli [...] new b445c488ba 29: onsuccess: #459: 1: Success after binutils/gcc/linux/gli [...] new 157b8ee54f 30: onsuccess: #460: 1: Success after binutils/gcc/linux/gdb [...] new a25455e6db 31: onsuccess: #461: 1: Success after binutils/gcc/linux/gli [...] new f46cdeafa4 32: onsuccess: #462: 1: Success after binutils/gcc/linux/gdb [...] new 3d6e70aff9 33: onsuccess: #463: 1: Success after binutils/gcc/linux/gli [...] new 1208abdf7b 34: onsuccess: #465: 1: Success after binutils: 11 commits new b5fdb93037 35: onsuccess: #467: 1: Success after glibc: 2 commits new a5a1aa8bee 36: onsuccess: #468: 1: Success after v6.0-rc5-25-g3245cb65f [...] new 125fef6857 37: onsuccess: #470: 1: Success after binutils: 3 commits new 1b7f018421 38: onsuccess: #472: 1: Success after glibc-2.36.9000-121-g5 [...] new 0c27f573ea 39: onsuccess: #474: 1: Success after binutils: 8 commits new 3a88b162be 40: onsuccess: #476: 1: Success after linux: 69 commits new 22a6ed323c 41: onsuccess: #477: 1: Success after binutils/gcc/glibc/gdb [...] new 2a53e3a595 42: onsuccess: #478: 1: Success after binutils/gcc/linux/gdb [...] new 0fceb57823 43: onsuccess: #479: 1: Success after binutils/gcc/glibc/gdb [...] new 091f199b6c 44: onsuccess: #480: 1: Success after binutils/gcc/linux/gli [...] new 3ff09fbe14 45: onsuccess: #481: 1: Success after binutils/gcc/linux/gli [...] new ae074104ae 46: onsuccess: #483: 1: Success after binutils/gcc/linux/gli [...] new 38cae9388d 47: onsuccess: #484: 1: Success after binutils/gcc/linux/gdb [...] new 71042832d3 48: onsuccess: #485: 1: Success after binutils/gcc/linux/gdb [...] new 599d90702e 49: onsuccess: #487: 1: Success after binutils: 11 commits new 43081266c9 50: onsuccess: #490: 1: Success after binutils: 6 commits new 5f376f7498 51: onsuccess: #493: 1: Success after binutils: 13 commits new a6fc55d9fc 52: onsuccess: #495: 1: Success after binutils/gcc/linux/gli [...] new f5a2f8521c 53: onsuccess: #496: 1: Success after binutils/gcc/linux/gli [...] new 3c4455ded7 54: onsuccess: #497: 1: Success after binutils/gcc/linux/gli [...] new 8099d1c330 55: onsuccess: #498: 1: Success after binutils/gcc/linux/gdb [...] new 098dd22dd5 56: onsuccess: #499: 1: Success after binutils/gcc/linux/gli [...] new fd79697041 57: onsuccess: #500: 1: Success after binutils/gcc/linux/gli [...] new 219b4c35f5 58: onsuccess: #501: 1: Success after binutils/gcc/linux/gli [...] new 4204fee952 59: onsuccess: #502: 1: Success after binutils/gcc/linux/gli [...] new 993aa584f6 60: onsuccess: #503: 1: Success after binutils/gcc/linux/gli [...] new 27a1dd9b45 61: onsuccess: #504: 1: Success after binutils/gcc/linux/gdb [...] new 4e489074e5 62: onsuccess: #505: 1: Success after binutils/gcc/linux/gli [...] new b41fc39d0d 63: onsuccess: #506: 1: Success after binutils/gcc/linux/gli [...] new d2e6e61bad 64: onsuccess: #507: 1: Success after binutils/gcc/linux/gdb [...] new b350515109 65: onsuccess: #508: 1: Success after binutils/gcc/linux/gli [...] new 09e8061ba0 66: onsuccess: #509: 1: Success after binutils/gcc/linux/gli [...] new 73eb7288d3 67: onsuccess: #510: 1: Success after binutils/gcc/linux/gli [...] new fe580385f1 68: onsuccess: #511: 1: Success after binutils/gcc/linux/gli [...] new 183f733a86 69: onsuccess: #512: 1: Success after binutils/gcc/linux/gdb [...] new 88073d6402 70: onsuccess: #513: 1: Success after binutils/gcc/linux/gli [...] new d5fa9e0ab5 71: onsuccess: #514: 1: Success after binutils/gcc/linux/gli [...] new 6f82b4302d 72: onsuccess: #515: 1: Success after binutils/gcc/gdb: 65 commits new 3655ecc93f 73: onsuccess: #516: 1: Success after binutils/gcc/glibc/gdb [...] new 36e1c9f59e 74: onsuccess: #517: 1: Success after binutils/gcc/linux/gdb [...] new f5f411cffa 75: onsuccess: #518: 1: Success after binutils/gcc/linux/gdb [...] new 84e45e89f4 76: onsuccess: #519: 1: Success after binutils/gcc/linux/gdb [...] new e843e17015 77: onsuccess: #520: 1: Success after binutils/gcc/linux/gli [...] new c1bc76acc5 78: onsuccess: #522: 1: Success after binutils: 10 commits new 588e21b922 79: onsuccess: #523: 1: Success after gcc: 25 commits new be959dc147 80: onsuccess: #524: 1: Success after linux: 9 commits new 3d7411e6ff 81: onsuccess: #525: 1: Success after binutils/gcc/linux/gli [...] new d698806270 82: onsuccess: #526: 1: Success after binutils/gcc/linux/gli [...] new 3f2a8f6f3f 83: onsuccess: #527: 1: Success after binutils/gcc/linux/gli [...] new 27888b0e21 84: onsuccess: #528: 1: Success after binutils/gcc/linux/gli [...] new 46a3bb7bf6 85: onsuccess: #529: 1: Success after binutils/gcc/linux/gli [...] new aa421fce39 86: onsuccess: #532: 1: Success after gcc: 16 commits new 60ef9348ee 87: onsuccess: #533: 1: Success after glibc-2.36.9000-267-gb [...] new 2ed18494a1 88: onsuccess: #534: 1: Success after linux: 12 commits new c8035603f9 89: onsuccess: #536: 1: Success after binutils: 27 commits new c00a61616a 90: onsuccess: #538: 1: Success after glibc: 10 commits new 56f7f122b6 91: onsuccess: #539: 1: Success after linux: 27 commits new 743878ed0c 92: onsuccess: #543: 1: Success after glibc: 4 commits new b2e8d304c0 93: onsuccess: #544: 1: Success after linux: 34 commits new 8568e3b4bd 94: onsuccess: #545: 1: Success after binutils/gcc/linux/gli [...] new e0e8588ea0 95: onsuccess: #546: 1: Success after binutils/gcc/linux/gli [...] new 7781c78219 96: onsuccess: #547: 1: Success after binutils/gcc/linux/gdb [...] new b647bb891f 97: onsuccess: #548: 1: Success after binutils/gcc/linux/gdb [...] new e363d504e0 98: onsuccess: #549: 1: Success after binutils/gcc/linux/gli [...] new ff4d721583 99: onsuccess: #550: 1: Success after binutils/gcc/linux/gli [...] new a35faa2856 100: onsuccess: #551: 1: Success after binutils/gcc/linux/gl [...] new 00db668e4b 101: onsuccess: #552: 1: Success after binutils/gcc/linux/gl [...] new dbf5aa2624 102: onsuccess: #553: 1: Success after binutils/gcc/linux/gd [...] new 8a81096c7b 103: onsuccess: #555: 1: Success after binutils: 4 commits new aac9d58c3c 104: onsuccess: #558: 1: Success after binutils: 3 commits new 3c2e0242f7 105: onsuccess: #560: 1: Success after binutils/gcc/linux/gl [...] new 34ffd07ec8 106: onsuccess: #561: 1: Success after binutils/gcc/linux/gd [...] new c779cd8802 107: onsuccess: #562: 1: Success after binutils/gcc/linux/gd [...] new c7b391b80a 108: onsuccess: #563: 1: Success after binutils/gcc/linux/gl [...] new 3ba952c48f 109: onsuccess: #564: 1: Success after binutils/gcc/linux/gd [...] new 31d581737a 110: onsuccess: #565: 1: Success after binutils/gcc/linux/gd [...] new 7982f8b73d 111: onsuccess: #566: 1: Success after binutils/gcc/linux/gd [...] new c5b23cc442 112: onsuccess: #567: 1: Success after binutils/gcc/linux/gl [...] new 107621823d 113: onsuccess: #568: 1: Success after binutils/gcc/gdb: 47 commits new 0909f569bc 114: onsuccess: #569: 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 (7b5b37d556) \ 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 1720 -> 1676 bytes 02-prepare_abe/console.log.xz | Bin 2720 -> 2728 bytes 03-build_abe-binutils/console.log.xz | Bin 52200 -> 52368 bytes 04-build_abe-gcc/console.log.xz | Bin 235320 -> 234740 bytes 05-clean_sysroot/console.log.xz | Bin 316 -> 316 bytes 06-build_abe-linux/console.log.xz | Bin 8352 -> 8840 bytes 07-build_abe-glibc/console.log.xz | Bin 235456 -> 234692 bytes 08-build_abe-gdb/console.log.xz | Bin 50964 -> 50576 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3824 -> 3816 bytes 10-build_abe-check_gcc/console.log.xz | Bin 3660 -> 2800 bytes 11-check_regression/console.log.xz | Bin 6824 -> 6936 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 26 +- 11-check_regression/mail-body.txt | 77 +- 11-check_regression/results.compare | 58 +- 11-check_regression/results.compare2 | 180 +- 11-check_regression/results.regressions | 58 +- 12-update_baseline/console.log | 38 +- 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 | 79 +- mail/mail-subject.txt | 2 +- manifest.sh | 32 +- results | 58 +- sumfiles/g++.log.xz | Bin 2922656 -> 2912452 bytes sumfiles/g++.sum | 122 +- sumfiles/gcc.log.xz | Bin 2495128 -> 2518156 bytes sumfiles/gcc.sum | 4483 ++++++++++++++++--------------- sumfiles/gfortran.log.xz | Bin 949168 -> 955016 bytes sumfiles/gfortran.sum | 49 +- sumfiles/libatomic.log.xz | Bin 2252 -> 2260 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 229400 -> 228168 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2676 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 460984 -> 467348 bytes sumfiles/libstdc++.sum | 10 +- 42 files changed, 2660 insertions(+), 2652 deletions(-)