From: bugzilla@dpdk.org
To: ci@dpdk.org
Subject: [Bug 1287] 404 server response code on some sub-pages for Test result (Tarball 26097): https://lab.dpdk.org/results/dashboard/tarballs/26097/
Date: Tue, 12 Sep 2023 17:52:26 +0000 [thread overview]
Message-ID: <bug-1287-149@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1287
Bug ID: 1287
Summary: 404 server response code on some sub-pages for Test
result (Tarball 26097):
https://lab.dpdk.org/results/dashboard/tarballs/26097/
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: dashboard
Assignee: ci@dpdk.org
Reporter: alexa7.free@gmail.com
CC: dpdklab@iol.unh.edu
Target Milestone: ---
Created attachment 261
--> https://bugs.dpdk.org/attachment.cgi?id=261&action=edit
404 server response code on some sub-pages for Test result (Tarball 26097):
https://lab.dpdk.org/results/dashboard/tarballs/26097/
Actual Result:
Server response code = 404 for some sub-pages inside Test result for
(Home/Tarballs/Tarball 26097):
https://lab.dpdk.org/results/dashboard/tarballs/26097/
1) http://git.dpdk.org/dpdk/tree/doc/build-sdk-meson.txt
2) https://doc.dpdk.org/dts/test_plans/unit_tests_lpm_test_plan.html
3) https://doc.dpdk.org/dts/test_plans/unit_tests_mbuf_test_plan.html
4)
http://git.dpdk.org/tools/dts/tree/test_plans/unit_tests_cryptodev_func_test_plan.rst
5)
http://git.dpdk.org/tools/dts/tree/test_plans/unit_tests_cryptodev_func_test_plan.rst
screen: 404_resp_bug_1.png (attached)
Expected Result:
should be server response code = 200 with appropriate content on both pages
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 4538 bytes --]
next reply other threads:[~2023-09-12 17:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 17:52 bugzilla [this message]
2023-09-25 17:45 ` bugzilla
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=bug-1287-149@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=ci@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).