Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build: Fix issue with test status logging #38799

Merged
merged 2 commits into from
Feb 15, 2019

Conversation

matriv
Copy link
Contributor

@matriv matriv commented Feb 12, 2019

Handle the case of Description being null which is a valid case as
described in the HeartBeatEvent's javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: #28563

Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
@matriv matriv added the :Delivery/Build Build or test infrastructure label Feb 12, 2019
@matriv matriv requested a review from rjernst February 12, 2019 16:55
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

return className.substring(className.lastIndexOf('.') + 1)
private static String simpleName(Description description) {
if (description == null) {
return "<unknown>"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should indicate unknown class, and in the test name we should add unknown test?

Copy link
Contributor Author

@matriv matriv Feb 12, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My thinking is: if the description is null then we cannot know either.
I believe, there is no case that the class is unknown but the method isn't or the opposite.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mean that we should be more explicit with unknown class vs unknown test.

@matriv
Copy link
Contributor Author

matriv commented Feb 14, 2019

@rjernst thx, fixup pushed.

Copy link
Member

@rjernst rjernst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@matriv matriv merged commit f8d86f9 into elastic:master Feb 15, 2019
@matriv matriv deleted the mt/fix-build-logger branch February 15, 2019 11:36
@matriv matriv restored the mt/fix-build-logger branch February 15, 2019 11:37
@matriv matriv deleted the mt/fix-build-logger branch February 15, 2019 11:37
matriv added a commit to matriv/elasticsearch that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
matriv added a commit to matriv/elasticsearch that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
matriv added a commit to matriv/elasticsearch that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
matriv added a commit to matriv/elasticsearch that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
matriv added a commit to matriv/elasticsearch that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
matriv added a commit that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: #28563
Backport: #38799
matriv added a commit to matriv/elasticsearch that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: elastic#28563
matriv added a commit that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: #28563
matriv added a commit that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: #28563
Backport: #38799
matriv added a commit that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: #28563
Backport: #38799
matriv added a commit that referenced this pull request Feb 15, 2019
Handle the case of `Description` being null which is a valid case as
described in the `HeartBeatEvent`'s javadoc, which previously resulted
in exceptions that "pollute" the build output.

Follows: #28563
Backport: #38799
jasontedor added a commit to jasontedor/elasticsearch that referenced this pull request Feb 15, 2019
* elastic/master:
  Avoid double term construction in DfsPhase (elastic#38716)
  Fix typo in DateRange docs (yyy → yyyy) (elastic#38883)
  Introduced class reuses follow parameter code between ShardFollowTasks (elastic#38910)
  Ensure random timestamps are within search boundary (elastic#38753)
  [CI] Muting  method testFollowIndex in IndexFollowingIT
  Update Lucene snapshot repo for 7.0.0-beta1 (elastic#38946)
  SQL: Doc on syntax (identifiers in particular) (elastic#38662)
  Upgrade to Gradle 5.2.1 (elastic#38880)
  Tie break search shard iterator comparisons on cluster alias (elastic#38853)
  Also mmap cfs files for hybridfs (elastic#38940)
  Build: Fix issue with test status logging (elastic#38799)
  Adapt FullClusterRestartIT on master (elastic#38856)
  Fix testAutoFollowing test to use createLeaderIndex() helper method.
  Migrate muted auto follow rolling upgrade test and unmute this test (elastic#38900)
  ShardBulkAction ignore primary response on primary (elastic#38901)
  Recover peers from translog, ignoring soft deletes (elastic#38904)
  Fix NPE on Stale Index in IndicesService (elastic#38891)
  Smarter CCR concurrent file chunk fetching (elastic#38841)
  Fix intermittent failure in ApiKeyIntegTests (elastic#38627)
  re-enable SmokeTestWatcherWithSecurityIT (elastic#38814)
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants