TODO fixes for GPU tests

divyashreepathihalli commented 9 months ago

TODO: Deeplab V3 presets don't work in Keras 2 - https://github.com/sampathweb/keras-cv/blob/86200dcc3884f441f9e648127e8c67c318c57725/keras_cv/models/segmentation/deeplab_v3_plus/deeplab_v3_plus.py#L247 TODO: test_end_to_end_golden_value test in stable diffusion is failing - https://github.com/sampathweb/keras-cv/blob/86200dcc3884f441f9e648127e8c67c318c57725/keras_cv/models/stable_diffusion/stable_diffusion_test.py#L27

y-vectorfield commented 9 months ago

Hello, @sampathweb, @divyashreepathihalli, I will help you to solve this problem.

divyashreepathihalli commented 9 months ago

@y-vectorfield Many thanks!! We really appreciate it. #BugBuster!!

y-vectorfield commented 9 months ago

@divyashreepathihalli , the latest version of Keras CV has the following problem.

Run pypa/gh-action-pypi-publish@release/v1
/usr/bin/docker run --name f7d0d34920e7fe564c92837f8fabb9579665_bcc2f7 --label 83f7d0 --workdir /github/workspace --rm -e "pythonLocation" -e "PKG_CONFIG_PATH" -e "Python_ROOT_DIR" -e "Python2_ROOT_DIR" -e "Python3_ROOT_DIR" -e "LD_LIBRARY_PATH" -e "INPUT_PASSWORD" -e "INPUT_PACKAGES-DIR" -e "INPUT_VERBOSE" -e "INPUT_USER" -e "INPUT_REPOSITORY-URL" -e "INPUT_REPOSITORY_URL" -e "INPUT_PACKAGES_DIR" -e "INPUT_VERIFY-METADATA" -e "INPUT_VERIFY_METADATA" -e "INPUT_SKIP-EXISTING" -e "INPUT_SKIP_EXISTING" -e "INPUT_PRINT-HASH" -e "INPUT_PRINT_HASH" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_ENVIRONMENT" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e "ACTIONS_RESULTS_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/keras-cv/keras-cv":"/github/workspace" 83f7d0:d34920e7fe564c92837f8fabb9579665  "__token__" "" "" "dist/" "" "" "true" ""
Notice: Attempting to perform trusted publishing exchange to retrieve a temporary short-lived API token for authentication against https://upload.pypi.org/legacy/ due to __token__ username with no supplied password field
Error: Trusted publishing exchange failure: 
OpenID Connect token retrieval failed: GitHub: missing or insufficient OIDC token permissions, the ACTIONS_ID_TOKEN_REQUEST_TOKEN environment variable was unset

This generally indicates a workflow configuration error, such as insufficient
permissions. Make sure that your workflow has `id-token: write` configured
at the job level, e.g.:

```yaml
permissions:
  id-token: write

Learn more at https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect#adding-permissions-settings.

divyashreepathihalli commented 9 months ago

@y-vectorfield do you have a repro? I tested the install and import quickly here and it seems to be working - https://colab.research.google.com/drive/1GyawyQ7_CbjyzJrBVChg4ZUtYc_fmFoZ?usp=sharing

keras-team / keras-cv

TODO fixes for GPU tests #2246