[
https://issues.apache.org/jira/browse/TEZ-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15957109#comment-15957109
]
TezQA commented on TEZ-3285:
----------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12862087/TEZ-3285.6.patch
against master revision d0b189a.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc warning messages.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 3.0.1) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:red}-1 core tests{color}. The patch failed these unit tests in :
org.apache.tez.test.TestRecovery
Test results:
https://builds.apache.org/job/PreCommit-TEZ-Build/2366//testReport/
Console output: https://builds.apache.org/job/PreCommit-TEZ-Build/2366//console
This message is automatically generated.
> Tez UI: Lock down dependency versions
> -------------------------------------
>
> Key: TEZ-3285
> URL: https://issues.apache.org/jira/browse/TEZ-3285
> Project: Apache Tez
> Issue Type: Bug
> Reporter: Sreenath Somarajapuram
> Assignee: Sreenath Somarajapuram
> Attachments: TEZ-3285.1.patch, TEZ-3285.2.patch, TEZ-3285.3.patch,
> TEZ-3285.4.patch, TEZ-3285.5.patch, TEZ-3285.6.patch,
> TEZ-3285_batch-0.8_1.patch
>
>
> All dependencies of tez-ui is having fixed versions. But the dependencies of
> our dependencies are not. Hence a level down in the dependency tree, the
> build might be looking for the latest packages in every build. This affects
> the reliability of the UI build. This must be fixed in both the package
> managers used by Tez UI - NPM & Bower.
> -NPM:-
> -npm shrinkwrap create a separate JSON from the currently installed packages,
> and ensure that the complete dependency tree is intact across all the build.-
> Yarn:
> Replace NPM with Yarn. Yarn is a package manager developed to solve this
> issue and many more.
> Bower:
> Bower shrinkwrap resolver plugin can be used to lock the dependency versions.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
