untagged-c9c414c3fef9899c8809: Try cibuildhweel

Change-Id: I7ca6e1341b5faf5026163c80e16f5daff3606524

untagged-90dab48ae3570f775356: Try cibuildhweel

Change-Id: I7ca6e1341b5faf5026163c80e16f5daff3606524

untagged-12f1d790f3643a3a144e: Try cibuildhweel

Change-Id: I7ca6e1341b5faf5026163c80e16f5daff3606524

untagged-84c9ac82dc460cd4b6f2: Redid tokens

Change-Id: I3e489ebec4dcc1b04fe50cdf25f7a088e3eb45c2

untagged-7113abbf3c5f6aac5dcd: Remove sudo

Change-Id: Ie0c73b4c57868e9de460d2ce2aff0f1e94ce03fe

untagged-32d9ab24829f3f33731d: PYCBC-628: Produce ManyLinux builds

Only build 3.5-9

Explicit version list

Use regex to validate extant Pythons
More detailed info on LCB_VERSION found
Do auditwheel

Change-Id: I3e84b00bb05942ca9449f188e06782fc5fb4af04

untagged-038417dac8a6669c3111: Disable not working

Change-Id: I2bf6affd43d10a0448c4d04eae14336d6e1b11ce

untagged-aa2552a210aae9292b4e: PYCBC-446: Gracefully fail on signal receipt

Motivation
----------
If the Python process is interrupted by a signal,
lcb_wait3 may return before all remaining jobs
have completed/timed out. This can lead to an exception
being thrown after the wait, as normally
this would only return after this point.

We should gracefully handle this scenario.

Changes
-------

Add a field 'check_type' to the Bucket class.

Instead of using pycbc_assert to raise an abort() if there are
remaining operations to complete after lcb_wait has
returned, according to the check_type value, do the following:

PYCBC_CHECK_NONE: don't raise an exception.
PYCBC_CHECK_STRICT: (the default): raise an SDKInternalError
PYCBC_CHECK_FAIL: (for testing): always fail and raise an exception

Results
-------
It is difficult to automatically reproduce this, but as
we are now raising a Python exception rather than an abort(),
as verified by the tests, the end user should be able
to handle this by catching the exception if necessary. Or
they can turn off checking by setting the flag to
PYCBC_CHECK_NONE.

Change-Id: I5497267ba58496c57fe03b040fbc4eeb67fb16bd
Reviewed-on: http://review.couchbase.org/112725
Tested-by: Ellis Breen <[email protected]>
Reviewed-by: Brett Lawson <[email protected]>
Reviewed-by: Sergey Avseyev <[email protected]>
Tested-by: Build Bot <[email protected]>

untagged-85cb2a42b92ce919c661: PYCBC-446: Gracefully fail on signal receipt

Motivation
----------
If the Python process is interrupted by a signal,
lcb_wait3 may return before all remaining jobs
have completed/timed out. This can lead to an exception
being thrown after the wait, as normally
this would only return after this point.

We should gracefully handle this scenario.

Changes
-------

Add a field 'check_type' to the Bucket class.

Instead of using pycbc_assert to raise an abort() if there are
remaining operations to complete after lcb_wait has
returned, according to the check_type value, do the following:

PYCBC_CHECK_NONE: don't raise an exception.
PYCBC_CHECK_STRICT: (the default): raise an SDKInternalError
PYCBC_CHECK_FAIL: (for testing): always fail and raise an exception

Results
-------
It is difficult to automatically reproduce this, but as
we are now raising a Python exception rather than an abort(),
as verified by the tests, the end user should be able
to handle this by catching the exception if necessary. Or
they can turn off checking by setting the flag to
PYCBC_CHECK_NONE.

Change-Id: I5497267ba58496c57fe03b040fbc4eeb67fb16bd
Reviewed-on: http://review.couchbase.org/112725
Tested-by: Ellis Breen <[email protected]>
Reviewed-by: Brett Lawson <[email protected]>
Reviewed-by: Sergey Avseyev <[email protected]>
Tested-by: Build Bot <[email protected]>

untagged-bcbc184c3de3a65f9ea7: PYCBC-446: Gracefully fail on signal receipt

Motivation
----------
If the Python process is interrupted by a signal,
lcb_wait3 may return before all remaining jobs
have completed/timed out. This can lead to an exception
being thrown after the wait, as normally
this would only return after this point.

We should gracefully handle this scenario.

Changes
-------

Add a field 'check_type' to the Bucket class.

Instead of using pycbc_assert to raise an abort() if there are
remaining operations to complete after lcb_wait has
returned, according to the check_type value, do the following:

PYCBC_CHECK_NONE: don't raise an exception.
PYCBC_CHECK_STRICT: (the default): raise an SDKInternalError
PYCBC_CHECK_FAIL: (for testing): always fail and raise an exception

Results
-------
It is difficult to automatically reproduce this, but as
we are now raising a Python exception rather than an abort(),
as verified by the tests, the end user should be able
to handle this by catching the exception if necessary. Or
they can turn off checking by setting the flag to
PYCBC_CHECK_NONE.

Change-Id: I5497267ba58496c57fe03b040fbc4eeb67fb16bd
Reviewed-on: http://review.couchbase.org/112725
Tested-by: Ellis Breen <[email protected]>
Reviewed-by: Brett Lawson <[email protected]>
Reviewed-by: Sergey Avseyev <[email protected]>
Tested-by: Build Bot <[email protected]>