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

workflows: windows: Add chain workflow for windows unit testing #8582

Merged

Conversation

cosmo0920
Copy link
Contributor

Currently, we're using GitHub Actions just for building confirmation on Windows.
This shouldn't sufficient to testing the internal tests.

Because AppVeyor CI tasks are not actively maintained. So, we have motivations to migrate unit test for Windows from AppVeyor to GitHub Actions.

This PR aims to translate and migrate the unit tests from AppVeyor style to GitHub Actions and just add chain workflows after the Windows compilation and uploading artefacts into S3.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • Example configuration file for the change
  • Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Copy link
Contributor

@patrick-stephens patrick-stephens left a comment

Choose a reason for hiding this comment

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

I think we should split the build and test into at least separate steps with an upload in between, ideally though into a separate job for downloading and running the binaries on a clean runner.

.github/workflows/call-windows-unit-tests.yaml Outdated Show resolved Hide resolved
cosmo0920 and others added 6 commits March 27, 2024 17:57
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
In Windows, the newline(\n) characters in internal test data are replaced with \r\n
by git settings: core.autocrlf true.
This settings accicdentally converting the newlines.
This commit handles the converted characters.

Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
Signed-off-by: Patrick Stephens <pat@chronosphere.io>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
patrick-stephens and others added 2 commits March 27, 2024 17:58
Signed-off-by: Pat <patrick.j.k.stephens@gmail.com>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
Signed-off-by: Hiroshi Hatake <hiroshi@chronosphere.io>
@patrick-stephens
Copy link
Contributor

Once green I'll merge

@patrick-stephens patrick-stephens merged commit 20c461a into master Mar 27, 2024
43 of 44 checks passed
@patrick-stephens patrick-stephens deleted the cosmo0920-add-chain-workflow-for-windows-unit-testing branch March 27, 2024 09:45
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.

None yet

2 participants