Daily linux-next Kernel CI builds=34/35/36 failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linaro CI |
Fix Released
|
Medium
|
Fathi Boudra |
Bug Description
linux next build link:
---------------
https:/
build log print:
-------
00:21:13 + lava_test_
00:21:13 + test -z
https:/
00:21:13 + wget -cq
https:/
00:21:13 + cleanup_exit
00:21:13 + cd /mnt/ci_
00:21:13 + rm -rf lci-build-tools
00:21:13 + rm -rf builddir*
00:21:13 Build step 'Execute shell' marked build as failure
00:21:13 Finished: FAILURE
origen build:
------------------
https:/
https:/
https:/
multiplatform build:
-------
https:/
https:/
https:/
panda build:
-----------------
https:/
https:/
https:/
vexpress build :
-------
https:/
https:/
https:/
Related branches
- Philip Colmer (community): Approve
- Milo Casagrande (community): Approve
- Ben Copeland: Pending requested
-
Diff: 29 lines (+8/-0)2 files modifiednode/setup-precise-node (+1/-0)
node/setup_lib (+7/-0)
Changed in linaro-ci: | |
milestone: | none → 2013.05 |
status: | New → Confirmed |
Changed in linaro-ci: | |
assignee: | Milo Casagrande (milo) → Fathi Boudra (fboudra) |
Changed in linaro-ci: | |
status: | Confirmed → Fix Committed |
Changed in linaro-ci: | |
status: | Fix Committed → Fix Released |
I started to take a look at this problem, but I'm not able to understand where the issue lies.
Looking at the job configuration:
https:/ /ci.linaro. org/jenkins/ job/linux- next/configure
and at the console output, it looks like it is failing in some way on the "wget" action, because it is calling the trapped function "cleanup_exit" just after that.
If I try locally to wget that URL, it works correctly.
We might want to try to suppress wget "-q" parameter to see more output from it.