[
https://issues.apache.org/jira/browse/HADOOP-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16202523#comment-16202523
]
Steve Loughran edited comment on HADOOP-13514 at 10/12/17 7:51 PM:
-------------------------------------------------------------------
Just tracked this down as the reason my stack traces don't appear no more.
Before: full stack trace on assertion failure, including nested entries.
Enables me to track down the problem through copy and paste into IDE.
After: one line toString value of raised assertion.
{code}
...
Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 129.494 sec
<<< FAILURE! - in org.apache.hadoop.fs.s3a.ITestS3AContractGetFileStatusV1List
testComplexDirActions(org.apache.hadoop.fs.s3a.ITestS3AContractGetFileStatusV1List)
Time elapsed: 92.017 sec <<< ERROR!
org.apache.hadoop.fs.s3a.AWSS3IOException: getFileStatus on
fork-0004/test/testComplexDirActions/dir-0-0002/dir-0-0002-0002/:
com.amazonaws.services.s3.model.AmazonS3Exception: Internal Server Error
(Service: Amazon S3; Status Code: 500; Error Code: 500 Internal Server Error;
Request ID: AFF8F7D8E3CD3A88; S3 Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=),
S3 Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=:500
Internal Server Error: Internal Server Error (Service: Amazon S3; Status Code:
500; Error Code: 500 Internal Server Error; Request ID: AFF8F7D8E3CD3A88; S3
Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=)
Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: Internal Server
Error (Service: Amazon S3; Status Code: 500; Error Code: 500 Internal Server
Error; Request ID: AFF8F7D8E3CD3A88; S3 Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=)
...
Results :
Tests in error:
ITestS3AContractGetFileStatusV1List>AbstractContractGetFileStatusTest.testComplexDirActions:142->AbstractContractGetFileStatusTest.createTestTree:421
» AWSS3IO
Tests run: 473, Failures: 0, Errors: 1, Skipped: 21
{code}
was (Author: [email protected]):
Just tracked this down as the reason my stack traces don't appear no more.
Before: full stack trace on assertion failure, including nested entries.
Enables me to track down the problem through copy and paste into IDE.
After: one line toString value of raised assertion.
{code}
...
Tests run: 18, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 129.494 sec
<<< FAILURE! - in org.apache.hadoop.fs.s3a.ITestS3AContractGetFileStatusV1List
testComplexDirActions(org.apache.hadoop.fs.s3a.ITestS3AContractGetFileStatusV1List)
Time elapsed: 92.017 sec <<< ERROR!
org.apache.hadoop.fs.s3a.AWSS3IOException: getFileStatus on
fork-0004/test/testComplexDirActions/dir-0-0002/dir-0-0002-0002/:
com.amazonaws.services.s3.model.AmazonS3Exception: Internal Server Error
(Service: Amazon S3; Status Code: 500; Error Code: 500 Internal Server Error;
Request ID: AFF8F7D8E3CD3A88; S3 Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=),
S3 Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=:500
Internal Server Error: Internal Server Error (Service: Amazon S3; Status Code:
500; Error Code: 500 Internal Server Error; Request ID: AFF8F7D8E3CD3A88; S3
Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=)
Caused by: com.amazonaws.services.s3.model.AmazonS3Exception: Internal Server
Error (Service: Amazon S3; Status Code: 500; Error Code: 500 Internal Server
Error; Request ID: AFF8F7D8E3CD3A88; S3 Extended Request ID:
U8W07ULDBLuCZWkZsdIkbj87JbceAunvWxvPS6niWl0Hpw96aGB2YttHYamRX7ZosLigip1iKg4=)
...
Results :
Tests in error:
ITestS3AContractGetFileStatusV1List>AbstractContractGetFileStatusTest.testComplexDirActions:142->AbstractContractGetFileStatusTest.createTestTree:421
» AWSS3IO
Tests run: 473, Failures: 0, Errors: 1, Skipped: 21
{code{
> Upgrade maven surefire plugin to 2.19.1
> ---------------------------------------
>
> Key: HADOOP-13514
> URL: https://issues.apache.org/jira/browse/HADOOP-13514
> Project: Hadoop Common
> Issue Type: Improvement
> Components: build
> Affects Versions: 2.8.0
> Reporter: Ewan Higgs
> Assignee: Akira Ajisaka
> Fix For: 3.0.0
>
> Attachments: HADOOP-13514-addendum.01.patch,
> HADOOP-13514-testing.001.patch, HADOOP-13514-testing.002.patch,
> HADOOP-13514-testing.003.patch, HADOOP-13514-testing.004.patch,
> HADOOP-13514.002.patch, HADOOP-13514.003.patch, surefire-2.19.patch
>
>
> A lot of people working on Hadoop don't want to run all the tests when they
> develop; only the bits they're working on. Surefire 2.19 introduced more
> useful test filters which let us run a subset of the tests that brings the
> build time down from 'come back tomorrow' to 'grab a coffee'.
> For instance, if I only care about the S3 adaptor, I might run:
> {code}
> mvn test -Dmaven.javadoc.skip=true -Pdist,native -Djava.awt.headless=true
> \"-Dtest=org.apache.hadoop.fs.*, org.apache.hadoop.hdfs.*,
> org.apache.hadoop.fs.s3a.*\"
> {code}
> We can work around this by specifying the surefire version on the command
> line but it would be better, imo, to just update the default surefire used.
> {code}
> mvn test -Dmaven.javadoc.skip=true -Pdist,native -Djava.awt.headless=true
> \"-Dtest=org.apache.hadoop.fs.*, org.apache.hadoop.hdfs.*,
> org.apache.hadoop.fs.s3a.*\" -Dmaven-surefire-plugin.version=2.19.1
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
