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 c1edb612af7 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] discards 520b3e43172 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] discards 7b491d9efd5 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] discards 7eb9712665f 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] discards 62803b0d67f 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] discards 05c241bbc57 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] discards 9d279b67ed4 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] discards ec76a2fa9f8 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] discards 9865611f4de 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] discards 79078c5c570 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] discards c297ba199b6 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] discards 3b327361daa 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] discards a5e59a79114 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] discards ba926ce1718 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] discards 87a3daa45a1 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] discards f1e9226527c 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] discards f07a12dab22 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] discards 2ac3f4a8561 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] discards 6b31995da1e 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] discards 99f1e167157 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] discards 02b32ae6b8b 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] discards a3d61a59465 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] discards c4ee79c39f8 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] discards 52b224ca48c 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] discards 8b63206aa16 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] discards 048578562fc 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] discards 43f3801aa3e 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] discards 5439aa9d591 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] discards 1e34fc23852 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] discards 07b2aeada7a 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] discards 2b23d8f4710 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] discards fae0ab6ad49 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] discards 0ec188fb440 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] discards b3afc4ff89d 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] discards d3075c433a5 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] discards 61687e59e1b 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] discards 43f02abf0ec 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] discards 94b4ce25120 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] discards 4f043db672a 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] discards 8348e1eebcd 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] discards 0be72f9e1e9 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] discards f242b664f5c 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] discards 19291a64c16 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] discards 02ea7578a7a 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] discards 50fa5df7636 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] discards 4d846718f81 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] discards fcd38c403cb 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] discards 1cdc5e32764 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] discards 0509d063726 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] discards aa18e98dd5f 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] discards 35d37653e7f 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] discards f6b5cb64b51 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] discards c326d94d426 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] discards b52fe8694a3 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] discards fff86ad3fc6 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] discards 14ed8b49713 152: onsuccess: #903: 1: Success after linux: 22 commits discards b7823fb8da3 151: onsuccess: #902: 1: Success after glibc: 8 commits discards b26b7d2af40 150: onsuccess: #900: 1: Success after gcc: 11 commits discards 3d3c4e5a290 149: onsuccess: #899: 1: Success after binutils: 15 commits discards e26b00761dc 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] discards 6ca9b5a16f7 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] discards 1e265b828c4 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] discards 03f50a8eaeb 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits discards 9387779a63e 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] discards 17ed41f531e 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] discards 0a0f46e734d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] discards 7331a0f17de 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] discards e818b98a9bd 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] discards b59bff42b32 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] discards 1eb488d11d5 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] discards f6e84cb42a6 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] discards cced951f8c5 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] discards 29e5df5d335 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] discards 51768127b4c 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] discards f7c0e612154 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] discards 2b56ffee6e9 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] discards 6d66cd5d7b9 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] discards 0f7354cd565 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] discards a956a78a8fe 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 64fe8df773f 128: onsuccess: #876: 1: Success after binutils: 12 commits discards b0cc0cb4476 127: onsuccess: #874: 1: Success after linux: 219 commits discards 73b64b155e4 126: onsuccess: #873: 1: Success after glibc: 2 commits discards c62099716c7 125: onsuccess: #871: 1: Success after binutils: 26 commits discards a4e54355bb6 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] discards 0c32aa5580c 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] discards 5c1d0febbfe 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] discards 5cfe67eb265 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] discards 83bde225dc0 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] discards 7482516918c 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] discards cc3889c8a28 118: onsuccess: #863: 1: Success after linux: 12 commits discards 315e80ebb73 117: onsuccess: #861: 1: Success after binutils: 18 commits discards cc6940615f2 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] discards 83b6471e1f9 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] discards 65df8839be4 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] discards 53c39f66914 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] discards 5f6364a1c17 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] discards 43373473e51 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] discards 3d47694ea3f 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] discards 7b3b413b382 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] discards 26cb4cecdb7 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 8cf8bc7b54a 107: onsuccess: #849: 1: Success after binutils: 5 commits new 80c4d61c04d 107: onsuccess: #849: 1: Success after binutils: 5 commits new 4ee708752f7 108: onsuccess: #850: 1: Success after gcc: 2 commits new b85e9d9b053 109: onsuccess: #852: 1: Success after binutils/gcc/linux/g [...] new 3cf76775669 110: onsuccess: #853: 1: Success after binutils/gcc/linux/g [...] new a34590fb548 111: onsuccess: #854: 1: Success after binutils/gcc/linux/g [...] new d9e9e4c1b66 112: onsuccess: #855: 1: Success after binutils/gcc/linux/g [...] new c770cb5e41d 113: onsuccess: #856: 1: Success after binutils/gcc/linux/g [...] new a8bd582d858 114: onsuccess: #857: 1: Success after binutils/gcc/linux/g [...] new d8f19ef1f1a 115: onsuccess: #858: 1: Success after binutils/gcc/linux/g [...] new 2f119da0303 116: onsuccess: #859: 1: Success after binutils/gcc/linux/g [...] new 682dba515d0 117: onsuccess: #861: 1: Success after binutils: 18 commits new dcd832996d4 118: onsuccess: #863: 1: Success after linux: 12 commits new e60577ceca6 119: onsuccess: #864: 1: Success after binutils/gcc/linux/g [...] new fbc1d7b3a4a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/g [...] new 6e9e7b231fd 121: onsuccess: #866: 1: Success after binutils/gcc/linux/g [...] new 94baa056ae1 122: onsuccess: #867: 1: Success after binutils/gcc/linux/g [...] new 5e693a6575d 123: onsuccess: #868: 1: Success after binutils/gcc/linux/g [...] new 556a4db5026 124: onsuccess: #869: 1: Success after binutils/gcc/linux/g [...] new 9ca88a00201 125: onsuccess: #871: 1: Success after binutils: 26 commits new f7449ccc802 126: onsuccess: #873: 1: Success after glibc: 2 commits new ac3b16d3946 127: onsuccess: #874: 1: Success after linux: 219 commits new f421fdfde60 128: onsuccess: #876: 1: Success after binutils: 12 commits new c48422603c8 129: onsuccess: #878: 1: Success after linux: 3008 commits new e2fdf4df728 130: onsuccess: #879: 1: Success after binutils/gcc/linux/g [...] new 4f4d67e856c 131: onsuccess: #880: 1: Success after binutils/gcc/linux/g [...] new 70535d82cc6 132: onsuccess: #881: 1: Success after binutils/gcc/linux/g [...] new 70edb2c8775 133: onsuccess: #882: 1: Success after binutils/gcc/linux/g [...] new 29eb955344b 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 [...] new b939c926eb3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/g [...] new be4828fc2d9 136: onsuccess: #885: 1: Success after binutils/gcc/linux/g [...] new 3cb2f4d537e 137: onsuccess: #886: 1: Success after binutils/gcc/linux/g [...] new d3d528975f6 138: onsuccess: #887: 1: Success after binutils/gcc/linux/g [...] new 86c10aeeb53 139: onsuccess: #888: 1: Success after binutils/gcc/linux/g [...] new 6af5c9730af 140: onsuccess: #889: 1: Success after binutils/gcc/linux/g [...] new bbada53be19 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 [...] new 08ff2a3043d 142: onsuccess: #891: 1: Success after binutils/gcc/linux/g [...] new a976368e78f 143: onsuccess: #892: 1: Success after binutils/gcc/gdb: 36 [...] new d5095047e13 144: onsuccess: #893: 1: Success after binutils/gcc/gdb: 18 [...] new 673f78adaf4 145: onsuccess: #894: 1: Success after binutils/gcc/gdb: 9 commits new 998badbbb5d 146: onsuccess: #895: 1: Success after binutils/gcc/linux/g [...] new dc24e7e448c 147: onsuccess: #896: 1: Success after binutils/gcc/linux/g [...] new 5e276b11aec 148: onsuccess: #897: 1: Success after binutils/gcc/linux/g [...] new 7f9c912428f 149: onsuccess: #899: 1: Success after binutils: 15 commits new 10d4308e145 150: onsuccess: #900: 1: Success after gcc: 11 commits new 35cb4368848 151: onsuccess: #902: 1: Success after glibc: 8 commits new 9e11bc36a67 152: onsuccess: #903: 1: Success after linux: 22 commits new d02a7ca0373 153: onsuccess: #904: 1: Success after binutils/gcc/linux/g [...] new 68e07f3199a 154: onsuccess: #905: 1: Success after binutils/gcc/glibc/g [...] new 8e24df7a239 155: onsuccess: #906: 1: Success after binutils/gcc/linux/g [...] new 4ba5f57d844 156: onsuccess: #907: 1: Success after binutils/gcc/linux/g [...] new 9e4fb0ea2ac 157: onsuccess: #908: 1: Success after binutils/gcc/linux/g [...] new 8e96538b249 158: onsuccess: #909: 1: Success after binutils/gcc/linux/g [...] new 1042b75bdf0 159: onsuccess: #910: 1: Success after binutils/gcc/linux/g [...] new bd0265e6f6e 160: onsuccess: #911: 1: Success after binutils/gcc/linux/g [...] new d55b71fd96f 161: onsuccess: #912: 1: Success after binutils/gcc/linux/g [...] new cb51f3150bd 162: onsuccess: #913: 1: Success after binutils/gcc/linux/g [...] new 85dabde760e 163: onsuccess: #914: 1: Success after binutils/gcc/linux/g [...] new 582bf73e748 164: onsuccess: #915: 1: Success after binutils/gcc/linux/g [...] new 4bcae613c37 165: onsuccess: #916: 1: Success after binutils/gcc/linux/g [...] new 3f681ffdf85 166: onsuccess: #917: 1: Success after binutils/gcc/linux/g [...] new 88f7c2e34b8 167: onsuccess: #918: 1: Success after binutils/gcc/linux/g [...] new cf872ad424f 168: onsuccess: #919: 1: Success after binutils/gcc/linux/g [...] new 05fb56155f1 169: onsuccess: #920: 1: Success after binutils/gcc/linux/g [...] new d75a2e08885 170: onsuccess: #921: 1: Success after binutils/gcc/linux/g [...] new ead6c46fa7d 171: onsuccess: #922: 1: Success after binutils/gcc/linux/g [...] new ffef902c9d5 172: onsuccess: #923: 1: Success after binutils/gcc/linux/g [...] new f13abde05b7 173: onsuccess: #924: 1: Success after binutils/gcc/linux/g [...] new 86d72b09dbe 174: onsuccess: #925: 1: Success after binutils/gcc/linux/g [...] new dc3a668d209 175: onsuccess: #926: 1: Success after binutils/gcc/linux/g [...] new f899c2d0740 176: onsuccess: #927: 1: Success after binutils/gcc/linux/g [...] new e5cf0a3023c 177: onsuccess: #928: 1: Success after binutils/gcc/linux/g [...] new c5870300964 178: onsuccess: #929: 1: Success after binutils/gcc/linux/g [...] new f35d571fb0b 179: onsuccess: #930: 1: Success after binutils/gcc/linux/g [...] new 51115a38097 180: onsuccess: #931: 1: Success after binutils/gcc/linux/g [...] new 72ee714ccba 181: onsuccess: #932: 1: Success after binutils/gcc/linux/g [...] new 635333e98b1 182: onsuccess: #933: 1: Success after binutils/gcc/linux/g [...] new 17d9d188938 183: onsuccess: #935: 1: Success after binutils/gcc/linux/g [...] new 3744f4531f5 184: onsuccess: #936: 1: Success after binutils/gcc/linux/g [...] new 7773af2a248 185: onsuccess: #937: 1: Success after binutils/gcc/linux/g [...] new a65e3dccc09 186: onsuccess: #938: 1: Success after binutils/gcc/linux/g [...] new 50328aa4990 187: onsuccess: #939: 1: Success after binutils/gcc/linux/g [...] new 1766db7404f 188: onsuccess: #941: 1: Success after binutils/gcc/linux/g [...] new 8189d3a75ed 189: onsuccess: #942: 1: Success after binutils/gcc/gdb: 39 [...] new c727a6b1720 190: onsuccess: #943: 1: Success after binutils/gcc/linux/g [...] new eceb8f915fa 191: onsuccess: #944: 1: Success after binutils/gcc/linux/g [...] new 7b4af2b19b4 192: onsuccess: #945: 1: Success after binutils/gcc/linux/g [...] new e2ddfcf52f0 193: onsuccess: #946: 1: Success after binutils/gcc/linux/g [...] new ca6226a25d2 194: onsuccess: #947: 1: Success after binutils/gcc/linux/g [...] new 3e3f59869f7 195: onsuccess: #948: 1: Success after binutils/gcc/linux/g [...] new 5af05d014e8 196: onsuccess: #1: 1: Success after binutils/gcc/linux/gli [...] new a5104136dc0 197: onsuccess: #2: 1: Success after binutils/gcc/linux/gdb [...] new 2a998382223 198: onsuccess: #3: 1: Success after binutils/gcc/linux/gli [...] new c094471ddcf 199: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb [...] new 86b00755ec4 200: onsuccess: #5: 1: Success after binutils/gcc/linux/gli [...] new 024bb0c3964 201: onsuccess: #6: 1: Success after binutils/gcc/linux/gli [...] new 105722290e8 202: onsuccess: #7: 1: Success after binutils/gcc/linux/gli [...] new 0d164ac32b9 203: onsuccess: #8: 1: Success after binutils/gcc/linux/gli [...] new 02f16bdf1a6 204: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb [...] new dea97f38634 205: onsuccess: #10: 1: Success after binutils/gcc/linux/gd [...] new ceb3d1d8b1d 206: onsuccess: #11: 1: Success after binutils/gcc/linux/gd [...] new 6d3ef0d4725 207: onsuccess: #12: 1: Success after binutils/gcc/linux/gl [...] new 22762dab52e 208: onsuccess: #13: 1: Success after binutils/gcc/linux/gl [...]
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 (c1edb612af7) \ 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 1764 -> 1764 bytes 02-prepare_abe/console.log.xz | Bin 2768 -> 2756 bytes 03-build_abe-binutils/console.log.xz | Bin 39492 -> 38776 bytes 04-build_abe-gcc/console.log.xz | Bin 205728 -> 204500 bytes 06-build_abe-linux/console.log.xz | Bin 9632 -> 10108 bytes 07-build_abe-glibc/console.log.xz | Bin 246336 -> 244148 bytes 08-build_abe-gdb/console.log.xz | Bin 39096 -> 38528 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3816 -> 3752 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2672 -> 3048 bytes 11-check_regression/console.log.xz | Bin 19980 -> 6360 bytes 11-check_regression/results.compare2 | 4719 +-------------------------------- 12-update_baseline/console.log | 42 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 2 +- mail/mail-subject.txt | 2 +- manifest.sh | 38 +- sumfiles/g++.log.xz | Bin 3683476 -> 3705328 bytes sumfiles/g++.sum | 49 +- sumfiles/gcc.log.xz | Bin 3235356 -> 3214652 bytes sumfiles/gcc.sum | 4 +- sumfiles/gfortran.log.xz | Bin 1084840 -> 1082940 bytes sumfiles/gfortran.sum | 2 +- sumfiles/libatomic.log.xz | Bin 2296 -> 2296 bytes sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.log.xz | Bin 235660 -> 235260 bytes sumfiles/libgomp.sum | 2 +- sumfiles/libitm.log.xz | Bin 2684 -> 2684 bytes sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.log.xz | Bin 450336 -> 445704 bytes 35 files changed, 156 insertions(+), 4722 deletions(-)