results of developer-galaxynexus-jb-gcc47-aosp-blob builds not archived

Bug #1134758 reported by Bernhard Rosenkraenzer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Android Infrastructure
Invalid
High
James Tunnicliffe

Bug Description

https://android-build.linaro.org/builds/~berolinux/developer-galaxynexus-jb-gcc47-aosp-blob/#build=34

Build succeeded, and the output at
https://android-build.linaro.org/jenkins/job/berolinux_developer-galaxynexus-jb-gcc47-aosp-blob/34/parsed_console/?
shows out/target/product/maguro/system.img and friends being created successfully.

Yet the only files made available at the android-build page are pinned-manifest.xml and source-manifest.xml

Revision history for this message
Данило Шеган (danilo) wrote :

Files are available on http://snapshots.linaro.org/android/~berolinux/developer-galaxynexus-jb-gcc47-aosp-blob/34/

In the console log, I get JavaScript errors:

Failed to load resource: the server responded with a status of 404 (NOT FOUND) https://android-build.linaro.org/api/test-dir-exists?url=http://snapshots.linaro.org/android/~berolinux/developer-galaxynexus-jb-gcc47-aosp-blob/34/
Failed to load resource: the server responded with a status of 404 (NOT FOUND) https://android-build.linaro.org/api/proxy-remote-file?url=http://android-build.linaro.org/builds/~berolinux/developer-galaxynexus-jb-gcc47-aosp-blob/34//MANIFEST
Failed to load resource: the server responded with a status of 404 (NOT FOUND) https://android-build.linaro.org/api/proxy-remote-file?url=http://android-build.linaro.org/builds/~berolinux/developer-galaxynexus-jb-gcc47-aosp-blob/34//lava-job-info
Failed to load resource: the server responded with a status of 404 (Not Found) https://android-build.linaro.org/static/images/ui-bg_highlight-soft_100_eeeeee_1x100.png
Failed to load resource: the server responded with a status of 404 (Not Found) https://android-build.linaro.org/static/images/ui-bg_glass_100_f6f6f6_1x400.png
Failed to load resource: the server responded with a status of 404 (Not Found) https://android-build.linaro.org/static/images/ui-bg_glass_65_ffffff_1x400.png
Failed to load resource: the server responded with a status of 404 (Not Found) https://android-build.linaro.org/static/images/ui-bg_glass_100_fdf5ce_1x400.png

I don't remember exactly, but I think we use MANIFEST file to list all the files on android-build. The fact that we can't fetch is probably why it doesn't display anything else.

Changed in linaro-android-infrastructure:
status: New → Triaged
importance: Undecided → High
milestone: none → 2013.03
Revision history for this message
James Tunnicliffe (dooferlad) wrote :

Yes, MANIFEST is used if we find it. If not we display the files listed under Build Artifacts (https://android-build.linaro.org/jenkins/job/berolinux_developer-galaxynexus-jb-gcc47-aosp-blob/38/ has pinned & source manifest.xml files, these show up on https://android-build.linaro.org/builds/~berolinux/developer-galaxynexus-jb-gcc47-aosp-blob/#build=38 because it couldn't find MANIFEST.

If neither MANIFEST or a list of artifacts can be found, you will see "Unable to find downloads list." printed in place. If you want to see what is happening, stick a breakpoint inside buildDetails.js in your browser around line 275. Chrome and FireFox can do this. Ping me if you need help.

As far as I can tell, the web UI is working fine. It is the job that needs to provide this information.

Changed in linaro-android-infrastructure:
status: Triaged → Invalid
assignee: nobody → James Tunnicliffe (dooferlad)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.