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

Steve Loughran commented on HADOOP-17325:
-----------------------------------------

Side issue: I couldn't do a fully automated git bisect with a run command as 
you can't pass in "mvn clean install -DskipTests && mvn --pl 
hadoop-tools/hadoop-azure test -Dtest=TestBlobMetadata

What do people think about having a script in dev-support/bin we can use here, 
so

{code}
git bisect run dev-support/bin/bisection-test.sh hadoop-tools/hadoop-azure test 
 TestBlobMetadata
{code}

And have the shell script do the right thing. Wouldn't be hard, and it means 
that it'd be a lot easier to find regressions as you could leave your machine 
to work it out for you


> WASB: Test failure in trunk
> ---------------------------
>
>                 Key: HADOOP-17325
>                 URL: https://issues.apache.org/jira/browse/HADOOP-17325
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure, test
>    Affects Versions: 3.3.0
>            Reporter: Sneha Vijayarajan
>            Assignee: Esfandiar Manii
>            Priority: Major
>
> WASB tests are failing in Apache trunk resulting in Yetus run failures for 
> PRs.
>  
> ||Reason||Tests||
> |Failed junit tests|hadoop.fs.azure.TestNativeAzureFileSystemMocked|
> | |hadoop.fs.azure.TestNativeAzureFileSystemConcurrency|
> | |hadoop.fs.azure.TestWasbFsck|
> | |hadoop.fs.azure.TestNativeAzureFileSystemOperationsMocked|
> | |hadoop.fs.azure.TestNativeAzureFileSystemFileNameCheck|
> | |hadoop.fs.azure.TestNativeAzureFileSystemContractMocked|
> | |hadoop.fs.azure.TestOutOfBandAzureBlobOperations|
> | |hadoop.fs.azure.TestBlobMetadata|
> Many PRs are hit by this. Test report link from one of the PRs:
> [https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2368/5/testReport/]
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to