Skip to content
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

Add chromium build to CI #80

Closed
juan-lunarg opened this issue Aug 23, 2023 · 4 comments · Fixed by #121
Closed

Add chromium build to CI #80

juan-lunarg opened this issue Aug 23, 2023 · 4 comments · Fixed by #121
Assignees

Comments

@juan-lunarg
Copy link
Contributor

juan-lunarg commented Aug 23, 2023

Avoid issues like this:
#81

@juan-lunarg juan-lunarg self-assigned this Aug 23, 2023
@juan-lunarg
Copy link
Contributor Author

FYI @charles-lunarg / @mikes-lunarg

@juan-lunarg juan-lunarg added the P1 label Sep 6, 2023
@juan-lunarg
Copy link
Contributor Author

juan-lunarg commented Sep 6, 2023

Higher priority since this seems to routinely cause issues:
#94

@christophe-lunarg
Copy link
Contributor

It seems to me that this issue is more a case of warning levels or -WERROR not being high enough on Vulkan-Utility-Libraries by default, so including on developer system, and consistently across our repositories.

Adding chromium to C.I. might solve the issue for chromium but does it really resolves the issue ecosystem wise, I would say no and that increases our C.I. workload and impact our productivity.

@mikes-lunarg
Copy link
Contributor

Happened again #113

juan-lunarg added a commit that referenced this issue Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants