GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — mysql test case(test_sql_registry.py) on mac environment is failing due to the container is not starting correctly. · Issue #4128 · feast-dev/feast

mysql test case(test_sql_registry.py) on mac environment is failing due to the container is not starting correctly. #4128

New issue
Copy link
New issue
Copy link
Closed
Closed
mysql test case(test_sql_registry.py) on mac environment is failing due to the container is not starting correctly.#4128
Copy link
Labels
kind/bugpriority/p2wontfixThis will not be worked onThis will not be worked on

Description

@lokeshrangineni
lokeshrangineni
opened on Apr 23, 2024
Issue body actions

Expected Behavior

test_sql_registry.py should pass on mac environment.

Current Behavior

test_sql_registry.py should be able to run on the local mac environment without any issues. Currently these are skipped in integration tests as well.

Here is the error seeing on mac local environment

===================================================================================================== short test summary info ===================================================================================================== ERROR sdk/python/tests/unit/test_sql_registry.py::test_apply_entity_success[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ERROR sdk/python/tests/unit/test_sql_registry.py::test_registry_cache[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ERROR sdk/python/tests/unit/test_sql_registry.py::test_apply_on_demand_feature_view_success[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ERROR sdk/python/tests/unit/test_sql_registry.py::test_apply_feature_view_success[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ERROR sdk/python/tests/unit/test_sql_registry.py::test_modify_feature_views_success[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ERROR sdk/python/tests/unit/test_sql_registry.py::test_update_infra[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ERROR sdk/python/tests/unit/test_sql_registry.py::test_apply_data_source[mysql_registry] - TimeoutError: container did not emit logs satisfying predicate in 60.000 seconds ===================================================================================== 249 passed, 831 warnings, 7 errors in 100.34s (0:01:40) ===================================================================================== make: *** [test-python-unit] Error 1

Steps to reproduce

Just run the tests on mac environment(intel) - run command make test-python-unit on the project root directory.

Specifications

  • Version:
  • Platform:
  • Subsystem:

Possible Solution

Activity

  1. lokeshrangineni
    added
    kind/bug
    priority/p2
    on Apr 23, 2024
  2. lokeshrangineni
    added 6 commits that reference this issue on Apr 23, 2024

    changed the code the way mysql container is initialized. Trying to fi…

    001a2a3

    changed the code the way mysql container is initialized. Trying to fi…

    ed2dd43

    changed the code the way mysql container is initialized. Trying to fi…

    4d43fcd

    changed the code to test mysql container is ready for testing in a mo…

    4a87118

    checking if this fixes the docker issue in macos12

    c6692ee

    changed the code the way mysql container is initialized. Trying to fi…

    f38b96c
  3. lokeshrangineni commented on Apr 24, 2024

    @lokeshrangineni
    lokeshrangineni
    on Apr 24, 2024
    ContributorAuthor
    More actions

    Created the PR to fix the issue on mac local environment - #4140

  4. lokeshrangineni
    added 2 commits that reference this issue on Apr 25, 2024

    changed the code the way mysql container is initialized. Trying to fi…

    7b50658

    changed the code the way mysql container is initialized. Trying to fi…

    d30914b
  5. jeremyary
    added a commit that references this issue on Apr 25, 2024

    fix: Changed the code the way mysql container is initialized. (#4140)

    8b5698f
  6. lokeshrangineni
    added a commit that references this issue on Apr 25, 2024

    fix: Changed the code the way mysql container is initialized. (feast-…

    d089b0b
  7. stale commented on Apr 26, 2025

    @stale
    staleBot
    on Apr 26, 2025 – with Stale
    More actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  8. stale
    added
    wontfixThis will not be worked onThis will not be worked on
    on Apr 26, 2025
  9. stale
    closed this as completedon May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugpriority/p2wontfixThis will not be worked onThis will not be worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.