Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

[Eric Engestrom]

On Thursday, 2017-11-16 14:20:03 +, Jose Fonseca wrote:
> On 16/11/17 14:08, Jose Fonseca wrote:
> > On 15/11/17 12:20, Eric Engestrom wrote:
> > > On Wednesday, 2017-11-15 10:35:04 +, Jose Fonseca wrote:
> > > > I could post a remark on AppVeyor's forums, but it sounds from the
> > > > logs the issue could be on our (freedesktop.org's) side.
> > > > 
> > > > 
> > > > I've reconfigured AppVeyor to use
> > > > https://anongit.freedesktop.org/git/mesa/mesa.git/ instead of
> > > > git://anongit.freedesktop.org/mesa/mesa .  Perhaps fewer things can go
> > > > wrong when using HTTP.
> > > 
> > > I seem to remember cloning through http was much more cpu intensive,
> > > which was an issue on the fdo servers; I'm not sure we want to do that
> > > for each commit now.
> > > 
> > > We can keep that for a while though, if only to see if it makes
> > > a difference in appveyor.
> > 
> > HTTP doesn't seem to make a difference:
> > 
> >    https://ci.appveyor.com/project/mesa3d/mesa/build/6174
> > 
> > I'll revert to git protocol.
> > 
> > Still no solution for these errors though.
> 
> I just had an idea:  is anongit.fdo an alias to git.fdo, or a separate
> server?

from a quick `dig`, git.fdo is on kemper, while anongit.fdo is on molly

> 
> Could it be the problem here is that whatever is syncing git -> anongit
> leaves the tree temporarily inconsistent?  If so I wonder if anything
> changed recently.

Could be, although git objects should remain valid forever since we
don't rewrite history, so the only thing I could see would be a sync
issue if molly copies the index and starts serving it before the objects
are copied.

fdo admins: is the sync between kemper and molly done via git, or some
external tool like rsync?

Jose, I think making appveyor use github might be a good idea regardless
of the fdo sync issue, as it would offload the per-commit-clone work,
and that's exactly the kind of things CDNs like github are for.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

[Jose Fonseca]

On 16/11/17 14:08, Jose Fonseca wrote:

On 15/11/17 12:20, Eric Engestrom wrote:

On Wednesday, 2017-11-15 10:35:04 +, Jose Fonseca wrote:

I could post a remark on AppVeyor's forums, but it sounds from the
logs the issue could be on our (freedesktop.org's) side.


I've reconfigured AppVeyor to use
https://anongit.freedesktop.org/git/mesa/mesa.git/ instead of
git://anongit.freedesktop.org/mesa/mesa .  Perhaps fewer things can go
wrong when using HTTP.


I seem to remember cloning through http was much more cpu intensive,
which was an issue on the fdo servers; I'm not sure we want to do that
for each commit now.

We can keep that for a while though, if only to see if it makes
a difference in appveyor.


HTTP doesn't seem to make a difference:

   https://ci.appveyor.com/project/mesa3d/mesa/build/6174

I'll revert to git protocol.

Still no solution for these errors though.


I just had an idea:  is anongit.fdo an alias to git.fdo, or a separate 
server?


Could it be the problem here is that whatever is syncing git -> anongit 
leaves the tree temporarily inconsistent?  If so I wonder if anything 
changed recently.


Jose
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

[Jose Fonseca]

On 15/11/17 12:20, Eric Engestrom wrote:

On Wednesday, 2017-11-15 10:35:04 +, Jose Fonseca wrote:

I could post a remark on AppVeyor's forums, but it sounds from the
logs the issue could be on our (freedesktop.org's) side.


I've reconfigured AppVeyor to use
https://anongit.freedesktop.org/git/mesa/mesa.git/ instead of
git://anongit.freedesktop.org/mesa/mesa .  Perhaps fewer things can go
wrong when using HTTP.


I seem to remember cloning through http was much more cpu intensive,
which was an issue on the fdo servers; I'm not sure we want to do that
for each commit now.

We can keep that for a while though, if only to see if it makes
a difference in appveyor.


HTTP doesn't seem to make a difference:

  https://ci.appveyor.com/project/mesa3d/mesa/build/6174

I'll revert to git protocol.

Still no solution for these errors though.

If I no other solution is found, I could switch AppVeyor to use 
https://github.com/mesa3d/mesa mirror instead.  Whatever side of 
AppVeyor<->FDO the problem is, using github should avoid it.


Jose
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

[Eric Engestrom]

On Wednesday, 2017-11-15 10:35:04 +, Jose Fonseca wrote:
> I could post a remark on AppVeyor's forums, but it sounds from the
> logs the issue could be on our (freedesktop.org's) side.
> 
> 
> I've reconfigured AppVeyor to use
> https://anongit.freedesktop.org/git/mesa/mesa.git/ instead of
> git://anongit.freedesktop.org/mesa/mesa .  Perhaps fewer things can go
> wrong when using HTTP.

I seem to remember cloning through http was much more cpu intensive,
which was an issue on the fdo servers; I'm not sure we want to do that
for each commit now.

We can keep that for a while though, if only to see if it makes
a difference in appveyor.

> 
> 
> Jose
> 
> 
> From: mesa-dev <mesa-dev-boun...@lists.freedesktop.org> on behalf of Roland 
> Scheidegger <srol...@vmware.com>
> Sent: Wednesday, November 15, 2017 02:27
> To: mesa-dev@lists.freedesktop.org
> Subject: Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed
> 
> Does someone know what's going on with that?
> 
> Build started
> git clone -q --depth=100 --branch=master
> git://anongit.freedesktop.org/mesa/mesa C:\projects\mesa
> remote: fatal: unable to read 7a5d62c8e87c50bacaf697e05230ba49a71a0129
> 
> remote: aborting due to possible repository corruption on the remote side.
> fatal: early EOF
> fatal: index-pack failed
> Command exited with code 128
> 
> I mean there were failures like this before. But now since a couple of
> days, this seems to happen at least daily, which is quite annoying.
> 
> Roland
> 
> Am 15.11.2017 um 03:19 schrieb AppVeyor:
> >
> >   Build mesa 6163 failed
> >   <https://ci.appveyor.com/project/mesa3d/mesa/build/6163>
> >
> > Commit 65123ee62c by Roland Scheidegger <mailto:srol...@vmware.com> on
> > 11/9/2017 6:53 PM:
> > r600: set the number type correctly for float rts in cb setup\n\nFloat
> > rts were always set as unorm instead of float.\nNot sure of the
> > consequences, but at least it looks like the blend clamp\nwould have
> > been enabled, which is against the rules (only eg really bothered\nto
> > even attempt to specify this correctly, r600 always used clamp
> > anyway).\nAlbeit r600 (not r700) setup still looks bugged to me due to
> > never setting\nBLEND_FLOAT32 which must be set according to docs...\nNot
> > sure if the hw really cares, no piglit change (on
> > eg/juniper).\n\nReviewed-by: Dave Airlie <airl...@redhat.com>
> >
> > Configure your notification preferences
> > <https://ci.appveyor.com/notifications>
> >
> >
> >
> > ___
> > 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

Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

[Jose Fonseca]

I could post a remark on AppVeyor's forums, but it sounds from the logs the 
issue could be on our (freedesktop.org's) side.


I've reconfigured AppVeyor to use 
https://anongit.freedesktop.org/git/mesa/mesa.git/ instead of 
git://anongit.freedesktop.org/mesa/mesa .  Perhaps fewer things can go wrong 
when using HTTP.


Jose


From: mesa-dev <mesa-dev-boun...@lists.freedesktop.org> on behalf of Roland 
Scheidegger <srol...@vmware.com>
Sent: Wednesday, November 15, 2017 02:27
To: mesa-dev@lists.freedesktop.org
Subject: Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

Does someone know what's going on with that?

Build started
git clone -q --depth=100 --branch=master
git://anongit.freedesktop.org/mesa/mesa C:\projects\mesa
remote: fatal: unable to read 7a5d62c8e87c50bacaf697e05230ba49a71a0129

remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
Command exited with code 128

I mean there were failures like this before. But now since a couple of
days, this seems to happen at least daily, which is quite annoying.

Roland

Am 15.11.2017 um 03:19 schrieb AppVeyor:
>
>   Build mesa 6163 failed
>   <https://ci.appveyor.com/project/mesa3d/mesa/build/6163>
>
> Commit 65123ee62c by Roland Scheidegger <mailto:srol...@vmware.com> on
> 11/9/2017 6:53 PM:
> r600: set the number type correctly for float rts in cb setup\n\nFloat
> rts were always set as unorm instead of float.\nNot sure of the
> consequences, but at least it looks like the blend clamp\nwould have
> been enabled, which is against the rules (only eg really bothered\nto
> even attempt to specify this correctly, r600 always used clamp
> anyway).\nAlbeit r600 (not r700) setup still looks bugged to me due to
> never setting\nBLEND_FLOAT32 which must be set according to docs...\nNot
> sure if the hw really cares, no piglit change (on
> eg/juniper).\n\nReviewed-by: Dave Airlie <airl...@redhat.com>
>
> Configure your notification preferences
> <https://ci.appveyor.com/notifications>
>
>
>
> ___
> 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

Re: [Mesa-dev] [AppVeyor] mesa master #6163 failed

[Roland Scheidegger]

Does someone know what's going on with that?

Build started
git clone -q --depth=100 --branch=master
git://anongit.freedesktop.org/mesa/mesa C:\projects\mesa
remote: fatal: unable to read 7a5d62c8e87c50bacaf697e05230ba49a71a0129

remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed
Command exited with code 128

I mean there were failures like this before. But now since a couple of
days, this seems to happen at least daily, which is quite annoying.

Roland

Am 15.11.2017 um 03:19 schrieb AppVeyor:
> 
>   Build mesa 6163 failed
>   
> 
> Commit 65123ee62c by Roland Scheidegger  on
> 11/9/2017 6:53 PM:
> r600: set the number type correctly for float rts in cb setup\n\nFloat
> rts were always set as unorm instead of float.\nNot sure of the
> consequences, but at least it looks like the blend clamp\nwould have
> been enabled, which is against the rules (only eg really bothered\nto
> even attempt to specify this correctly, r600 always used clamp
> anyway).\nAlbeit r600 (not r700) setup still looks bugged to me due to
> never setting\nBLEND_FLOAT32 which must be set according to docs...\nNot
> sure if the hw really cares, no piglit change (on
> eg/juniper).\n\nReviewed-by: Dave Airlie 
> 
> 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] [AppVeyor] mesa master #6163 failed

[AppVeyor]

Build mesa 6163 failed


Commit 65123ee62c by Roland Scheidegger on 11/9/2017 6:53 PM:

r600: set the number type correctly for float rts in cb setup\n\nFloat rts were always set as unorm instead of float.\nNot sure of the consequences, but at least it looks like the blend clamp\nwould have been enabled, which is against the rules (only eg really bothered\nto even attempt to specify this correctly, r600 always used clamp anyway).\nAlbeit r600 (not r700) setup still looks bugged to me due to never setting\nBLEND_FLOAT32 which must be set according to docs...\nNot sure if the hw really cares, no piglit change (on eg/juniper).\n\nReviewed-by: Dave Airlie 


Configure your notification preferences

___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev