Hi,
During last Testperf meeting, it is noticed that there will be several holidays
in the first week of July.
I was actioned to send out an mail to figure out if we should hold the Testperf
meeting on July 5th.
Please feedback by replying the email if you could attend or have some topics
in mi
Dear all,
Right before 4th of July, let’s meet at 6pm Monday 07/02 California time, will
focus on docker registry and Auto CI.
Agenda is posted here.
https://wiki.opnfv.org/pages/viewpage.action?pageId=24576703
Talk to you soon, have a good weekend.
Thank you,
Tina
IMPORTANT NOTICE: The cont
Thanks to those who have submitted LFN Booth Demo Ideas for ONS Europe. *This
is a reminder that submissions are due July 9th*. Please send your ideas to
me as well as add them to this OPNFV Wiki page:
https://wiki.opnfv.org/pages/viewpage.action?pageId=24576260.
Best,
Brandon Wick
Senior Integr
Hi,
Fuel and Armband 6.2.0 release information:
1. Fuel artifacts (x86_64)
- git tag gerrit change [1];
- git tag [2] (will go live once [1] is merged);
- documentation [4, 5, 6];
2. Armband Fuel artifacts (aarch64)
- git tag gerrit change [1];
- git tag [3] (will go live once [1] is merged);
- d
Hey Mark,
I'm aware of the issue and even made a JIRA for it. It happens when multiple
verify jobs are run at the same time. Commenting 'recheck' on the patch should
trigger the job again and hopefully make it pass.
Regards,
Trevor Bramwell
On June 29, 2018 8:46:05 AM PDT, "Beierl, Mark" wrot
Hello, David.
It appears there is an error in Releng [1] that I need to have addressed before
the tagging will be done:
jenkins_jobs.errors.JenkinsJobsException: Unable to lock cache for
'https://build.opnfv.org/ci'
[1] https://build.opnfv.org/ci/job/releng-jjb-verify/278/
Regards,
Mark
Mark
Hi,
Fuel & Armband CI runs:
- nosdn x86_64 HA [1];
- nosdn aarch64 HA [2];
- ODL x86_64 HA [3] (last CI run was before the new tests were
skipped, so please ignore failures related to those);
- ODL aarch64 HA [4] (ditto);
With the new functest testcases ski
BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
Hello Louie,
You were absolutely right to verify your deployment via Functest
Fraser. I suggest you to switch to master because this version can be
already considered as better regarding deployment configurations which
are unverified or partially verified by OPNFV gates such for instance:
- few
Hi，Cédric，
The functest（opnfv/functest-healthcheck：latest）does work, and vping testcase
can test successfully.
Why I chose functest(opnfv/functest-smoke:fraser) is due to the dovetail use
opnfv/functest-smoke:fraser,
and the vping testcase of dovetail has failed, so I chose functest to
10 matches
Mail list logo
