From bugzilla at dpdk.org Mon Jun 17 17:29:20 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Mon, 17 Jun 2019 15:29:20 +0000
Subject: [dpdk-ci] [Bug 157] Allow primary contact to revoke access to
accounts
In-Reply-To:
References:
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=157
Jeremy Plsek (jplsek at iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jeremy Plsek (jplsek at iol.unh.edu) ---
This now exists in the preferences page. If you are a primary contact and the
"Manage Users" page does not show up in the sidebar, please email me.
--
You are receiving this mail because:
You are the assignee for the bug.
From bugzilla at dpdk.org Mon Jun 17 17:29:22 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Mon, 17 Jun 2019 15:29:22 +0000
Subject: [dpdk-ci] [Bug 129] [Epic] Add user management functionality to
dashboard
In-Reply-To:
References:
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=129
Bug 129 depends on bug 157, which changed state.
Bug 157 Summary: Allow primary contact to revoke access to accounts
https://bugs.dpdk.org/show_bug.cgi?id=157
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--
You are receiving this mail because:
You are the assignee for the bug.
From bugzilla at dpdk.org Mon Jun 17 17:33:19 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Mon, 17 Jun 2019 15:33:19 +0000
Subject: [dpdk-ci] [Bug 156] The primary contact should be able to update
the configuration information pdf
In-Reply-To:
References:
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=156
Jeremy Plsek (jplsek at iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jeremy Plsek (jplsek at iol.unh.edu) ---
The "Manage Environments" page now exists in the preferences page.
--
You are receiving this mail because:
You are the assignee for the bug.
From bugzilla at dpdk.org Mon Jun 17 17:33:19 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Mon, 17 Jun 2019 15:33:19 +0000
Subject: [dpdk-ci] [Bug 129] [Epic] Add user management functionality to
dashboard
In-Reply-To:
References:
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=129
Bug 129 depends on bug 156, which changed state.
Bug 156 Summary: The primary contact should be able to update the configuration information pdf
https://bugs.dpdk.org/show_bug.cgi?id=156
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--
You are receiving this mail because:
You are the assignee for the bug.
From bugzilla at dpdk.org Mon Jun 17 17:44:45 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Mon, 17 Jun 2019 15:44:45 +0000
Subject: [dpdk-ci] [Bug 220] Add hardware usage status to the dashboard
In-Reply-To:
References:
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=220
Jeremy Plsek (jplsek at iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jeremy Plsek (jplsek at iol.unh.edu) ---
This is the "CI Status" page.
--
You are receiving this mail because:
You are the assignee for the bug.
From ferruh.yigit at intel.com Tue Jun 18 15:35:25 2019
From: ferruh.yigit at intel.com (Ferruh Yigit)
Date: Tue, 18 Jun 2019 14:35:25 +0100
Subject: [dpdk-ci] DPDK Community Lab Meeting Minutes, Tuesday June 18st
Message-ID: <408f2224-544a-10f6-4cfd-3be240e0c0b2@intel.com>
Tim was out, we did a quick status update and closed early
OVS Tests:
- Work is going on.
SPDK Tests:
- Need to investigate
CI work:
- Will stat next week probably
- Zhaoyan and Aaron already has experience on the topic
Unit test:
- Aaron is working to run unit test on travis
- David Marchand has a patchset in mail list for unit test fixes
- Needs review on the patchset, Aaron's feedback is positive
Misc:
- Aaron did an update to associate travis builds with patchset
- Can it be possible to send a status to patchwork from travis?
- New vendor infrastructure work from past going on.
From bugzilla at dpdk.org Thu Jun 20 13:45:55 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Thu, 20 Jun 2019 13:45:55 +0200 (CEST)
Subject: [dpdk-ci] Your Bugzilla bug list needs attention.
Message-ID: <20190620114555.51DC1A0613@dpdk.space>
[This e-mail has been automatically generated.]
You have one or more bugs assigned to you in the Bugzilla bug tracking system (http://dpdk.space:8000/) that require
attention.
All of these bugs are in the CONFIRMED
state, and have not been touched in 7 days or more.
You need to take a look at them, and decide on an initial action.
Generally, this means one of three things:
(1) You decide this bug is really quick to deal with (like, it's INVALID),
and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to
someone else. (Hint: if you don't know who to reassign it to, make
sure that the Component field seems reasonable, and then use the
"Reset Assignee to default" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
Accept the bug by setting the status to IN_PROGRESS.
To get a list of all CONFIRMED bugs, you can use this URL (bookmark
it if you like!):
http://dpdk.space:8000/buglist.cgi?bug_status=CONFIRMED&assigned_to=ci at dpdk.org
Or, you can use the general query page, at
http://dpdk.space:8000/query.cgi
Appended below are the individual URLs to get to all of your CONFIRMED bugs
that haven't been touched for 7 days or more.
You will get this message once a day until you've dealt with these bugs!
Performance results are not correct on Intel I40E environments
-> http://dpdk.space:8000/show_bug.cgi?id=122
Add mechanism to periodically image nodes
-> http://dpdk.space:8000/show_bug.cgi?id=123
Add previous/next navigation links to dashboard detail page
-> http://dpdk.space:8000/show_bug.cgi?id=124
Find a replacement for NFS for Jenkins filestore
-> http://dpdk.space:8000/show_bug.cgi?id=125
Rename dev cluster FQDN suffix to dpdkdev.iol.unh.edu
-> http://dpdk.space:8000/show_bug.cgi?id=126
Add a favicon to the dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=127
[Epic] Display historical trend plots on dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=128
[Epic] Add user management functionality to dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=129
As an IOL employee, I would like to send a new user a token-based URL to set their password
-> http://dpdk.space:8000/show_bug.cgi?id=130
As an employee of a Member company, I would like to be able to request a dashboard account
-> http://dpdk.space:8000/show_bug.cgi?id=131
As a primary contact for a Member company, I would like to manage the users in my organization
-> http://dpdk.space:8000/show_bug.cgi?id=132
As an employee of a Member company, I would like to request/access my VPN credentials
-> http://dpdk.space:8000/show_bug.cgi?id=133
Investigate using OAuth or SAML for dashboard authentication to REST API
-> http://dpdk.space:8000/show_bug.cgi?id=134
Consider using zxcvbn for client-side password validation
-> http://dpdk.space:8000/show_bug.cgi?id=135
Add a way for users to filter results
-> http://dpdk.space:8000/show_bug.cgi?id=136
[Epic] Patchwork 2.1 (API 1.1)
-> http://dpdk.space:8000/show_bug.cgi?id=137
Delete old log files
-> http://dpdk.space:8000/show_bug.cgi?id=138
When measurements throws a 404, the dashboard throws a 500
-> http://dpdk.space:8000/show_bug.cgi?id=139
Invalidate dashboard cache on database changes
-> http://dpdk.space:8000/show_bug.cgi?id=140
Restructure network
-> http://dpdk.space:8000/show_bug.cgi?id=141
Creating a user requires restarting sssd on leaf node for them to log in
-> http://dpdk.space:8000/show_bug.cgi?id=142
[Epic] Add hardware description page
-> http://dpdk.space:8000/show_bug.cgi?id=144
Add API Key access to the preferences page
-> http://dpdk.space:8000/show_bug.cgi?id=145
Add initial hardware description API
-> http://dpdk.space:8000/show_bug.cgi?id=146
Add hardware description UI to the dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=148
Add GA Performance results to the database
-> http://dpdk.space:8000/show_bug.cgi?id=149
Add GA Performance deltas to the detailed view
-> http://dpdk.space:8000/show_bug.cgi?id=150
Add graphing of GA over time to the dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=151
[Epic] Increase performance or perception of performance of the dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=152
Add timezone to date times
-> http://dpdk.space:8000/show_bug.cgi?id=153
Parse NIC speed into GbE
-> http://dpdk.space:8000/show_bug.cgi?id=155
The primary contact should be able to set their environments public or private
-> http://dpdk.space:8000/show_bug.cgi?id=158
Change VPN to use routed configuration instead of bridged
-> http://dpdk.space:8000/show_bug.cgi?id=159
Add graphing of LTS over time to the dashboard
-> http://dpdk.space:8000/show_bug.cgi?id=160
Private files can't be downloaded via CLI easily
-> http://dpdk.space:8000/show_bug.cgi?id=162
Check hardware/software for changes on each test run
-> http://dpdk.space:8000/show_bug.cgi?id=167
Send separate emails to users instead of CCing everyone
-> http://dpdk.space:8000/show_bug.cgi?id=170
Create LTS performance Jenkins Job
-> http://dpdk.space:8000/show_bug.cgi?id=171
JS homepage TypeError with Chrome
-> http://dpdk.space:8000/show_bug.cgi?id=207
Main tree is not up to date when patch sent, which cause merge error
-> http://dpdk.space:8000/show_bug.cgi?id=209
Patches with dependency fails to apply
-> http://dpdk.space:8000/show_bug.cgi?id=210
add a new testcase: autotest, which runs a defined set of unit tests
-> http://dpdk.space:8000/show_bug.cgi?id=212
Using wrong/old commit id of the tree to apply the patch
-> http://dpdk.space:8000/show_bug.cgi?id=223
Possibly wrong regression report
-> http://dpdk.space:8000/show_bug.cgi?id=224
lab scripts should be upstreamed to dpdk-ci repository
-> http://dpdk.space:8000/show_bug.cgi?id=229
publish a tutorial about how to deploy a DPDK lab
-> http://dpdk.space:8000/show_bug.cgi?id=230
when a sub-tree used as base, two different commit id displayed in logs
-> http://dpdk.space:8000/show_bug.cgi?id=231
Should we make it more visible when at least one of the platforms failed?
-> http://dpdk.space:8000/show_bug.cgi?id=232
Create a way to share artifacts
-> http://dpdk.space:8000/show_bug.cgi?id=233
DPDK Compilation Coverage
-> http://dpdk.space:8000/show_bug.cgi?id=243
Running Unit Testing
-> http://dpdk.space:8000/show_bug.cgi?id=244
Add virtio testing to the community lab
-> http://dpdk.space:8000/show_bug.cgi?id=245
Add cryptodev testing to the community lab
-> http://dpdk.space:8000/show_bug.cgi?id=246
Add compression testing to the community lab
-> http://dpdk.space:8000/show_bug.cgi?id=247
Auto create measurements and test cases as results are submitted
-> http://dpdk.space:8000/show_bug.cgi?id=254
Run clang compilation on windows
-> http://dpdk.space:8000/show_bug.cgi?id=286
From mb at smartsharesystems.com Mon Jun 24 12:02:15 2019
From: mb at smartsharesystems.com (=?utf-8?B?TW9ydGVuIEJyw7hydXA=?=)
Date: Mon, 24 Jun 2019 12:02:15 +0200
Subject: [dpdk-ci] DPDK Patchwork account creation problem
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B42972@smartserver.smartshare.dk>
Hi DPDK CI team,
I have a problem registering a new account with DPDK patchwork. I couldn't find any support email address about this, so I'm hoping someone on this mailing list can pick it up. (Please reply directly, as I'm not subscribing to this mailing list.)
When I tried to register a new account (https://patchwork.dpdk.org/register/) with my email address (mb at smartsharesystems.com) and the username (MortenBr?rup), it failed with a 500 server error.
If I now use the password reset function (https://patchwork.dpdk.org/user/password-reset/) and provide my email address (mb at smartsharesystems.com), I don't receive an email with reset instructions (or any email at all). I have checked the log in our spam filter... Nothing.
If I now try to register a new account (https://patchwork.dpdk.org/register/) with the same email address and my username (MortenBr?rup), it says that the email address is already in use and the username is already taken.
Med venlig hilsen / kind regards
Morten Br?rup
CTO
SmartShare Systems A/S
Tonsbakken 16-18
DK-2740 Skovlunde
Denmark
Office +45 70 20 00 93
Direct +45 89 93 50 22
Mobile +45 25 40 82 12
mb at smartsharesystems.com
www.smartsharesystems.com
From mb at smartsharesystems.com Mon Jun 24 15:24:43 2019
From: mb at smartsharesystems.com (=?utf-8?B?TW9ydGVuIEJyw7hydXA=?=)
Date: Mon, 24 Jun 2019 15:24:43 +0200
Subject: [dpdk-ci] DPDK Patchwork account creation problem
In-Reply-To: <3701432.lnjjSTQL8V@xps>
References: <98CBD80474FA8B44BF855DF32C47DC35B42972@smartserver.smartshare.dk>
<3701432.lnjjSTQL8V@xps>
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B42976@smartserver.smartshare.dk>
Hi Thomas,
This time I tried without the Danish letter ? in my username, and it worked.
Thank you for the quick response!
Med venlig hilsen / kind regards
- Morten Br?rup
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas at monjalon.net]
> Sent: Monday, June 24, 2019 3:21 PM
> To: Morten Br?rup
> Subject: Re: [dpdk-ci] DPDK Patchwork account creation problem
>
> I removed your user in patchwork.
> Please try to create it again.
>
> 24/06/2019 12:02, Morten Br?rup:
> > Hi DPDK CI team,
> >
> > I have a problem registering a new account with DPDK patchwork. I
> couldn't find any support email address about this, so I'm hoping
> someone on this mailing list can pick it up. (Please reply directly, as
> I'm not subscribing to this mailing list.)
> >
> > When I tried to register a new account
> (https://patchwork.dpdk.org/register/) with my email address
> (mb at smartsharesystems.com) and the username (MortenBr?rup), it failed
> with a 500 server error.
> >
> > If I now use the password reset function
> (https://patchwork.dpdk.org/user/password-reset/) and provide my email
> address (mb at smartsharesystems.com), I don't receive an email with reset
> instructions (or any email at all). I have checked the log in our spam
> filter... Nothing.
> >
> > If I now try to register a new account
> (https://patchwork.dpdk.org/register/) with the same email address and
> my username (MortenBr?rup), it says that the email address is already
> in use and the username is already taken.
> >
> >
> > Med venlig hilsen / kind regards
> >
> > Morten Br?rup
> > CTO
> >
> >
> > SmartShare Systems A/S
> > Tonsbakken 16-18
> > DK-2740 Skovlunde
> > Denmark
> >
> > Office +45 70 20 00 93
> > Direct +45 89 93 50 22
> > Mobile +45 25 40 82 12
> >
> > mb at smartsharesystems.com
> > www.smartsharesystems.com
> >
> >
>
>
>
>
>
From bugzilla at dpdk.org Mon Jun 24 20:33:52 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Mon, 24 Jun 2019 18:33:52 +0000
Subject: [dpdk-ci] [Bug 292] Allow members to stop future jobs from running
on their host from the dashboard
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=292
Bug ID: 292
Summary: Allow members to stop future jobs from running on
their host from the dashboard
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: enhancement
Priority: Normal
Component: dashboard
Assignee: ci at dpdk.org
Reporter: jplsek at iol.unh.edu
CC: jplsek at iol.unh.edu
Target Milestone: ---
At the moment, I think it is possible for members to log into Jenkins and
disable jobs via the matrix permissions that we have set up.
But it would be nice for this functionality to exist in the dashboard.
Sometimes we have members that are on the system trying to fix issues, while
the CI could be potentially running. Aside from members going on Jenkins,
typically I'll stop the CI for a period of time before putting it back online,
for this maintenance to take place.
This system would need these features:
Some way of notifying that the job has been manually disabled and enabled from
the dashboard (most likely email).
Notify via email every 24 hours to the user who stopped the CI, to remind them
that the job is disabled and should be re-enabled asap.
--
You are receiving this mail because:
You are the assignee for the bug.
From mb at smartsharesystems.com Tue Jun 25 21:43:35 2019
From: mb at smartsharesystems.com (=?utf-8?B?TW9ydGVuIEJyw7hydXA=?=)
Date: Tue, 25 Jun 2019 21:43:35 +0200
Subject: [dpdk-ci] Compilation error fixed by other patch
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B42985@smartserver.smartshare.dk>
Dear CI team,
Some patches failed compilation in CI due to unrelated compilation errors, which have now been fixed.
The fixes for the unrelated compilation errors are these:
https://patchwork.dpdk.org/patch/55085/
https://patchwork.dpdk.org/patch/55086/
A couple of my patches that failed compilation due to the above bugs, and would probably not fail now that they have been fixed, are:
https://patchwork.dpdk.org/patch/55168/
https://patchwork.dpdk.org/patch/55170/
How do I make Patchwork run the compilation tests on my two patches again, so they don't show up in the list as failing?
And a lot of other people's patches are similarly affected. Is there anything to do about that?
Med venlig hilsen / kind regards
- Morten Br?rup
From bugzilla at dpdk.org Wed Jun 26 09:55:59 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Wed, 26 Jun 2019 07:55:59 +0000
Subject: [dpdk-ci] [Bug 293] Can we add a filter for status,
to be able to see only some patches with specific status
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=293
Bug ID: 293
Summary: Can we add a filter for status, to be able to see only
some patches with specific status
Product: lab
Version: unspecified
Hardware: All
OS: All
Status: CONFIRMED
Severity: normal
Priority: Normal
Component: dashboard
Assignee: ci at dpdk.org
Reporter: ferruh.yigit at intel.com
CC: jplsek at iol.unh.edu
Target Milestone: ---
To be able to see quickly see only the patches with 'possible regression' etc,
without need to go through all list to find them.
This is a low priority, good to have feature request.
--
You are receiving this mail because:
You are the assignee for the bug.
From bugzilla at dpdk.org Wed Jun 26 16:21:07 2019
From: bugzilla at dpdk.org (bugzilla at dpdk.org)
Date: Wed, 26 Jun 2019 14:21:07 +0000
Subject: [dpdk-ci] [Bug 232] Should we make it more visible when at least
one of the platforms failed?
In-Reply-To:
References:
Message-ID:
https://bugs.dpdk.org/show_bug.cgi?id=232
Jeremy Plsek (jplsek at iol.unh.edu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jeremy Plsek (jplsek at iol.unh.edu) ---
Sure thing.
--
You are receiving this mail because:
You are the assignee for the bug.
From thomas at monjalon.net Thu Jun 27 18:34:18 2019
From: thomas at monjalon.net (Thomas Monjalon)
Date: Thu, 27 Jun 2019 18:34:18 +0200
Subject: [dpdk-ci] [dpdk-dev] [PATCH 00/14] Unit tests fixes for CI
In-Reply-To: <81c5f665-97ac-c4d0-8281-8f195c63195e@redhat.com>
References: <1559638792-8608-1-git-send-email-david.marchand@redhat.com>
<81c5f665-97ac-c4d0-8281-8f195c63195e@redhat.com>
Message-ID: <2134880.WhL1dmy7PZ@xps>
04/06/2019 17:49, Michael Santana Francisco:
> On 6/4/19 4:59 AM, David Marchand wrote:
> > - the "perf" tests are taking way too long for my taste,
>
> We should still fix them. However I don't know if we should be running
> the perf test for every job and every patch on travis. It takes too
> long. The travis queue will be delayed too far behind for it to be of
> any use.
>
> OTOH we could have one job as part of the travis build dedicated to
> running tests (or just perf test). It's still time consuming but better
> than running the test on every travis job. For this to work we would
> need to decreased the timeout for the perf tests as the timeout for it
> and the travis are both 10 minutes
+Cc ci at dpdk.org
I don't think we should run the perf tests in basic CI like Travis.
We can run perf tests if the purpose is to compare the performance
with previous releases, as some other tests in the community lab.