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.

Sign up for GitHub

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

Jump to bottom

Workflow failure: master #387

Closed
pulumi-bot opened this issue Jun 20, 2024 · 4 comments
Closed

Workflow failure: master #387

pulumi-bot opened this issue Jun 20, 2024 · 4 comments
Assignees
@guineveresaenger
Labels
kind/engineering Work that is not visible to an external user p1 A bug severe enough to be the next item assigned to an engineer resolution/fixed This issue was fixed

Comments

@pulumi-bot
Copy link
Contributor

pulumi-bot commented Jun 20, 2024 •
edited
Loading

Workflow Failure

master has failed. See the list of failures below:
@pulumi-bot pulumi-bot added kind/engineering Work that is not visible to an external user needs-triage Needs attention from the triage team p1 A bug severe enough to be the next item assigned to an engineer labels Jun 20, 2024
@guineveresaenger guineveresaenger self-assigned this Jun 21, 2024
@guineveresaenger guineveresaenger removed the needs-triage Needs attention from the triage team label Jun 21, 2024
@guineveresaenger
Copy link
Contributor

guineveresaenger commented Jun 21, 2024 •
edited
Loading

Summary of progress in root causing this failure so far:

  1. In /testing/ there's a docker-compose.yml that sets up a Splunk host running on localhost:8089. This is a way to run a light-weight, free-of-charge installation of Splunk.
  2. We set up this container in CI to run the admin-saml-groups test.
  3. Ever since Update GitHub Actions workflows. #386 merged, the Node test has been failing with connection reset by peer. The Python tests succeeds.
  4. A local repro of the docker-container with the example program succeeds for Node.

@guineveresaenger guineveresaenger mentioned this issue Jun 21, 2024
Merged
guineveresaenger added a commit that referenced this issue Jun 21, 2024
@guineveresaenger
Revert "Update GitHub Actions workflows." (#391)
d1dcc97 
Reverts #386.

This is a confidence screen to gather more information for
#387. These tests are
unlikely to pass, so I will force merge this revert.
@guineveresaenger
Copy link
Contributor

update: a revert of #391 https://github.com/pulumi/pulumi-splunk/actions/runs/9619236488/job/26535671789 was canceled (GitHub failure?) but before that, it passed the Node test.

conclusion: something about the Docker setup is different.

@guineveresaenger
Copy link
Contributor

update: this seems to have been a flake in GHA? Reverting the revert in https://github.com/pulumi/pulumi-splunk/actions/runs/9620367680 is passing, with no modifications.

@guineveresaenger guineveresaenger added the resolution/fixed This issue was fixed label Jun 21, 2024
@guineveresaenger
Copy link
Contributor

This is magically no longer happening after several days of persistent failures. Closing this for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@guineveresaenger guineveresaenger

Labels
kind/engineering Work that is not visible to an external user p1 A bug severe enough to be the next item assigned to an engineer resolution/fixed This issue was fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@guineveresaenger @pulumi-bot