From: don.brown@codethink.com (Don Brown)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] The Problem with build.log
Date: Thu, 08 Dec 2016 09:44:10 -0500 [thread overview]
Message-ID: <01e40d42ba066478e3aa474b7b6fea5e@codethink.com> (raw)
Hi Robert,
I may have found the problem with the links to the build.log,
kernel.config and zImage files.
As you can see from the attached Screenshots, when I hover over the
links, the URL has some duplicated information in it.
* For instance, the link to the build.log file is shown as:
o
/localhost:5000/build/cip-dreiwettertaft/kernel/v4.4.27/localhost/cip-dreiwettertaft/kernel/v4.4.27/arm-tinyconfig/build.log/
* The kernel.config link is shown as:
o
/localhost:5000/build/cip-dreiwettertaft/kernel/v4.4.27/localhost/cip-dreiwettertaft/kernel/v4.4.27/arm-tinyconfig/kernel.config/
* The zImage link is shown as:
o
/localhost:5000/build/cip-dreiwettertaft/kernel/v4.4.27/localhost/cip-dreiwettertaft/kernel/v4.4.27/arm-tinyconfig/zImage/
The files are actually stored in the following location on disk:
//var/www/images/kernel-ci/cip-dreiwettertaft/v4.4.27/arm-tinyconfig/
So I think they are grabbing a string to append to the site URL and they
are grabbing more than they wanted.
P.S. I also created an Issue (#2) in the GitLab site for this, but I
wasn't sure how attaching the pics would go.
--
Don Brown
Codethink, Ltd.
Software Engineering Consultant
Indianapolis, IN USA
Email: don.brown at codethink.co.uk
Mobile: +1 317-560-0513
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20161208/34a8a26f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot #1 from 2016-12-07 19-50-36.png
Type: image/png
Size: 120710 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20161208/34a8a26f/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot #2 from 2016-12-07 19-50-57.png
Type: image/png
Size: 115470 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20161208/34a8a26f/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot #3 from 2016-12-07 19-51-08.png
Type: image/png
Size: 120762 bytes
Desc: not available
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20161208/34a8a26f/attachment-0005.png>
reply other threads:[~2016-12-08 14:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01e40d42ba066478e3aa474b7b6fea5e@codethink.com \
--to=don.brown@codethink.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.