Skip to content

Track failing tests after go fix ./... changes (PR #7018) #7047

@neo-by-projectdiscovery-dev

Description

@neo-by-projectdiscovery-dev

Summary

This issue tracks test failures that may occur after applying go fix ./... from Go 1.26.0, which converts interface{} to any throughout the codebase. The changes in PR #7018 are syntactic but may expose test issues that need investigation.

Steps to Reproduce

  1. Checkout PR chore: golangci-lint run --fix ./... #7018 branch: dwisiswant0/chore/go-fix
  2. Run make test to execute unit tests
  3. Run integration tests: cd integration_tests && bash run.sh ubuntu-latest
  4. Run functional tests: cd cmd/functional-test && bash run.sh
  5. Run SDK examples: cd examples/simple && go run .
  6. Check CI workflow results for all test jobs

Expected

All tests should pass after the go fix ./... changes:

  • Unit tests (make test)
  • Integration tests
  • Functional tests
  • SDK examples
  • Template validation
  • Race condition tests

Actual

Some tests may be failing after the interface{} to any conversion. This needs investigation to determine:

  1. Which specific tests are failing
  2. Whether failures are related to the syntactic changes
  3. Whether failures are pre-existing issues exposed by the changes

Evidence

Suggested Fix

  1. Run the full test suite locally and in CI to identify specific failures
  2. For each failing test:
    • Determine if the failure is caused by the interface{} to any conversion
    • Check if the failure is a pre-existing issue
    • Fix the test or update the code as needed
  3. Document any tests that need to be skipped temporarily
  4. Update PR chore: golangci-lint run --fix ./... #7018 with test fixes or create follow-up PRs for complex issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions