[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2020-03-12 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Worker Ant  changed:

   What|Removed |Added

 Status|NEW |CLOSED
 Resolution|--- |UPSTREAM
Last Closed||2020-03-12 12:52:34



--- Comment #11 from Worker Ant  ---
This bug is moved to
https://github.com/gluster/project-infrastructure/issues/28, and will be
tracked there from now on. Visit GitHub issues URL for further details

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2019-05-10 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Amar Tumballi  changed:

   What|Removed |Added

   Priority|unspecified |low
 Status|ASSIGNED|NEW
   Severity|unspecified |low



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2019-02-15 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

PnT Account Manager  changed:

   What|Removed |Added

   Assignee|nig...@redhat.com   |b...@gluster.org



-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-10-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670



--- Comment #9 from Prashanth Pai  ---
(In reply to Nigel Babu from comment #8)
> Hey Prashanth, what's the status on this one? How ready are we to get a
> nightly job running? It's okay to fail.

We have nightly job on Centos CI running against glusterfs nightly. That job is
currently broken. I sent a patch to fix it:

https://github.com/gluster/centosci/pull/22

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=7YUsiWoKxv=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-10-07 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Nigel Babu  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|b...@gluster.org|nig...@redhat.com



--- Comment #8 from Nigel Babu  ---
Hey Prashanth, what's the status on this one? How ready are we to get a nightly
job running? It's okay to fail.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=lI0fiVIo4j=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-09-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670



--- Comment #7 from Nigel Babu  ---
Let's get the tests running in any case. I think it's better to have a nightly
job that fails rather than nothing.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=LBcpQ8tcYI=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-09-03 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Prashanth Pai  changed:

   What|Removed |Added

  Flags|needinfo?(p...@redhat.com)  |



--- Comment #6 from Prashanth Pai  ---
(In reply to Niels de Vos from comment #5)
> I think we might need to add a way to do feature detection through new gfapi
> function.
> 
> How about adding this:
> 
> int glfs_supports(glfs_t *fs, enum glfs_feature)
> 
> enum glfs_features {
> GFAPI_READLINK_HAS_FOLLOW = 1,
> GFAPI_GETXATTR_RETURNS_STAT = 2,
> ...
> }
> 
> It can return 1=YES, 0=NO, -1=unknown feature. Any changes in the API can
> then be dynamically checked, making it possible for non-compiled languages
> (like Python) to handle different versions. Some features may be available
> only when a particular option is set in for the volume, by passing the
> glfs_t it would be possible to support these kind of requests as well.

Sounds okay to me

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=m1K4bcqUOr=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-07-25 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Niels de Vos  changed:

   What|Removed |Added

 CC||nde...@redhat.com,
   ||p...@redhat.com
  Flags||needinfo?(p...@redhat.com)



--- Comment #5 from Niels de Vos  ---
I think we might need to add a way to do feature detection through new gfapi
function.

How about adding this:

int glfs_supports(glfs_t *fs, enum glfs_feature)

enum glfs_features {
GFAPI_READLINK_HAS_FOLLOW = 1,
GFAPI_GETXATTR_RETURNS_STAT = 2,
...
}

It can return 1=YES, 0=NO, -1=unknown feature. Any changes in the API can then
be dynamically checked, making it possible for non-compiled languages (like
Python) to handle different versions. Some features may be available only when
a particular option is set in for the volume, by passing the glfs_t it would be
possible to support these kind of requests as well.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=xOWW9a23v7=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-07-20 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670



--- Comment #4 from Prashanth Pai  ---
> I guess that is not an ideal thing to do. Either we have to keep the goal as 
> every release rebase

Every release rebase would be ideal.

> There will be no chance of knowing when we will have 'all the changes' 
> completed.

All the changes planned for a particular release. I think glusterfs release 5
has some API changes planned (that got pushed from 4.1 plan). When all those
API changes are in, we can make libgfapi-python rebase to those changes.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=oQx2xHUzVg=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-07-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Amar Tumballi  changed:

   What|Removed |Added

 CC||atumb...@redhat.com



--- Comment #3 from Amar Tumballi  ---
>  I'm waiting for all API changes in glusterfs to finish so that I can do the 
> corresponding changes in libgfapi-python all at once.

I guess that is not an ideal thing to do. Either we have to keep the goal as
every release rebase, or consumer (in this case, libgfapi-python) will mandate
the version they are compatible. So, even if you run on master, it should fail,
because it is not the version one needs.

There will be no chance of knowing when we will have 'all the changes'
completed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=U2sPy47YcW=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-07-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670



--- Comment #2 from Prashanth Pai  ---
> Is master of libgfapi-python compatible with master of glusterfs now?

Most likely, no it's not. I'll try it out and confirm though. I'm waiting for
all API changes in glusterfs to finish so that I can do the corresponding
changes in libgfapi-python all at once.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=Ab1KddhHB1=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra


[Gluster-infra] [Bug 1562670] Run libgfapi-python tests on Gerrit against glusterfs changes

2018-07-19 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1562670

Nigel Babu  changed:

   What|Removed |Added

 CC||nig...@redhat.com



--- Comment #1 from Nigel Babu  ---
Is master of libgfapi-python compatible with master of glusterfs now?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug 
https://bugzilla.redhat.com/token.cgi?t=ge7jJlVlq8=cc_unsubscribe
___
Gluster-infra mailing list
Gluster-infra@gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-infra