Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
M
mesa_jenkins
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Mesa_CI
  • mesa_jenkins
  • Issues
  • #41

Closed
Open
Opened Sep 17, 2019 by Kenneth Graunke@kwgContributor

icelake-only developer builds

I could use the ability to test Icelake on developer builds. Ideally this would be added to normal developer builds, but that may not be possible yet. In the meantime, Clayton gave me the ability to test Icelake only via a developer build by doing a custom build:

<craftyguy> Kayden: do custom build, for 'build support' use sha e69a3a83a457fe7fa705e5943e9efeb100cfa37b, select 'all-test' project in drop down. you can leave everything else as default

<craftyguy> Kayden: also beware that this will only test ICL, so if there are regressions in other platforms.. they won't be found in this build...

However, this broke within a few days. Now, if I submit a custom job with that build support sha, it doesn't even register a new job in the mesa_custom build list. It doesn't fail, it just silently does absolutely nothing as far as I can tell.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Mesa_CI/mesa_jenkins#41