[jira] [Commented] (REEF-160) Fail-fast generating code with wrong protoc version

["Tae-Geon Um (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/REEF-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323778#comment-14323778 ] 

Tae-Geon Um commented on REEF-160:
----------------------------------

More details: 
 - We’ve got stalling builds whenever they run on ubuntu-3 machine. Here are the stalling builds list \[1\]. (you can see the ubuntu-3 label at the top-right corner of the website of the links)   
- In this builds, we’ve got the following error: 
{code}
java.lang.UnsupportedOperationException: This is supposed to be overridden by subclasses.
{code}
The problem is that ubuntu-3 machine has protobuf-2.4.1, not protobuf-2.5.0. This is why we’ve got some protoc errors on ubuntu-3. 
- Apache Infra Build Platform Team says that ubuntu-3 runs on 12.04 LTS and the protoc version is the newest available for that platform \[2\]. They just recommend not using ubuntu-3 machine if we want to use protoc-2.5.0. So I just removed ubuntu-3 machine from the list of our building machines.

I agree with Brian that we need to check the version of protoc during the build. It looks like HBASE already did \[2\].


\[1\]: 
https://builds.apache.org/job/Reef-pull-request-ubuntu/267/
https://builds.apache.org/job/Reef-pull-request-ubuntu/260/
https://builds.apache.org/job/Reef-pull-request-ubuntu/253/
https://builds.apache.org/job/Reef-pull-request-ubuntu/250/

\[2\]: https://issues.apache.org/jira/browse/BUILDS-45?jql=project%20%3D%20BUILDS%20AND%20text%20~%20protobuf

> Fail-fast generating code with wrong protoc version
> ---------------------------------------------------
>
>                 Key: REEF-160
>                 URL: https://issues.apache.org/jira/browse/REEF-160
>             Project: REEF
>          Issue Type: Bug
>            Reporter: Brian Cho
>            Assignee: Brian Cho
>
> We've recently had trouble with the Ubuntu builds. It turns out that this was because protoc 2.4.1 was being used on one of the servers. What made it difficult to track down, is that the compilation succeeds. Errors only show up while running tests.
> ([~taegeonum] will probably have a more detailed writeup on the particular problem soon.)
> We can probably do some maven hacking to check the version of protoc during the build. I'll take a look.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)