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

discards ea10c5a5c5 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 840605e1a0 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] discards 53498c0fc5 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] discards 6fce410605 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 274be53d03 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards a8acfe1582 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards edb7bf2bcd 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] discards bc65cea118 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 07f2cc3396 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 5be55e8539 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 734d7d80e6 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] discards 4517e1e2d3 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 736e61364a 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards d60076c066 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards 4dff8fd6f6 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards a38e1ff17d 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards 9d5eca028b 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards a29650bad8 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards 462026cf0e 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 7f75f79fa8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] discards c62c9b0a2b 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] discards 7374dc120a 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 43ccd9d35b 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 54f9137a3c 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] discards 6a581a6b48 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 41927e90d9 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] discards 76f7b2ea3d 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards eea0feccdc 127: force: #27: : Failure after baseline build: no new commits discards 41962840f1 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] discards ef85666416 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 017ddf6eb0 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits discards 6a9d0d490e 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] discards a2361a7948 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] discards e26c32fb1b 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards 8ec2d5536f 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] discards 30b380d3b6 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards dec560f05b 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 067f3bd97d 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits discards 0823a15e2c 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] discards 052774f25e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards bf7f3aef90 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 82a12d258b 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] discards 9ff6c36c29 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] discards c7f4a4e369 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 613d1f43e8 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] discards f00bdc406a 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] discards 4836a622c4 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] discards aebfc5b579 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] discards befe3ce298 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] discards e3a45c9bc9 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] discards 575fec0c37 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] discards bcbad1739f 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] discards 3ea0d4d28c 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] discards e5c0d25cf6 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] discards d3612cc239 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits discards 18d75290f0 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] discards 4fdbf4fc14 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] discards 3490eabe48 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] discards 52f9c98f23 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] discards 0fbe107053 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] discards bcb45df58e 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] discards c0abcae656 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] discards 4c3fafbdb3 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] discards c9cb19bac3 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] discards a0ad95b6ef 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] discards 050ee1cfe1 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] discards aa6777b342 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] discards 01b901881e 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] discards c122506a9b 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] discards 832b68b8f3 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] discards 4786223d34 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] discards 5d60e0f8b2 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits discards fc24179aef 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] discards a109139c60 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] discards 83ae4b5d55 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] discards 6f512bb30c 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] discards d9a43afb22 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] discards a0c50803eb 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] discards fad79bcb92 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] discards 6558f3e596 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] discards 36b9b8c1c9 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] discards 788083bee4 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] discards 625067a114 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] discards f69ef3845b 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] discards 5cbbe20f2f 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] discards e068d014d3 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] discards 8c4d674acf 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] discards 3284cf79e9 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] discards 611728d06d 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] discards af21a64858 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] discards 2df2e00018 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] discards 4b0e4149e4 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] discards 60cd1ebbe7 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] discards 6286c6e189 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] discards 0e8caa4974 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] discards d3f2d625f8 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] discards 91acff30ad 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits discards fc30a74c02 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits discards c9c76dfdea 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits discards 2393595b88 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] discards 9159522dab 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new 68df263038 54: onsuccess: #65: 1: Success after binutils/gcc/gdb: 44 commits new b1841a1c15 55: onsuccess: #66: 1: Success after binutils/gcc/linux/gdb: [...] new 0c7d762ba1 56: onsuccess: #67: 1: Success after binutils/gcc/gdb: 36 commits new 25778184cb 57: onsuccess: #68: 1: Success after binutils/gcc/gdb: 18 commits new 640ccab5fe 58: onsuccess: #69: 1: Success after binutils/gcc/gdb: 24 commits new 7aa34b9087 59: onsuccess: #70: 1: Success after binutils/gcc/linux/glib [...] new 41239cb5fd 60: onsuccess: #71: 1: Success after binutils/gcc/linux/gdb: [...] new db74053877 61: onsuccess: #72: 1: Success after binutils/gcc/linux/gdb: [...] new 614468d6b0 62: onsuccess: #74: 1: Success after binutils/gcc/linux/glib [...] new 89bbea0f8a 63: onsuccess: #76: 1: Success after binutils/gcc/linux/glib [...] new 5ab3f2e51c 64: onsuccess: #77: 1: Success after binutils/gcc/glibc/gdb: [...] new 9eb0deb09c 65: onsuccess: #78: 1: Success after binutils/gcc/linux/glib [...] new 2f2c01b2e6 66: onsuccess: #79: 1: Success after binutils/gcc/linux/gdb: [...] new 5359b11468 67: onsuccess: #80: 1: Success after binutils/gcc/linux/glib [...] new 331e565e69 68: onsuccess: #81: 1: Success after binutils/gcc/linux/gdb: [...] new 303ef14f87 69: onsuccess: #82: 1: Success after binutils/gcc/linux/gdb: [...] new e4e9e962a5 70: onsuccess: #83: 1: Success after binutils/gcc/linux/glib [...] new 5ab14927b5 71: onsuccess: #84: 1: Success after binutils/gcc/linux/glib [...] new 2b91489146 72: onsuccess: #85: 1: Success after binutils/gcc/linux/glib [...] new 11c77c04d6 73: onsuccess: #86: 1: Success after binutils/gcc/linux/glib [...] new e45dfede3e 74: onsuccess: #87: 1: Success after binutils/gcc/linux/glib [...] new 2ff376f12f 75: onsuccess: #88: 1: Success after binutils/gcc/linux/glib [...] new 373654c8ce 76: onsuccess: #89: 1: Success after binutils/gcc/linux/gdb: [...] new 05b1b507b7 77: onsuccess: #90: 1: Success after binutils/gcc/linux/gdb: [...] new c4c443385a 78: onsuccess: #91: 1: Success after binutils/gcc/linux/gdb: [...] new 454dcfa884 79: onsuccess: #92: 1: Success after binutils/gcc/linux/gdb: [...] new 2e7aeb6e19 80: onsuccess: #93: 1: Success after binutils/gcc/linux/glib [...] new 6a9a17258a 81: onsuccess: #94: 1: Success after binutils/gcc/linux/glib [...] new 39dd9e8f3a 82: onsuccess: #95: 1: Success after binutils/gcc/linux/gdb: [...] new 4656f19f60 83: onsuccess: #96: 1: Success after binutils/gcc/gdb: 183 commits new edca9b948c 84: onsuccess: #97: 1: Success after binutils/gcc/linux/glib [...] new 6f30745cd2 85: onsuccess: #98: 1: Success after binutils/gcc/linux/gdb: [...] new b9d10954b0 86: onsuccess: #99: 1: Success after binutils/gcc/linux/glib [...] new 8935c03f6a 87: onsuccess: #100: 1: Success after binutils/gcc/linux/gli [...] new 889e2a58ca 88: onsuccess: #101: 1: Success after binutils/gcc/linux/gli [...] new 0525b8af1d 89: onsuccess: #102: 1: Success after binutils/gcc/linux/gli [...] new 9be3c8d91d 90: onsuccess: #103: 1: Success after binutils/gcc/linux/gli [...] new 562f60d14c 91: onsuccess: #104: 1: Success after binutils/gcc/linux/gli [...] new a15f0c1b87 92: onsuccess: #105: 1: Success after binutils/gcc/linux/gli [...] new 6f6f9763f5 93: onsuccess: #106: 1: Success after binutils/gcc/linux/gli [...] new c7061a2a2d 94: onsuccess: #108: 1: Success after binutils/gcc/linux/gli [...] new 2b40aa2a11 95: onsuccess: #109: 1: Success after binutils/gcc/linux/gli [...] new d5fa1b195f 96: onsuccess: #110: 1: Success after binutils/gcc/linux/gdb [...] new d77ca16f99 97: onsuccess: #111: 1: Success after binutils/gcc/linux/gli [...] new 2d72b594a8 98: onsuccess: #112: 1: Success after binutils/gcc/linux/gli [...] new 6d8187dd59 99: onsuccess: #114: 1: Success after binutils/gcc/linux/gli [...] new ecd735c43c 100: onsuccess: #115: 1: Success after binutils/gcc/gdb: 32 commits new 99b5de7151 101: onsuccess: #116: 1: Success after binutils/gcc/linux/gl [...] new cef4f57c46 102: onsuccess: #117: 1: Success after binutils/gcc/linux/gl [...] new a7a08f80d4 103: onsuccess: #118: 1: Success after binutils/gcc/linux/gd [...] new 1fd30647b5 104: onsuccess: #119: 1: Success after binutils/gcc/linux/gl [...] new 238456e2ac 105: onsuccess: #120: 1: Success after binutils/gcc/linux/gl [...] new fd1aa3ad6b 106: onsuccess: #121: 1: Success after binutils/gcc/linux/gl [...] new 43bde4adba 107: onsuccess: #1: 1: Success after binutils/gcc/linux/glib [...] new b7e9dd8cb3 108: onsuccess: #2: 1: Success after binutils/gcc/linux/glib [...] new 46867f819e 109: onsuccess: #3: 1: Success after binutils/gcc/linux/glib [...] new 3b4e35c273 110: onsuccess: #4: 1: Success after binutils/gcc/linux/gdb: [...] new 7a8371153d 111: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 558ed251e0 112: onsuccess: #6: 1: Success after binutils/gcc/linux/glib [...] new 8b9890124f 113: onsuccess: #7: 1: Success after binutils/gcc/linux/gdb: [...] new 4f5b7af083 114: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new 9a760b2e0e 115: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new c501165294 116: onsuccess: #10: 1: Success after binutils/gcc/linux/gdb [...] new 8b593e6ad7 117: onsuccess: #11: 1: Success after gcc/linux: 45 commits new 7171dfa583 118: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new dbb0b32245 119: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new f47a7bac69 120: onsuccess: #14: 1: Success after binutils/gcc/linux/gli [...] new 04ebc0dc7c 121: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new a69c13956e 122: onsuccess: #16: 1: Success after binutils/gcc/linux/gli [...] new e47ad6fa77 123: onsuccess: #17: 1: Success after binutils/gcc/linux/gdb [...] new d083b009a2 124: onsuccess: #18: 1: Success after gcc/linux: 46 commits new 1fee0dda4e 125: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new 4e88ed7485 126: onsuccess: #20: 1: Success after binutils/gcc/linux/gli [...] new bba96cd0ef 127: force: #27: : Failure after baseline build: no new commits new 0d9d99efc7 128: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 871b33b18b 129: onsuccess: #32: 1: Success after binutils/gcc/linux/gdb [...] new 4295540714 130: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 00a1371302 131: onsuccess: #34: 1: Success after binutils/gcc/linux/gli [...] new ed5cdca2ef 132: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new 78dd74651c 133: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 6e32405ceb 134: onsuccess: #37: 1: Success after binutils/gcc/linux/gdb [...] new 4e3657caf8 135: onsuccess: #38: 1: Success after binutils/gcc/linux/gli [...] new 543eae9725 136: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new ab23c8b058 137: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new bfdcbee50e 138: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new 441ee2e8eb 139: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new deb55763b3 140: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new 66e8f934db 141: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new c31d1a66e1 142: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 7a2a23e986 143: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new bdba1a34e3 144: onsuccess: #48: 1: [TCWG CI] Success after binutils/gcc [...] new c6f9ea49d0 145: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new ce0cf31489 146: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new 781060aded 147: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new db96c4c850 148: onsuccess: #53: 1: [TCWG CI] Success after binutils/gcc [...] new d23a270f86 149: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new f10cc2ebfd 150: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 54853b1f76 151: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 9b56920c33 152: force: #64: : [TCWG CI] https://ci.linaro.org/job/tcwg_ [...] new bb93255b7e 153: onsuccess: #65: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 787810f7e9 154: onsuccess: #66: 0: [TCWG CI] https://ci.linaro.org/job/ [...] new 3b22680a8b 155: onsuccess: #67: 1: [TCWG CI] https://ci.linaro.org/job/ [...]

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 (ea10c5a5c5) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_native_fast_check_gd [...]

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 2028 -> 2196 bytes 02-prepare_abe/console.log.xz | Bin 2520 -> 2428 bytes 03-build_abe-binutils/console.log.xz | Bin 35312 -> 35828 bytes 04-build_abe-gcc/console.log.xz | Bin 203788 -> 203380 bytes 05-clean_sysroot/console.log.xz | Bin 312 -> 312 bytes 06-build_abe-linux/console.log.xz | Bin 8484 -> 8288 bytes 07-build_abe-glibc/console.log.xz | Bin 241520 -> 241564 bytes 08-build_abe-gdb/console.log.xz | Bin 34828 -> 35196 bytes 09-build_abe-dejagnu/console.log.xz | Bin 3832 -> 3916 bytes 10-build_abe-check_gdb/console.log.xz | Bin 1712 -> 3760 bytes 10-build_abe-check_gdb/flaky.xfail | 2 +- 11-check_regression/console.log.xz | Bin 548 -> 548 bytes 12-update_baseline/console.log | 40 ++-- git/binutils_rev | 2 +- git/gcc_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- jenkins/notify.sh | 2 +- manifest.sh | 34 +-- results | 2 +- sumfiles/gdb.log.xz | Bin 0 -> 14440 bytes sumfiles/gdb.sum | 409 ++++++++++++++++++++++++++++++++++ sumfiles/xfails.xfail | 0 24 files changed, 454 insertions(+), 45 deletions(-) create mode 100644 sumfiles/gdb.log.xz create mode 100644 sumfiles/gdb.sum create mode 100644 sumfiles/xfails.xfail