I suspect it's an infrastructure problem. I appeared frequently a while
back, then went away, now's comming again.
I think the consensus is to move this jobs out of fdo into
https://github.com/mesa3d but I got no reply from Daniel Stone, so I'm
not sure how to move that forward.
Jose
On 19/01/18 23:10, Bas Nieuwenhuizen wrote:
Does not seem like a build issue:
Build started
git clone -q --depth=100 --branch=master
git://anongit.freedesktop.org/mesa/mesa C:\projects\mesa
remote: error: Could not read 6bc54a6fc26d022b77e72f7498aa427aa2544062
remote: fatal: bad tree object 6bc54a6fc26d022b77e72f7498aa427aa2544062
remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
Command exited with code 128
Interesting though that it finds a revision when it can't even clone.
On Fri, Jan 19, 2018 at 11:37 PM, AppVeyor <no-re...@appveyor.com> wrote:
Build mesa 6655 failed
Commit 61a790409e by Bas Nieuwenhuizen on 1/16/2018 1:08 AM:
radv: Always re-emit the sample position offset user SGPR.\n\nThe user SGPR
location can change between pipelines, so we need to\nemit it again to the
pottentially changed SGPR index.\n\nReviewed-by: Samuel Pitoiset
<samuel.pitoi...@gmail.com>
Configure your notification preferences
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
_______________________________________________
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev
