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

args_width: No such file or directory #249

Open
pwaller opened this issue Dec 10, 2018 · 1 comment
Open

args_width: No such file or directory #249

pwaller opened this issue Dec 10, 2018 · 1 comment

Comments

@pwaller
Copy link
Contributor

pwaller commented Dec 10, 2018

While troubleshooting #689, we found this error message in the logs.

It turns out it goes back to at least Sept 6th. Cause not yet known.

$ sudo ag -l args_w.*such | xargs ls -ltr
-rw-r--r-- 1 jenkins jenkins   25378 Sep  5 15:36 jobs/reconfigureio/jobs/reco-sdaccel/branches/auto/builds/316/51.log
-rw-r--r-- 1 jenkins jenkins   18230 Sep  5 15:47 jobs/reconfigureio/jobs/reco-sdaccel/branches/auto/builds/316/105.log
-rw-r--r-- 1 jenkins jenkins   14860 Sep  5 15:55 jobs/reconfigureio/jobs/reco-sdaccel/branches/auto/builds/316/114.log
-rw-r--r-- 1 jenkins jenkins   17816 Sep  5 16:11 jobs/reconfigureio/jobs/reco-sdaccel/branches/auto/builds/316/115.log
-rw-r--r-- 1 jenkins jenkins   18258 Sep  5 16:46 jobs/reconfigureio/jobs/reco-sdaccel/branches/auto/builds/316/160.log
[many other builds failing]
-rw-r--r-- 1 root    root     202060 Dec  7 16:33 jobs/Reconfigure.io/jobs/reco-sdaccel/branches/PR-242/builds/3/log
-rw-r--r-- 1 root    root     201518 Dec  7 16:38 jobs/Reconfigure.io/jobs/reco-sdaccel/branches/PR-242/builds/4/log
-rw-r--r-- 1 root    root     338757 Dec  7 16:48 jobs/Reconfigure.io/jobs/reco-sdaccel/branches/PR-242/builds/5/log
-rw-r--r-- 1 root    root     202087 Dec  7 17:04 jobs/Reconfigure.io/jobs/reco-sdaccel/branches/PR-242/builds/6/log
-rw-r--r-- 1 root    root     397909 Dec 10 04:14 jobs/reconfigureio/jobs/reco-sdaccel/branches/master/builds/723/log
@pwaller
Copy link
Contributor Author

pwaller commented Dec 10, 2018

Going by date I would guess #227 is a probable culprit.

@pwaller pwaller transferred this issue from another repository Dec 18, 2018
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

No branches or pull requests

1 participant