This is an automated email from the git hooks/post-receive script.
tcwg-buildslave pushed a change to branch linaro-local/ci/tcwg_gnu_cross_check_gcc/master-arm in repository toolchain/ci/base-artifacts.
discards 9f8c93d7c3 499: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] discards 32cd966df8 498: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 66dea88955 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 651369964c 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0b486c5405 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 06977de817 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 0865d9ed96 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards b5ff1c94cc 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 3e224f42b0 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards 87700aba83 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] discards fcec70cd75 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] discards 6cd6a2d0bf 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] discards 5abf03cf34 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] discards 0ee12a7cb1 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] discards 6ebc9b2468 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] discards 754d6c443d 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] discards 130dff27b7 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] discards fbd17b662d 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] discards c3e5a0e97e 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] discards b4028ef715 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] discards 8f6f5feafe 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] discards a2db9966cf 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] discards 3106c1b121 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] discards 14ac77e362 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] discards ada0640ee2 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] discards 03a6845b86 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] discards 65f6b64120 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] discards 2a17d6c58d 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] discards 1eb191f526 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] discards 3d196196c4 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] discards a2fdbbdfbf 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] discards 02439847b8 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] discards e8119555f6 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] discards 9bc92da3a0 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] discards d0a19419b4 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] discards 51db651e89 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] discards ca4dbdc01d 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] discards ac637ae7a0 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] discards 558fa4f776 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] discards 5a25010b87 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] discards 581381f3c3 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] discards 45d92df135 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] discards 833641e26a 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] discards d5f75f5d33 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] discards 7b52feb0dc 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] discards fddd710d87 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] discards ab5c633bdb 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] discards 017fa0ca03 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] discards 077f735576 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] discards 3392d9876b 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] discards 91dcc209a5 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] discards 8b40e4033e 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] discards 17dd21d746 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] discards 3a0e7aa412 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits discards 7ae66dcece 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] discards fd5c52e48c 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] discards 563926cb04 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] discards 7dceefd1c3 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] discards be0170419d 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] discards 71d17f6929 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] discards 2d2819254a 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] discards 6c717e40cf 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] discards e12a6fdf3e 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] discards f369096ca8 436: onsuccess: #2260: 1: Success after gcc: 7 commits discards b7ebe7d68b 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] discards 110c317325 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] discards 80c82b7dc4 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] discards 20d4ba64cd 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits discards e686b354a1 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] discards b34fe1c078 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] discards 84ebd488fe 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] discards dffe44d45e 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits discards 71f34f1d4d 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] discards 5a917521c6 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] discards f29dc80f76 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] discards f79026a168 424: onsuccess: #2248: 1: Success after gcc: 6 commits discards dae6045e7d 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits discards 8c11a498db 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] discards 1e38807d3b 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] discards 62cfd7d4e9 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits discards 401bbb2f28 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] discards 4d13b75ef6 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits discards 6c0cfc4857 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] discards 49b03674d8 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] discards 0aec68e149 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] discards bcff6a6f22 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] discards 2938aef12f 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] discards bd812f38a6 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] discards 2645eb604c 411: onsuccess: #2232: 1: Success after gcc: 3 commits discards 92f7101508 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] discards 0fe146819e 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] discards 9592a65416 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] discards 5af2a11186 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] discards 77d3ca933c 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] discards cd6afca0e8 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits discards ff4ceae874 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] discards 0dda22a3e8 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] discards 4a27cd39c9 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] discards 3107eb26bb 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] discards fca4153eb4 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] discards 0e99f47ed8 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 3540776ab1 399: onsuccess: #2220: 1: Success after binutils/gcc/linux/g [...] new 06c557946b 400: onsuccess: #2221: 1: Success after binutils/gcc/linux/g [...] new 222ce93e51 401: onsuccess: #2222: 1: Success after binutils/gcc/gdb: 10 [...] new 5285e54ca6 402: onsuccess: #2223: 1: Success after binutils/gcc/gdb: 10 [...] new 3de72b8503 403: onsuccess: #2224: 1: Success after binutils/gcc/linux/g [...] new ea1d60168b 404: onsuccess: #2225: 1: Success after binutils/gcc/gdb: 10 [...] new 18a1e129e3 405: onsuccess: #2226: 1: Success after gcc/glibc: 39 commits new 5db96cd2b8 406: onsuccess: #2227: 1: Success after binutils/linux/glibc [...] new 29779b6d75 407: onsuccess: #2228: 1: Success after binutils/gcc/linux/g [...] new 05d7c5d038 408: onsuccess: #2229: 1: Success after binutils/gcc/gdb: 26 [...] new 7a2889b56b 409: onsuccess: #2230: 1: Success after binutils/gcc/glibc/g [...] new 9f523ef824 410: onsuccess: #2231: 1: Success after binutils/gcc/linux/g [...] new 492238b12f 411: onsuccess: #2232: 1: Success after gcc: 3 commits new 8edbb29d04 412: onsuccess: #2233: 1: Success after binutils/gcc/glibc/g [...] new fdb60d5557 413: onsuccess: #2234: 1: Success after binutils/gcc/linux/g [...] new bd91287835 414: onsuccess: #2235: 1: Success after binutils/gcc/gdb: 13 [...] new 3b345eeca6 415: onsuccess: #2236: 1: Success after binutils/gcc/gdb: 14 [...] new b494bacd34 416: onsuccess: #2237: 1: Success after binutils/gcc/glibc/g [...] new b9cccca302 417: onsuccess: #2238: 1: Success after binutils/gcc/linux/g [...] new f14ed510aa 418: onsuccess: #2239: 1: Success after binutils/gcc/gdb: 5 commits new 8741d1dce2 419: onsuccess: #2243: 1: Success after binutils/gcc/linux/g [...] new 90891326f8 420: onsuccess: #2244: 1: Success after gcc/glibc: 5 commits new c8066c9928 421: onsuccess: #2245: 1: Success after binutils/gcc/glibc/g [...] new 95e12add92 422: onsuccess: #2246: 1: Success after binutils/gcc/linux/g [...] new 2c12f89336 423: onsuccess: #2247: 1: Success after gcc/linux: 8 commits new 932eccc817 424: onsuccess: #2248: 1: Success after gcc: 6 commits new 648e8b60db 425: onsuccess: #2249: 1: Success after binutils/gcc/linux/g [...] new 871f62b462 426: onsuccess: #2250: 1: Success after binutils/linux/gdb: [...] new 44d48f6e68 427: onsuccess: #2251: 1: Success after binutils/gcc/linux/g [...] new 6f9982742a 428: onsuccess: #2252: 1: Success after binutils/gdb: 2 commits new 77c4dc13a0 429: onsuccess: #2253: 1: Success after binutils/gcc/glibc/g [...] new 55f1e9a79f 430: onsuccess: #2254: 1: Success after binutils/gcc/linux/g [...] new 3c50db68ba 431: onsuccess: #2255: 1: Success after binutils/gcc/linux/g [...] new f35f4d345b 432: onsuccess: #2256: 1: Success after binutils/gdb: 10 commits new 436534271d 433: onsuccess: #2257: 1: Success after binutils/gcc/gdb/qem [...] new 71f6803e26 434: onsuccess: #2258: 1: Success after binutils/gcc/linux/g [...] new 93e42503cf 435: onsuccess: #2259: 1: Success after binutils/gcc/linux/g [...] new 1294c09572 436: onsuccess: #2260: 1: Success after gcc: 7 commits new d6732391df 437: onsuccess: #2261: 1: Success after binutils/gcc/glibc/g [...] new bb51abf854 438: onsuccess: #2263: 1: Success after binutils/gcc/linux/g [...] new fcdc97e673 439: onsuccess: #2264: 1: Success after binutils/gcc/gdb: 13 [...] new 055801006c 440: onsuccess: #2265: 1: Success after binutils/gcc/linux/g [...] new 74c74c99b5 441: onsuccess: #2266: 1: Success after binutils/gcc/linux/g [...] new f0511f24b0 442: onsuccess: #3: 1: Success after binutils/gcc/glibc/gdb/ [...] new eb0b5ecbe5 443: onsuccess: #4: 1: Success after binutils/gcc/gdb/qemu: [...] new 3c3caea4b5 444: onsuccess: #5: 1: Success after binutils/gcc/linux/glib [...] new 510d3d9148 445: onsuccess: #6: 1: Success after binutils/gcc/linux/gdb: [...] new 2854d03708 446: onsuccess: #7: 1: Success after binutils/gcc/gdb: 5 commits new 8c49d6575c 447: onsuccess: #8: 1: Success after binutils/gcc/linux/glib [...] new d2d8544bfd 448: onsuccess: #9: 1: Success after binutils/gcc/linux/gdb: [...] new 45579fdfe6 449: onsuccess: #10: 1: Success after binutils/gcc/linux/gli [...] new 92625f9bf1 450: onsuccess: #11: 1: Success after binutils/gcc/linux/gli [...] new 7a5de29289 451: onsuccess: #12: 1: Success after binutils/gcc/linux/gli [...] new 2b9f0f8079 452: onsuccess: #13: 1: Success after binutils/gcc/linux/gli [...] new e8f88e7499 453: onsuccess: #14: 1: Success after binutils/gcc/linux/gdb [...] new a0a5b8cf36 454: onsuccess: #15: 1: Success after binutils/gcc/linux/gdb [...] new 002c1c32c1 455: onsuccess: #16: 1: Success after binutils/gcc/linux/gdb [...] new f10f8302af 456: onsuccess: #17: 1: Success after binutils/gcc/linux/gli [...] new 02a20f3f98 457: onsuccess: #18: 1: Success after binutils/gcc/linux/gli [...] new adf91ab99e 458: onsuccess: #19: 1: Success after binutils/gcc/linux/gli [...] new a04906bc2e 459: onsuccess: #20: 1: Success after binutils/gcc/linux/gdb [...] new 9fb2d7a2f8 460: onsuccess: #21: 1: Success after binutils/gcc/linux/gli [...] new 47bf6b8edc 461: onsuccess: #22: 1: Success after binutils/gcc/linux/gdb [...] new e797ea09dc 462: onsuccess: #23: 1: Success after binutils/gcc/linux/gli [...] new f7a8b36c1a 463: onsuccess: #24: 1: Success after binutils/gcc/linux/gli [...] new afcdb1a19a 464: onsuccess: #25: 1: Success after binutils/gcc/linux/gli [...] new 8dfc1bd1db 465: onsuccess: #26: 1: Success after binutils/gcc/linux/gdb [...] new 466371b8a3 466: onsuccess: #27: 1: Success after binutils/gcc/linux/gdb [...] new 32351cecce 467: onsuccess: #28: 1: Success after binutils/gcc/linux/gdb [...] new a678e1a94b 468: onsuccess: #29: 1: Success after binutils/gcc/linux/gdb [...] new 986a9b7998 469: onsuccess: #30: 1: Success after binutils/gcc/linux/gdb [...] new 1a975bbffb 470: onsuccess: #31: 1: Success after binutils/gcc/linux/gdb [...] new d44539c918 471: onsuccess: #32: 1: Success after binutils/gcc/linux/gli [...] new 0eb7e46d46 472: onsuccess: #33: 1: Success after binutils/gcc/linux/gdb [...] new 7646be5b00 473: onsuccess: #34: 1: Success after binutils/gcc/linux/gdb [...] new 9909d319f5 474: onsuccess: #35: 1: Success after binutils/gcc/linux/gdb [...] new fe325965bb 475: onsuccess: #36: 1: Success after binutils/gcc/linux/gdb [...] new 2560b01466 476: onsuccess: #37: 1: Success after binutils/gcc/linux/gli [...] new 31c704d6b2 477: onsuccess: #39: 1: [TCWG CI] Success after binutils/gcc [...] new 362ec76e7a 478: onsuccess: #40: 1: [TCWG CI] Success after binutils/gcc [...] new fdeb77bac4 479: onsuccess: #41: 1: [TCWG CI] Success after binutils/gcc [...] new c3aaf0e48d 480: onsuccess: #42: 1: [TCWG CI] Success after binutils/gcc [...] new ad59911076 481: onsuccess: #43: 1: [TCWG CI] Success after binutils/gcc [...] new a84922a675 482: onsuccess: #44: 1: [TCWG CI] Success after binutils/gcc [...] new cf63cd43ba 483: onsuccess: #45: 1: [TCWG CI] Success after binutils/gcc [...] new c7c0fe8865 484: onsuccess: #46: 1: [TCWG CI] Success after binutils/gcc [...] new 16049bb915 485: onsuccess: #47: 1: [TCWG CI] Success after binutils/gcc [...] new 7bd31b3cbc 486: onsuccess: #49: 1: [TCWG CI] Success after binutils/gcc [...] new f131d8da0d 487: onsuccess: #50: 1: [TCWG CI] Success after binutils/gcc [...] new f3e553893a 488: onsuccess: #51: 1: [TCWG CI] Success after binutils/gcc [...] new e2aa18c0b1 489: onsuccess: #52: 1: [TCWG CI] Success after binutils/gcc [...] new a3204e57c9 490: onsuccess: #53: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 3cc852b446 491: onsuccess: #54: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new fc605a5e36 492: onsuccess: #55: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 6349792aa6 493: onsuccess: #56: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7ce1f94a00 494: onsuccess: #58: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 54977af4c4 495: onsuccess: #59: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 73851a513b 496: onsuccess: #60: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 04418fd815 497: onsuccess: #64: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new 7f88a3c97f 498: onsuccess: #65: 1: [TCWG CI] https://ci.linaro.org/job/ [...] new d2066e91ed 499: force: #67: 1: [TCWG CI] https://ci.linaro.org/job/tcwg [...] new ffa30e03e7 500: onsuccess: #69: 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 (9f8c93d7c3) \ N -- N -- N refs/heads/linaro-local/ci/tcwg_gnu_cross_check_gcc/mast [...]
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: 00-sumfiles/g++.log.0.xz | Bin 2713668 -> 2661464 bytes 00-sumfiles/gcc.log.0.xz | Bin 2230540 -> 2230976 bytes 00-sumfiles/gcc.log.1.xz | Bin 38308 -> 0 bytes 00-sumfiles/gcc.sum.1 | 1668 ---------------------- 00-sumfiles/gfortran.log.0.xz | Bin 908516 -> 902064 bytes 00-sumfiles/libatomic.log.0.xz | Bin 2284 -> 2280 bytes 00-sumfiles/libatomic.sum.0 | 2 +- 00-sumfiles/libgomp.log.0.xz | Bin 217616 -> 217504 bytes 00-sumfiles/libgomp.sum.0 | 2 +- 00-sumfiles/libitm.log.0.xz | Bin 2688 -> 2692 bytes 00-sumfiles/libitm.sum.0 | 2 +- 00-sumfiles/libstdc++.log.0.xz | Bin 454452 -> 446336 bytes 00-sumfiles/libstdc++.log.1.xz | Bin 0 -> 449040 bytes 00-sumfiles/libstdc++.sum.0 | 6 +- 00-sumfiles/{libstdc++.sum.0 => libstdc++.sum.1} | 13 +- 01-reset_artifacts/console.log.xz | Bin 2240 -> 2096 bytes 02-prepare_abe/console.log.xz | Bin 2448 -> 2420 bytes 03-build_abe-binutils/console.log.xz | Bin 27148 -> 27048 bytes 04-build_abe-stage1/console.log.xz | Bin 89080 -> 89176 bytes 06-build_abe-linux/console.log.xz | Bin 8684 -> 8524 bytes 07-build_abe-glibc/console.log.xz | Bin 231228 -> 232564 bytes 08-build_abe-stage2/console.log.xz | Bin 224640 -> 225980 bytes 09-build_abe-gdb/console.log.xz | Bin 34332 -> 34504 bytes 10-build_abe-qemu/console.log.xz | Bin 29628 -> 30572 bytes 11-build_abe-dejagnu/console.log.xz | Bin 3860 -> 3872 bytes 12-build_abe-check_gcc/console.log.xz | Bin 7720 -> 7732 bytes 12-build_abe-check_gcc/flaky.xfail | 2 +- 13-check_regression/console.log.xz | Bin 2028 -> 1568 bytes 13-check_regression/extra-bisect-params | 1 - 13-check_regression/fails.sum | 6 - 13-check_regression/results.compare | 23 +- 13-check_regression/results.compare2 | 20 +- 13-check_regression/results.regressions | 32 - 14-update_baseline/console.log | 74 +- git/binutils_rev | 2 +- git/gdb_rev | 2 +- git/glibc_rev | 2 +- git/linux_rev | 2 +- git/qemu_rev | 2 +- jenkins/notify.sh | 2 +- mail/check-regression-status.txt | 2 +- mail/results.compare | 23 +- mail/results.regressions | 32 - manifest.sh | 35 +- results | 32 - sumfiles/libatomic.sum | 2 +- sumfiles/libgomp.sum | 2 +- sumfiles/libitm.sum | 2 +- sumfiles/libstdc++.sum | 6 +- sumfiles/xfails.xfail | 2 +- 50 files changed, 112 insertions(+), 1889 deletions(-) delete mode 100644 00-sumfiles/gcc.log.1.xz delete mode 100644 00-sumfiles/gcc.sum.1 create mode 100644 00-sumfiles/libstdc++.log.1.xz copy 00-sumfiles/{libstdc++.sum.0 => libstdc++.sum.1} (99%) delete mode 100644 13-check_regression/extra-bisect-params delete mode 100644 13-check_regression/fails.sum delete mode 100644 13-check_regression/results.regressions delete mode 100644 mail/results.regressions