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

broken tests on windows #1140

Open
jabdr opened this issue Aug 24, 2024 · 1 comment
Open

broken tests on windows #1140

jabdr opened this issue Aug 24, 2024 · 1 comment

Comments

@jabdr
Copy link
Contributor

jabdr commented Aug 24, 2024

Description

I tried to compile and run coraza on windows, which obiously failed.

I know that windows is not a supported platform, but I like to contribute patches to improve the situation. Currently, I am able to pass all tests on windows except those requiring go-ftw (which also does not work on windows). I also ran the tests on linux and the changes did not have any negative impact.

IMHO these patches also improve code quality for other platforms, as they mostly fix incorrect behaviour of not properly closed files and expected behaviour of filepath.Clean/path.Join.

I have created several pull requests to make reviewing easier.

Steps to reproduce

  • run windows (or wine?)
  • go run mage.go test

Expected result

all tests pass

Actual result

Some tests fail. Mostly because of filesystem behaviour differences.

PR

#1133 fix: broken TestInspectFile on windows
#1135 fix: broken embedio on windows
#1132 fix: broken TestDirectives SecUploadDir on windows
#1134 fix: broken normalisePath/normalisePathWin on windows
#1137 fix: broken mutlipart processor on windows
#1136 fix: broken TestHardcodedIncludeDirectiveDDOS2 on windows
#1138 fix: broken TestConcurrentWriterSuccess on windows
#1139 fix: broken unclosed files on windows

@fzipi
Copy link
Member

fzipi commented Nov 22, 2024

@jabdr Looks like you did a good job on creating all those PRs. There were some changes, and ideally you could rebase on top of the required branch. Do you want to follow-up with those changes or not interested anymore?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants