https://sourceware.org/bugzilla/show_bug.cgi?id=32491
--- Comment #3 from Thiago Jung Bauermann <thiago.bauermann at linaro dot org> --- (In reply to Sam James from comment #2) > (In reply to Matthias Klose from comment #0) > > it looks like in some cases these succeed, then fail in subsequent runs. > > Given this, and the contents of Jan's commit, I suspect the bisect done by > the CI bot was unreliable. We need to try bisect again in a setup which can > reproduce, with several tries per commit before declaring it good. I reverted the binutils commit that the CI bisected and these compress.exp regressions were fixed. Though if they succeed sometimes I'll try it again and run the testcase a number of times to be sure. Also, I'm in the middle of debugging ld to see if I can figure out what exactly it's complaining about. The error it gives is this: /home/thiago.bauermann/.cache/builds/abe/builds/armv8l-unknown-linux-gnueabihf/armv8l-unknown-linux-gnueabihf/binutils-binutils-gdb.git~master/ld/tmpdir/ld/collect-ld: tmpdir/zlibbegin.o: final close failed: invalid operation collect2: error: ld returned 1 exit status -- You are receiving this mail because: You are on the CC list for the bug.
