Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
S
swiftshader
  • Project
    • Overview
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 0
    • Issues 0
    • List
    • Board
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Chen Yisong
  • swiftshader
  • Repository

Switch branch/tag
  • swiftshader
  • tests
  • regres
  • git
  • git.go
Find file
BlameHistoryPermalink
  • Ben Clayton's avatar
    Regres: Add workaround for Khronos Gitlab issues · e2f83aa3
    Ben Clayton authored Nov 12, 2019
    It seems that once a change is no longer in the top N most recent changes, the server will start responding `server does not allow request for unadvertised object` when attempting to fetch the specific change by SHA.
    
    To work around this, we need to fetch the branch by name, then checkout the specific change locally. As the Khronos seems to be particularly slow to respond today, I've limited the branch depth to 99, for now. This hopefully will not be a problem as we should typically only be updating to newer changes.
    
    Also bumped the git command timeout to 15 mintutes as this repo can be _really_ slow.
    
    Change-Id: Ie08165a6ca92e79d56bb4d2d5376410f2850a471
    Reviewed-on: https://swiftshader-review.googlesource.com/c/SwiftShader/+/38129Tested-by: 's avatarBen Clayton <bclayton@google.com>
    Reviewed-by: 's avatarNicolas Capens <nicolascapens@google.com>
    e2f83aa3
git.go 6.88 KB
EditWeb IDE
×

Replace git.go

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.