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

test: synchronizing json spec #1833

Merged
merged 1 commit into from
Sep 26, 2022
Merged

test: synchronizing json spec #1833

merged 1 commit into from
Sep 26, 2022

Conversation

apmmachine
Copy link
Contributor

What

APM agent specs automatic sync

Why

Changeset

@z1c0 z1c0 self-assigned this Sep 26, 2022
@z1c0 z1c0 requested a review from gregkalapos September 26, 2022 07:52
@z1c0
Copy link
Contributor

z1c0 commented Sep 26, 2022

@gregkalapos the JSON test specs are now synced into our repository.
As discussed, I will create follow-up issues to actually use these test data in our tests once the PR is merged.

Copy link
Contributor

@gregkalapos gregkalapos left a comment

Choose a reason for hiding this comment

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

@gregkalapos the JSON test specs are now synced into our repository.
As discussed, I will create follow-up issues to actually use these test data in our tests once the PR is merged.

Sound good 👍

The failing test is this: #1819 (comment) (super painful stuff, doesn't always fail - anyways I'm looking at it and it's definitely unrelated to this PR, so this is ok to merge)

@apmmachine
Copy link
Contributor Author

💔 Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-09-26T07:50:52.872+0000

  • Duration: 70 min 56 sec

Test stats 🧪

Test Results
Failed 1
Passed 16436
Skipped 154
Total 16591

Test errors 1

Expand to view the tests failures

Initializing / Parallel / Windows .NET Core / Test / ElasticsearchTests.Elastic.Apm.Elasticsearch.Tests.ElasticsearchTests.Elasticsearch_Span_Does_Not_Have_Http_Child_Span – Elastic.Apm.Elasticsearch.Tests.ElasticsearchTests
    Expand to view the error details

     [Test Class Cleanup Failure (Elastic.Apm.Elasticsearch.Tests.ElasticsearchTests)]: System.InvalidOperationException : Testcontainer has not been created. 
    

    Expand to view the stacktrace

     [Test Class Cleanup Failure (Elastic.Apm.Elasticsearch.Tests.ElasticsearchTests)]: System.InvalidOperationException : Testcontainer has not been created.
    Stack Trace:
       at DotNet.Testcontainers.Containers.TestcontainersContainer.ThrowIfContainerHasNotBeenCreated()
       at DotNet.Testcontainers.Containers.TestcontainersContainer.get_Id()
       at DotNet.Testcontainers.Containers.TestcontainersContainer.StopAsync(CancellationToken ct)
       at Elastic.Apm.Elasticsearch.Tests.ElasticsearchFixture.DisposeAsync() in C:\Users\jenkins\workspace\net_apm-agent-dotnet-mbp_PR-1833\apm-agent-dotnet\test\Elastic.Apm.Elasticsearch.Tests\ElasticsearchFixture.cs:line 35 
    

Steps errors 3

Expand to view the steps failures

Test & coverage
  • Took 26 min 10 sec . View more details here
  • Description: .ci/windows/test.bat
Archive the artifacts
  • Took 0 min 0 sec . View more details here
  • Description: [2022-09-26T08:43:00.990Z] Archiving artifacts withAzureCredentials: error hudson.AbortException: s
Error signal
  • Took 0 min 0 sec . View more details here
  • Description: withAzureCredentials: error hudson.AbortException: script returned exit code 1

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • run benchmark tests : Run the benchmark test.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

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.

3 participants