- 
                Notifications
    You must be signed in to change notification settings 
- Fork 74
          [E2E] Align pytorch/benchmarks/dynamo configs and torchbench dependencies to match what torch-xpu-ops uses
          #5390
        
          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
          
     Closed
      
      
    Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
b6e5d0a    to
    90fd146      
    Compare
  
    Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
| 
 It looks like  
 @kwasd could you take a look? This has P0 priority. | 
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
              
                    anmyachev
  
              
              commented
              
                  
                    Oct 27, 2025 
                  
              
              
            
            
pytorch/benchmarks/dynamo configs to match what torch-xpu-ops usespytorch/benchmarks/dynamo configs and torchbench dependencies to match what torch-xpu-ops uses
      Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
              
                    anmyachev
  
              
              commented
              
                  
                    Oct 28, 2025 
                  
              
              
            
            
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
Signed-off-by: Anatoly Myachev <anatoly.myachev@intel.com>
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Inspired by intel/torch-xpu-ops@779f899
CI:
Cannot access gated repo for url https://huggingface.co/google/gemma-2-2b/resolve/main/config.json. Access to model google/gemma-2-2b is restricted. You must have access to it and be authenticated to access it. Please log in.torchrec_dlrm)Test all models: https://github.com/intel/intel-xpu-backend-for-triton/actions/runs/18856801306 (see summary)
Summary:
Error checking:
meta-llama/Llama-3.2-1Bandgoogle/gemma-2-2bwork locally. Problem with token in CI.CamemBertis not supposed to work according to intel/torch-xpu-ops@779f899. Can be ignored.openai/whisper-tiny (fail_accuracy). There might be a problem with the Triton, but it's a new model and hasn't been tested before (I checked it here: https://github.com/intel/torch-xpu-ops/actions/runs/17338511026/job/49263018812), so it's not a regression and a blocker.sebotnet33ts_256 (fail_accuracy). There might be a problem with the Triton. However, the problem was already present in the previous iteration of validation: https://github.com/intel/torch-xpu-ops/actions/runs/17338511026/job/49263026473#step:18:7802, so it's not a regression and a blocker.functorch_maml_omniglotandmaml_omniglotare fixed in [E2E] Aligntorchbenchdependencies to match whattorch-xpu-opsuses #5398. There was a problem in the environment.convit_base. The error looks like this and is not related to Triton:detectron2_fasterrcnn_r_50_fpnthe problem was already present in the previous iteration of validation: https://github.com/intel/torch-xpu-ops/actions/runs/17329304896/job/49900834883#step:14:41819(eager_1st_run_OOM)worked before, the cause of the breakdown is unknown.