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.

Sign up for GitHub

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

Confusing UI in case of automatic retry #272

Open

maruel opened this issue Jul 19, 2016 · 2 comments

Member

maruel commented Jul 19, 2016

Repro:

Schedule task to run with dimensions that make it runnable only on one bot.
Task fails with BOT_DIED after generating stdout.
Task is rescheduled automatically.
Task stays in PENDING state.

Expected:

UI explicitly states what is happening.

Actual:

UI shows the task is in PENDING yet shows stdout. It stays in this state for several minutes. This is very confusing for the user.

Contributor

kjlubick commented Dec 20, 2016

With the new UI, there is a bit more explaining about what is going on with the auto retries: https://chromium-swarm.appspot.com/task?id=332a28c3d025e310&refresh=10

Contributor

kjlubick commented Jan 24, 2017

In the new UI, this can still be a bit confusing: https://chromium-swarm.appspot.com/task?id=33e91f3119745610&refresh=10
The stdout/milo shows up, but pending/cancelled shows up in the request spot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment