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 d583171bf0 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] discards d7208fa6cc 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] discards eceb875977 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] discards 95614f01ca 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] discards 380f097567 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] discards 3473e7cde3 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] discards 637d54cd75 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits discards dfd6952ac7 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] discards 64864aa58a 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] discards ff1f9439a2 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] discards d8ef9304cc 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] discards 65e78c47d4 129: onsuccess: #878: 1: Success after linux: 3008 commits discards 9f41588da7 128: onsuccess: #876: 1: Success after binutils: 12 commits discards 23110c21e9 127: onsuccess: #874: 1: Success after linux: 219 commits discards 6f6fa88aef 126: onsuccess: #873: 1: Success after glibc: 2 commits discards 0726ae72c7 125: onsuccess: #871: 1: Success after binutils: 26 commits discards 3bcf43a7e1 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] discards 8fa96dd6c9 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] discards fc4fe55526 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] discards 17908fe61e 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] discards bca4f80a8a 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] discards d8fdb11c86 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] discards 3b8a2945cd 118: onsuccess: #863: 1: Success after linux: 12 commits discards cecdcf176a 117: onsuccess: #861: 1: Success after binutils: 18 commits discards 7deaf8b27c 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] discards 2e37fbb08d 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] discards 01ad012a4f 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] discards 90ed957369 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] discards 91bba390b4 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] discards a574d64e71 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] discards c43f9a5017 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] discards 67a802747a 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] discards 222ae16508 108: onsuccess: #850: 1: Success after gcc: 2 commits discards 9a896eb39a 107: onsuccess: #849: 1: Success after binutils: 5 commits discards ddebd86d7a 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] discards abcf80fcba 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] discards e1a697de08 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits discards 5c10cf84ac 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits discards a2d082c34e 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] discards 6cc4969af9 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] discards 96b4eccb1c 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] discards b9ff9c5b6e 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] discards eda0c4cbdb 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] discards c0fca66d29 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] discards fa4022eb2a 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] discards a3dbc844a4 95: onsuccess: #835: 1: Success after binutils: 3 commits discards a9aef33567 94: onsuccess: #832: 1: Success after binutils: 5 commits discards b17d6fbd77 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] discards 2cb6b2b3a1 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] discards 2c567dfa38 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] discards 1e27eb0688 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] discards bc5c4da971 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] discards 9f4453743b 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] discards a39f3763e6 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] discards 09d1bd2225 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] discards 95989465bf 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] discards 3d28bb2255 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] discards 40e164fda3 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] discards be4c2db1cb 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] discards 0989032c44 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] discards 0fd0804faa 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] discards 40e3522b71 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] discards 4f9035e15a 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] discards efa9300c80 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] discards c5fe134702 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] discards 2dcf48a339 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] discards 6c48e820fa 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] discards a00d57ba2c 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] discards ddf79d64f5 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] discards e1ff83fa48 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] discards b0c400db57 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] discards 1a2cdd942a 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] discards 7fd01309ea 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] discards 2cac81074d 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] discards 6c9eac002d 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] discards 818f04f770 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] discards 08f92db4cb 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] discards 339dfffa5b 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] discards c1646efa25 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] discards 3ea6fb6b69 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] discards 1ce2e5f872 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] discards 6f1c6f6fad 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] discards 28f3cb22db 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] discards 719c1e34db 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] discards 3338ebaa98 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] discards 9a053dbefd 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] discards 512c4dd924 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] discards ff6a8d82ac 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] discards 54eee30f9a 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] discards a3a528eab2 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] discards 30625937ec 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] discards 036d925d4e 49: onsuccess: #785: 1: Success after binutils: 12 commits discards 4b1f765011 48: onsuccess: #782: 1: Success after binutils: 8 commits discards 3e2668d4ea 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] discards 99e26d7e5f 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] discards 9fb2639757 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] discards b1a906b404 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] discards 543b67a641 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] discards 02ed8f3154 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] discards 704f56df23 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] discards 51aed3b256 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 13831dd73a 40: onsuccess: #773: 1: Success after binutils/gcc/linux/gli [...] new 86b6a8ddab 41: onsuccess: #774: 1: Success after binutils/gcc/linux/gli [...] new 10c737049b 42: onsuccess: #775: 1: Success after binutils/gcc/linux/gli [...] new aa49f8711b 43: onsuccess: #776: 1: Success after binutils/gcc/glibc/gdb [...] new 3a8c427118 44: onsuccess: #777: 1: Success after binutils/gcc/linux/gli [...] new 5dcdd28cd1 45: onsuccess: #778: 1: Success after binutils/gcc/linux/gdb [...] new 348f7cfc6e 46: onsuccess: #779: 1: Success after binutils/gcc/linux/gdb [...] new c7aa23f6c8 47: onsuccess: #780: 1: Success after binutils/gcc/linux/gli [...] new 0025c26a17 48: onsuccess: #782: 1: Success after binutils: 8 commits new 5fd60c4dc7 49: onsuccess: #785: 1: Success after binutils: 12 commits new bed22023a5 50: onsuccess: #787: 1: Success after binutils/gcc/linux/gli [...] new fd1fe5e6a8 51: onsuccess: #788: 1: Success after binutils/gcc/linux/gli [...] new 73059d7073 52: onsuccess: #789: 1: Success after binutils/gcc/linux/gli [...] new 1b3e34b0c2 53: onsuccess: #790: 1: Success after binutils/gcc/linux/gli [...] new fde951f267 54: onsuccess: #791: 1: Success after binutils/gcc/linux/gli [...] new f5bf51178a 55: onsuccess: #792: 1: Success after binutils/gcc/linux/gli [...] new b320c43e38 56: onsuccess: #793: 1: Success after binutils/gcc/linux/gli [...] new 15334b5ae9 57: onsuccess: #794: 1: Success after binutils/gcc/linux/gli [...] new dc926458e0 58: onsuccess: #795: 1: Success after binutils/gcc/linux/gdb [...] new afb67b375b 59: onsuccess: #796: 1: Success after binutils/gcc/linux/gli [...] new 811b047418 60: onsuccess: #797: 1: Success after binutils/gcc/glibc/gdb [...] new 1d1a0ce0a7 61: onsuccess: #798: 1: Success after binutils/gcc/linux/gli [...] new c7af2bdcd1 62: onsuccess: #799: 1: Success after binutils/gcc/linux/gdb [...] new 7ebd579502 63: onsuccess: #800: 1: Success after binutils/gcc/linux/gli [...] new 73c2973c63 64: onsuccess: #801: 1: Success after binutils/gcc/linux/gli [...] new 6c41724080 65: onsuccess: #802: 1: Success after binutils/gcc/linux/gli [...] new 99222aa8df 66: onsuccess: #803: 1: Success after binutils/gcc/linux/gli [...] new bb08907010 67: onsuccess: #804: 1: Success after binutils/gcc/linux/gdb [...] new 8fec567f01 68: onsuccess: #805: 1: Success after binutils/gcc/linux/gli [...] new aa9e5c28b6 69: onsuccess: #806: 1: Success after binutils/gcc/linux/gli [...] new bf40473b79 70: onsuccess: #807: 1: Success after binutils/gcc/linux/gli [...] new d9454f990b 71: onsuccess: #808: 1: Success after binutils/gcc/glibc/gdb [...] new e6ccf067bb 72: onsuccess: #809: 1: Success after binutils/gcc/linux/gli [...] new 17d5c057db 73: onsuccess: #810: 1: Success after binutils/gcc/linux/gdb [...] new 9540134751 74: onsuccess: #811: 1: Success after binutils/gcc/linux/gdb [...] new fc8d5ac74d 75: onsuccess: #812: 1: Success after binutils/gcc/linux/gli [...] new 316220ca02 76: onsuccess: #813: 1: Success after binutils/gcc/linux/gli [...] new bf3e434219 77: onsuccess: #814: 1: Success after binutils/gcc/linux/gli [...] new c74ec7a797 78: onsuccess: #815: 1: Success after binutils/gcc/linux/gli [...] new 3704759ed3 79: onsuccess: #816: 1: Success after binutils/gcc/linux/gli [...] new 0f43ab70ad 80: onsuccess: #817: 1: Success after binutils/gcc/linux/gli [...] new 93be9a5a5c 81: onsuccess: #818: 1: Success after binutils/gcc/linux/gdb [...] new e9dee4ddd4 82: onsuccess: #819: 1: Success after binutils/gcc/linux/gli [...] new 057966f958 83: onsuccess: #820: 1: Success after binutils/gcc/linux/gli [...] new f46a8b716f 84: onsuccess: #821: 1: Success after binutils/gcc/linux/gli [...] new dc55ed843b 85: onsuccess: #822: 1: Success after binutils/gcc/linux/gli [...] new 45e244fc36 86: onsuccess: #823: 1: Success after binutils/gcc/linux/gli [...] new bbb7e51926 87: onsuccess: #824: 1: Success after binutils/gcc/linux/gli [...] new 9403844414 88: onsuccess: #825: 1: Success after binutils/gcc/linux/gdb [...] new bfdcef1712 89: onsuccess: #826: 1: Success after binutils/gcc/linux/gli [...] new 526f518485 90: onsuccess: #827: 1: Success after binutils/gcc/linux/gli [...] new e2f2bd34df 91: onsuccess: #828: 1: Success after binutils/gcc/linux/gli [...] new 84351e89ed 92: onsuccess: #829: 1: Success after binutils/gcc/linux/gli [...] new f37ecde2cc 93: onsuccess: #830: 1: Success after binutils/gcc/linux/gdb [...] new 08e5689093 94: onsuccess: #832: 1: Success after binutils: 5 commits new 21880ad077 95: onsuccess: #835: 1: Success after binutils: 3 commits new 599f5dc6fd 96: onsuccess: #837: 1: Success after binutils/gcc/linux/gli [...] new f7661a4f97 97: onsuccess: #838: 1: Success after binutils/gcc/linux/gdb [...] new 32140ef6bd 98: onsuccess: #839: 1: Success after binutils/gcc/linux/gli [...] new 80ae81bbbc 99: onsuccess: #840: 1: Success after binutils/gcc/linux/gdb [...] new 40171fdc3e 100: onsuccess: #841: 1: Success after binutils/gcc/linux/gd [...] new f034a45e9a 101: onsuccess: #842: 1: Success after binutils/gcc/linux/gd [...] new 0e710a808f 102: onsuccess: #843: 1: Success after binutils/gcc/linux/gl [...] new 49ace43587 103: onsuccess: #844: 1: Success after binutils/gcc/gdb: 52 commits new a17b81562c 104: onsuccess: #845: 1: Success after binutils/gcc/gdb: 64 commits new 89886fb464 105: onsuccess: #846: 1: Success after binutils/gcc/linux/gd [...] new 826df00a12 106: onsuccess: #847: 1: Success after binutils/gcc/linux/gd [...] new 2038b63924 107: onsuccess: #849: 1: Success after binutils: 5 commits new d381e456d5 108: onsuccess: #850: 1: Success after gcc: 2 commits new 292c4a82ea 109: onsuccess: #852: 1: Success after binutils/gcc/linux/gd [...] new 53114692b6 110: onsuccess: #853: 1: Success after binutils/gcc/linux/gl [...] new 37e1efa0fe 111: onsuccess: #854: 1: Success after binutils/gcc/linux/gl [...] new 2f922b6ba5 112: onsuccess: #855: 1: Success after binutils/gcc/linux/gl [...] new 6106d74fd3 113: onsuccess: #856: 1: Success after binutils/gcc/linux/gd [...] new f1e214cfa6 114: onsuccess: #857: 1: Success after binutils/gcc/linux/gl [...] new f727e73f96 115: onsuccess: #858: 1: Success after binutils/gcc/linux/gl [...] new 157f1d05d9 116: onsuccess: #859: 1: Success after binutils/gcc/linux/gd [...] new 292c5dac64 117: onsuccess: #861: 1: Success after binutils: 18 commits new 071bb0b231 118: onsuccess: #863: 1: Success after linux: 12 commits new 11c097cdc8 119: onsuccess: #864: 1: Success after binutils/gcc/linux/gl [...] new 3654d4ce54 120: onsuccess: #865: 1: Success after binutils/gcc/linux/gl [...] new 812352d978 121: onsuccess: #866: 1: Success after binutils/gcc/linux/gl [...] new 9c9a4b241a 122: onsuccess: #867: 1: Success after binutils/gcc/linux/gl [...] new 58f22242cd 123: onsuccess: #868: 1: Success after binutils/gcc/linux/gd [...] new 6274e50acf 124: onsuccess: #869: 1: Success after binutils/gcc/linux/gd [...] new 1e20f9f9ff 125: onsuccess: #871: 1: Success after binutils: 26 commits new fc202f5fc4 126: onsuccess: #873: 1: Success after glibc: 2 commits new ec988a8eac 127: onsuccess: #874: 1: Success after linux: 219 commits new 9242a5cd89 128: onsuccess: #876: 1: Success after binutils: 12 commits new f3905ed345 129: onsuccess: #878: 1: Success after linux: 3008 commits new 3f5b507fee 130: onsuccess: #879: 1: Success after binutils/gcc/linux/gl [...] new b56e2f1d68 131: onsuccess: #880: 1: Success after binutils/gcc/linux/gl [...] new 30bdccf7af 132: onsuccess: #881: 1: Success after binutils/gcc/linux/gl [...] new 7347b8cac3 133: onsuccess: #882: 1: Success after binutils/gcc/linux/gd [...] new 58dfb77eae 134: onsuccess: #883: 1: Success after binutils/gcc/gdb: 14 commits new 0cf820ff57 135: onsuccess: #884: 1: Success after binutils/gcc/linux/gl [...] new fc343278f6 136: onsuccess: #885: 1: Success after binutils/gcc/linux/gl [...] new 6eac8def15 137: onsuccess: #886: 1: Success after binutils/gcc/linux/gl [...] new 874e8d2992 138: onsuccess: #887: 1: Success after binutils/gcc/linux/gl [...] new 725492654e 139: onsuccess: #888: 1: Success after binutils/gcc/linux/gl [...] new 5e98107d42 140: onsuccess: #889: 1: Success after binutils/gcc/linux/gd [...] new 7f748c9f8b 141: onsuccess: #890: 1: Success after binutils/gcc/gdb: 47 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 (d583171bf0) \ 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 1744 -> 1760 bytes 02-prepare_abe/console.log.xz | Bin 2756 -> 2760 bytes 03-build_abe-binutils/console.log.xz | Bin 40596 -> 39856 bytes 04-build_abe-gcc/console.log.xz | Bin 215364 -> 216820 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8540 -> 8560 bytes 07-build_abe-glibc/console.log.xz | Bin 245448 -> 245548 bytes 08-build_abe-gdb/console.log.xz | Bin 39580 -> 39748 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3852 -> 3828 bytes 10-build_abe-check_gcc/console.log.xz | Bin 2460 -> 3284 bytes 11-check_regression/console.log.xz | Bin 6964 -> 6800 bytes 11-check_regression/extra-bisect-params | 2 +- 11-check_regression/fails.sum | 6 +- 11-check_regression/mail-body.txt | 58 +- 11-check_regression/results.compare | 31 +- 11-check_regression/results.compare2 | 65 +- 11-check_regression/results.regressions | 31 +- 12-update_baseline/console.log | 38 +- dashboard/dashboard-generate.sh | 2 +- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- mail/jira-body.txt | 2 +- mail/mail-body.txt | 60 +- mail/mail-subject.txt | 2 +- manifest.sh | 30 +- results | 31 +- sumfiles/g++.log.xz | Bin 3752572 -> 3775616 bytes sumfiles/g++.sum | 148 +- sumfiles/gcc.log.xz | Bin 3302488 -> 3310296 bytes sumfiles/gcc.sum | 4692 +++++++++++++++---------------- sumfiles/gfortran.log.xz | Bin 1072908 -> 1080828 bytes sumfiles/gfortran.sum | 46 +- sumfiles/libatomic.log.xz | Bin 2280 -> 2272 bytes sumfiles/libatomic.sum | 4 +- sumfiles/libgomp.log.xz | Bin 232176 -> 232248 bytes sumfiles/libgomp.sum | 16 +- sumfiles/libitm.log.xz | Bin 2668 -> 2668 bytes sumfiles/libitm.sum | 6 +- sumfiles/libstdc++.log.xz | Bin 452460 -> 462656 bytes sumfiles/libstdc++.sum | 12 +- 41 files changed, 2705 insertions(+), 2583 deletions(-)