Skip to contentSkip to conversation

LTP release

LTP Cyril Hrubis 1 participant 4 messages Mar 23, 2015 – Apr 14, 2015 2 messages not in the archive

lore
Share & tools
lore
#0 lore raw

Hi!
It's about the time we start to prepare for next release. I will (hopefully) start runing latest git code and look for unexpected failures during this week. Everybody please try to run the latest git code and report any problems.

If there is anything that should be solved/applied before the release, plese let us know.

(My current plan is to have a look at the power_management fixes.)

Signature · 13 lines
Cyril Hrubis
[email protected]

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list
#1 lore raw

Hi!

Quoted 4 lines

It's about the time we start to prepare for next release. I will (hopefully) start runing latest git code and look for unexpected failures during this week. Everybody please try to run the latest git code and report any problems.

I've seen email from Jan that the release is green from his side. (haven't got it because we had an email outgate in the SUSE and it seems some emails were lost :(, if you get errors for my suse email account do not hestitate to resend).

What is the status from the rest of you?

From my side, I've fixed a few problem I've found but there are still two things I want to fix before the release.

One is aligment bug causing aiocp with O_DIRECT exit with EINVAL on s390x with 4096 block size. That should be fixed with block size autodetection for O_DIRECT.

And the second is with the rewrite of the exec* testcases (without the p in the name). The problem is that the machinery that runs tests in SUSE does not execute the testcases in the $LTPROOT/testcases/bin directory, and these testcases fail to find the child binary. Solution I have in mind is to create a function similar to tst_dataroot() that will fill a buffer with a path to the binary (so that the tests works both in git checkout and executed from installed tree). Is anybody opposed to this idea?

Signature · 13 lines
Cyril Hrubis
[email protected]

------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

Hi!

Quoted 10 lines
Quoted 10 lines
Quoted 4 lines

It's about the time we start to prepare for next release. I will (hopefully) start runing latest git code and look for unexpected failures during this week. Everybody please try to run the latest git code and report any problems.

I've seen email from Jan that the release is green from his side. (haven't got it because we had an email outgate in the SUSE and it seems some emails were lost :(, if you get errors for my suse email account do not hestitate to resend).

Quoted 6 lines
Quoted 2 lines

What is the status from the rest of you?

We have several issues in our sparc64 environment. Need a day or two to figure out whether they are test case issues or problems with our environment.

Ok.

Signature · 13 lines
Cyril Hrubis
[email protected]

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw

Hi!

Quoted 12 lines
Quoted 6 lines
Quoted 3 lines

We have several issues in our sparc64 environment. Need a day or two to figure out whether they are test case issues or problems with our environment.

Ok.

Finally, there are only two test case issues:
* cpuhotplug04 fails if there is no 'online' file in
/sys/devices/system/cpu/cpuXX/
* sem_comm fails because it doesn't use 'union semun' with semctl()

Quoted 4 lines

Patches to the problems were sent.

I suppose that cpuhotplug* fixes may be postponed for a later time, but it would be good to have the sem_comm fixes in this release.

The 'union semun' patches looks good, acked. Please push these.

And that should be, hopefully, last patches going into the release.

I will do a full testrun once these paches are pushed and if everything works fine I will tag the release. Does everybody agree?

Signature · 13 lines
Cyril Hrubis
[email protected]

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list