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.

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

https://ci.nodejs.org/ unreachable #814

Closed
misterdjules opened this issue Jul 24, 2017 · 5 comments
Closed

https://ci.nodejs.org/ unreachable #814

misterdjules opened this issue Jul 24, 2017 · 5 comments

Comments

@misterdjules
Copy link
Contributor

When pointing my browser to https://ci.nodejs.org/, I get a 502 bad gateway error. It's been the case in the past hour.

/cc @nodejs/build
@rvagg
Copy link
Member

rvagg commented Jul 24, 2017

I'm on it

@rvagg
Copy link
Member

rvagg commented Jul 24, 2017

should be good to go now

@misterdjules
Copy link
Contributor Author

Thanks! Some of the history/data for jobs that were running seems to have been lost, but I suspect this is expected?

@rvagg
Copy link
Member

rvagg commented Jul 25, 2017

@misterdjules this is one of the mysteries of Jenkins .. it seems to not flush state very frequently so a crash or restart can lead to blocks of missing data. So my guess is that if it's missing for you then consider it lost.

@misterdjules
Copy link
Contributor Author

Sounds good, thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rvagg @misterdjules