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

Jump to bottom

Find out why we get sometimes "Gtk-WARNING **: cannot open display" warnings #7564

Closed
mkustermann opened this issue Dec 21, 2012 · 4 comments
Closed

Find out why we get sometimes "Gtk-WARNING **: cannot open display" warnings #7564

mkustermann opened this issue Dec 21, 2012 · 4 comments
Assignees
@whesse
Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant

Comments

@mkustermann
Copy link
Member

It seems that we get the "Gtk-WARNING **: cannot open display" error quite frequently on DRT runs.

For example:
http://chromegw.corp.google.com/i/client.dart/builders/dart2js-chrome-linux/builds/1994/steps/annotated_steps/logs/stdio

Currently we just rerun the test, but this approach just hides this flake. We need to find out why this happens.
@ricowind
Copy link
Contributor

Removed Area-Test label.
Added Area-Infrastructure label.

@mkustermann
Copy link
Member Author

cc @whesse.
Removed the owner.
Added Triaged label.

@ricowind
Copy link
Contributor

ricowind commented Jun 2, 2015

Added AssumedStale label.

@mkustermann mkustermann added Type-Defect area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant labels Jun 2, 2015
@whesse whesse removed the closed-obsolete Closed as the reported issue is no longer relevant label Jun 21, 2016
@whesse whesse self-assigned this Jun 21, 2016
@whesse
Copy link
Member

whesse commented Jun 21, 2016

This is still assumed to be happening, by the suppression in test_runner.dart. Test that the issue has disappeared by removing the suppression code before closing.

@whesse whesse reopened this Jun 21, 2016
@matanlurey matanlurey added the closed-obsolete Closed as the reported issue is no longer relevant label Jun 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@whesse whesse

Labels
area-infrastructure Use area-infrastructure for SDK infrastructure issues, like continuous integration bot changes. closed-obsolete Closed as the reported issue is no longer relevant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@matanlurey @whesse @ricowind @mkustermann