Skip to content

Periodic windows release test CI failures #736

@anissa111

Description

@anissa111

Logging this so there's a record of how to unstick future tests

See

micromamba list
  C:\Users\runneradmin\micromamba-bin\micromamba.exe list -r C:\Users\runneradmin\micromamba -n import_test
  info     libmamba ****************** Backtrace Start ******************
  debug    libmamba Loading configuration
  trace    libmamba Compute configurable 'create_base'
  trace    libmamba Compute configurable 'no_env'
  trace    libmamba Compute configurable 'no_rc'
  trace    libmamba Compute configurable 'rc_files'
  trace    libmamba Compute configurable 'root_prefix'
  trace    libmamba Get RC files configuration from locations up to HomeDir
  trace    libmamba Configuration found at 'D:\a\_temp\setup-micromamba\.condarc'
  trace    libmamba Update configurable 'no_env'
  trace    libmamba Compute configurable 'envs_dirs'
  trace    libmamba Compute configurable 'file_specs'
  trace    libmamba Compute configurable 'spec_file_env_name'
  trace    libmamba Compute configurable 'env_name'
  trace    libmamba Compute configurable 'use_default_prefix_fallback'
  trace    libmamba Compute configurable 'use_root_prefix_fallback'
  trace    libmamba Compute configurable 'use_target_prefix_fallback'
  trace    libmamba Compute configurable 'target_prefix'
  trace    libmamba Get RC files configuration from locations up to TargetPrefix
  trace    libmamba Configuration found at 'D:\a\_temp\setup-micromamba\.condarc'
  trace    libmamba Update configurable 'no_env'
  trace    libmamba Compute configurable 'relocate_prefix'
  trace    libmamba Compute configurable 'target_prefix_checks'
  error    libmamba No prefix found at: C:\Users\runneradmin\micromamba\envs\import_test
  error    libmamba Environment must first be created with "micromamba create -n {env_name} ..."
  critical libmamba Aborting.
  info     libmamba ****************** Backtrace End ********************
Error: The process 'C:\Users\runneradmin\micromamba-bin\micromamba.exe' failed with exit code 1

I'm not sure why the windows tests are particularly brittle or why the failures are occurring, but since it appears to be a caching issue, we could probably alter the retry environment step to ignore the cached environment to make them less brittle.


To fix the failing tests, run

gh cache delete "release_test-Windows"

and then re-run them

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtestingIssue related to testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions