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

use Files.createTempFile #141

Merged
merged 10 commits into from
Jun 21, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions .github/workflows/slack-alert.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
name: slack-alert

on:
workflow_run:
workflows: [tests]
types: [completed]

jobs:
on-failure:
runs-on: ubuntu-latest
if: ${{ github.event.workflow_run.conclusion == 'failure' }}
steps:
- name: Send Slack Alert
id: slack
uses: slackapi/[email protected]
with:
payload: |
Github Actions ${{ github.event.workflow_run.conclusion }}
Repo: ${{github.event.workflow_run.repository.name }}
Workflow URL: ${{ github.event.workflow_run.html_url }}
env:
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
5 changes: 4 additions & 1 deletion .github/workflows/tests.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,9 @@ on:
branches: [master, stable-*]
pull_request:
branches: [master, stable-*]
schedule:
# Every Sunday, rerun
- cron: "0 12 * * 0"
Comment on lines +8 to +10
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why this re-run? What would the test suite catch when re-run?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I feel like it's often my experience that the CI process for this repo turns out to have some problem when I go to make a change here, and I'd rather be alerted to that proactively rather than when trying to fix something else. Perhaps the CI issues encountered here are indeed not something that would be usefully caught by this; if that's the case then maybe we don't need it.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I see. There definitely seems to be some flakiness involving the docker images. I wonder if it would make more sense to pull the Dockerfile into the repo and have the test suite build its own docker image to then run? I guess that would depend on how long it takes to build the image.


jobs:
tests:
Expand Down Expand Up @@ -64,7 +67,7 @@ jobs:
os: [ubuntu-latest]
java-distribution: [adopt]
java-version: [17]
dockcross-tag: ["20220906-e88a3ce", "20230116-670f7f7"]
dockcross-tag: ["20230116-670f7f7", "20240529-0dade71", "latest"]

steps:
- uses: actions/[email protected]
Expand Down
Loading