lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From laimis <>
Subject [GitHub] lucenenet pull request: throw a more informative exception to trac...
Date Tue, 30 Dec 2014 01:40:24 GMT
GitHub user laimis opened a pull request:

    throw a more informative exception to track down TeamCity test failures

    TeamCity CI tests show a lot of tests failing locating test artifacts:
    Test(s) failed. System.ArgumentOutOfRangeException : StartIndex cannot be less than zero.
    Parameter name: startIndex
       at System.String.Substring(Int32 startIndex, Int32 length)
       at Lucene.Net.Util.Paths.get_ProjectRootDirectory() in z:\Builds\work\bcdbe6b8cc677a49\src\Lucene.Net.TestFramework\Util\Paths.cs:line
       at Lucene.Net.Util.Paths.ResolveTestArtifactPath(String fileName) in z:\Builds\work\bcdbe6b8cc677a49\src\Lucene.Net.TestFramework\Util\Paths.cs:line
       at Lucene.Net.Util.LineFileDocs..ctor(Random random, String path, Boolean useDocValues)
in z:\Builds\work\bcdbe6b8cc677a49\src\Lucene.Net.TestFramework\Util\LineFileDocs.cs:line
    Hard to say what the issue is as running locally from NUnit or R# in VS does not cause
this issue to appear even though the same code path is triggered.
    Added a better exception that will report what value is returned for assembly location
that might be something that is not expected.

You can merge this pull request into a Git repository by running:

    $ git pull teamcity_test_failures

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #32
commit a57d7201e74ba53784dffb2e18be2e2646618da3
Author: Laimonas Simutis <>
Date:   2014-12-30T01:34:20Z

    throw a more informative exception to track down TeamCity test failures


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message