Yup, it seems so.
I created:
https://issues.apache.org/jira/browse/BEAM-2379
for the tracking and I gonna take a look waiting Mairbek's feedback.
Thanks !
Regards
JB
On 05/29/2017 06:43 PM, Dan Halperin wrote:
This looks like somewhere the unit tests are inferring a project from the
environment when they should not be doing so.
On Mon, May 29, 2017 at 8:38 AM, Jean-Baptiste Onofré <j...@nanthrax.net>
wrote:
Gonna try to purge my local m2 repo.
Regards
JB
On 05/29/2017 08:05 AM, Jean-Baptiste Onofré wrote:
Hi team,
Since last week, the build is broken due to tests failure on the
GCP/Spanner IO:
java.lang.IllegalArgumentException: A project ID is required for this
service but could not be determined from the builder or the environment.
Please set a project ID using the builder.
However, Jenkins seems OK on this. I checked and I don't see anything
special in the system variables or JVM arguments.
I started a change on the SpannerIO to get the project ID in the code in
order to have the tests OK (fixing SpannerIO write). Depending of the
answers on this e-mail, I will create a pull request.
Do you think it's reasonable ? I don't see anything special in the
READMEr about new prerequisites for SpannerIO.
Does anyone else notice this tests failure ?
Thanks,
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
