Menu
▾
▴
crackerjack-devel — List for development discussions
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(12) |
Feb
(6) |
Mar
|
Apr
(25) |
May
(6) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
(2) |
Feb
(11) |
Mar
|
Apr
(5) |
May
(5) |
Jun
(19) |
Jul
(17) |
Aug
(15) |
Sep
(22) |
Oct
(5) |
Nov
(8) |
Dec
(2) |
| 2009 |
Jan
(6) |
Feb
(7) |
Mar
(7) |
Apr
(2) |
May
(1) |
Jun
|
Jul
(4) |
Aug
(4) |
Sep
(7) |
Oct
(8) |
Nov
|
Dec
|
| 2010 |
Jan
(2) |
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
(20) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: Samuel Q. <Sam...@sy...> - 2012-11-20 17:15:52
|
Hello,
I have crackerjack-3.3. When I run the write test almost every test fails with "Bad file descriptor". This is because most of the files are opened readonly – using FLAGS2 in lib/kor/test_common.c.
See for example symbolic_exist_file_fd() in test_common.c:
#define FLAGS O_RDWR
#define FLAGS2 O_RDONLY
int symbolic_exist_file_fd()
{
int fd;
char tmpfile[MAXFILENAME];
memset(&tmpfile, 0, MAXFILENAME);
strcpy(tmpfile, symbolic_exist_file());
fd = open(tmpfile, FLAGS2);
errno=0;
return fd;
}
It seems to me like there should be a version of symbolic_exist_file_fd() that uses FLAGS instead of FLAGS2 for the write case.
Why does cs_write.c call symbolic_exist_file_fd()? Look at this declaration in testcases/write/cs_write.h:
cs_write.h
struct data_and_gen fd_data[] = {
#include "fd_name_read.h"
};
include/kor/fd_name_read.h
{ 1, "EXIST_FILE_FD", exist_file_fd },
{ 2, "EXIST_DIR_FD", exist_dir_fd },
{ 3, "SYMBOLIC_EXIST_FILE_FD", symbolic_exist_file_fd },
{ 4, "SYMBOLIC_EXIST_DIR_FD", symbolic_exist_dir_fd },
{ 5, "PIPE_FD", pipe_fd },
//{ 6, "FIFO_FD", fifo_fd }, // be holding status
{ 7, "MAX_FD", max_fd },
{ 8, "INVALID_FD", invalid_fd },
{ 9, "CLOSE_FD", close_fd },
{ FINAL_DATA, NULL, NULL }
There is a similar issue with pipe_fd(), it returns the read end of the pipe. Shouldn't there be a version that returns the write end?
-Sam
|
|
From: Caspar Z. <cz...@re...> - 2010-12-28 02:57:26
|
On 12/28/2010 10:50 AM, his...@hi... wrote: > Casper, > > Sorry for getting back to you. > > Basically, I agree on your proposal. > > Why this kind of complex structure happend is that > we have not discussed on the structure of directory among us when we started this > project. So that China, Korea, Japan engineers had developed under their > own idea. > > I had tried to re-structure directories, but not had enough time. > But I would like to do with you. > I've made a fix for this, on my own branch in git.sf repo: http://crackerjack.git.sourceforge.net/git/gitweb.cgi?p=crackerjack/crackerjack;a=shortlog;h=refs/heads/caspar I've tested it in RHEL6-i386 GA and seemed everything works OK. Welcome to download the snapshot tar ball to test and give feedbacks: http://crackerjack.git.sourceforge.net/git/gitweb.cgi?p=crackerjack/crackerjack;a=snapshot;h=08bf4ccd0fb570ea09b03f2dbd91a44b6fde33dc;sf=tgz Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ -- C-A-S-P-A-R, Caspar /kæspɑ:/ ;-) |
|
From: <his...@hi...> - 2010-12-28 02:51:00
|
Casper, Sorry for getting back to you. Basically, I agree on your proposal. Why this kind of complex structure happend is that we have not discussed on the structure of directory among us when we started this project. So that China, Korea, Japan engineers had developed under their own idea. I had tried to re-structure directories, but not had enough time. But I would like to do with you. Thanks, >Hi list, I'm wondering if we can re-organize the testcase dir, changes >could be as follows: > >1) testcases/testcasedir/*, I don't know why some testcases are under >testcasedir folder, seems that they have no difference with other tests. >Why not mv testcases/testcasedir/* to testcase/*? > >2) some testcases only test man page, in a folder `man'. To categorize >such tests, I suggest to mv testcases/*/man to testcases/man/*, so that >we can easily find man page testings under testcases/man. > >Any suggestions? > >Thanks, >Caspar >-- >Quality Assurance Associate (Kernel) in >Red Hat Software (Beijing) Co., R&D Branch > >TEL: +86-10-62608150 >WEB: http://www.redhat.com/ > >------------------------------------------------------------------------------ >Forrester recently released a report on the Return on Investment (ROI) of >Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even >within 7 months. Over 3 million businesses have gone Google with Google Apps: >an online email calendar, and document program that's accessible from your >browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew >_______________________________________________ >Crackerjack-devel mailing list >Cra...@li... >https://lists.sourceforge.net/lists/listinfo/crackerjack-devel > Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
|
From: Caspar Z. <cz...@re...> - 2010-12-22 17:35:26
|
Hi list, I'm wondering if we can re-organize the testcase dir, changes could be as follows: 1) testcases/testcasedir/*, I don't know why some testcases are under testcasedir folder, seems that they have no difference with other tests. Why not mv testcases/testcasedir/* to testcase/*? 2) some testcases only test man page, in a folder `man'. To categorize such tests, I suggest to mv testcases/*/man to testcases/man/*, so that we can easily find man page testings under testcases/man. Any suggestions? Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-21 10:29:39
|
On 12/17/2010 01:39 PM, Caspar Zhang wrote: > Hi list, I open this thread to discuss the plan and implementation of > improving crackerjack code quality, anyone who is interested in it is > welcomed to join the discussion. > > What I've met for now are as follows: > > 1) Handling non-existed syscalls. I wonder if anyone got a chance to > look into LTP's codes, maybe we can backport some codes from it to > handle this issue. Anyway, I think it is necessary to handle non-existed > syscalls, else the compilation will not pass. > > 2) feature test macros. I don't know much about that, but I guess > _GNU_SOURCE macro is necessary, while others like: SUSv2 (UNIX 98) which > needs _XOPEN_SOURCE defined and value > 500, is it necessary? does > crackerjack supposed to be run on Unix systems? fixed one in r1004, will fix them if I find more similar defects. > > 3) hard-coded syscalls. take ssetmask testcase, in Line 25: > syscall(69, SIGALRM); > > Different arch has different number for ssetmask() syscall, we shouldn't > use hard-coded number. > > 4) Windows ^M character and non-English comments: see delete_module03 > testcase. fixed in r999, will fix them if I find more similar defects. > > That's all so far, will add more items if I find. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-21 10:27:13
|
On 12/10/2010 02:57 AM, Caspar Zhang wrote: > discarded and updated patches, see commit r997 - r1006. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-21 10:27:07
|
On 12/10/2010 02:57 AM, Caspar Zhang wrote: > discarded and updated patches, see commit r997 - r1006. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-21 10:27:00
|
On 12/10/2010 02:56 AM, Caspar Zhang wrote: > discarded and updated patches, see commit r997 - r1006. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-21 10:26:45
|
discarded and updated, see commit r997 - r1006. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-21 10:24:58
|
On 12/16/2010 07:32 PM, Caspar Zhang wrote: > > I found there're something can be improved on my patches, now I want to > discard all my previous patches and will come up with a batch of new > versions. Sorry for inconvenience. I've submitted my new changes to svn and a new git repo[1], all patches are discarded. Thanks, Caspar [1] http://crackerjack.git.sourceforge.net/ -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: <his...@hi...> - 2010-12-21 00:39:14
|
Casper, >discard all my previous patches and will come up with a batch of new I understand. >to public yet? If I want to patch Crackerjack codes, I want to work on a >latest svn/git version. I only update the tar ball which contains test cases only. I placed that tar ball on sourceforge. Sorry for your inconvenience. Hashimoto >On 12/14/2010 08:01 AM, his...@hi... wrote: >> Casper, >> >> Thanks for patches. >> >> I will apply them and upload new source. >> > >Hashimoto-san, thanks for your reply. > >I found there're something can be improved on my patches, now I want to >discard all my previous patches and will come up with a batch of new >versions. Sorry for inconvenience. > >Additionally, I have a question. I found crackerjack team released a new >version in Oct, 2010. However, I found the svn version was too old, the >last commit was on Nov 28, 2009. Is there any changes/commits not send >to public yet? If I want to patch Crackerjack codes, I want to work on a >latest svn/git version. > >Thanks in advance, >Caspar > >-- >Quality Assurance Associate (Kernel) in >Red Hat Software (Beijing) Co., R&D Branch > >TEL: +86-10-62608150 >WEB: http://www.redhat.com/ > Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
|
From: Caspar Z. <cz...@re...> - 2010-12-17 05:39:37
|
Hi list, I open this thread to discuss the plan and implementation of improving crackerjack code quality, anyone who is interested in it is welcomed to join the discussion. What I've met for now are as follows: 1) Handling non-existed syscalls. I wonder if anyone got a chance to look into LTP's codes, maybe we can backport some codes from it to handle this issue. Anyway, I think it is necessary to handle non-existed syscalls, else the compilation will not pass. 2) feature test macros. I don't know much about that, but I guess _GNU_SOURCE macro is necessary, while others like: SUSv2 (UNIX 98) which needs _XOPEN_SOURCE defined and value > 500, is it necessary? does crackerjack supposed to be run on Unix systems? 3) hard-coded syscalls. take ssetmask testcase, in Line 25: syscall(69, SIGALRM); Different arch has different number for ssetmask() syscall, we shouldn't use hard-coded number. 4) Windows ^M character and non-English comments: see delete_module03 testcase. That's all so far, will add more items if I find. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-16 11:32:37
|
On 12/14/2010 08:01 AM, his...@hi... wrote: > Casper, > > Thanks for patches. > > I will apply them and upload new source. > Hashimoto-san, thanks for your reply. I found there're something can be improved on my patches, now I want to discard all my previous patches and will come up with a batch of new versions. Sorry for inconvenience. Additionally, I have a question. I found crackerjack team released a new version in Oct, 2010. However, I found the svn version was too old, the last commit was on Nov 28, 2009. Is there any changes/commits not send to public yet? If I want to patch Crackerjack codes, I want to work on a latest svn/git version. Thanks in advance, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: <his...@hi...> - 2010-12-14 00:30:53
|
Yes I'm here. Thnx >Hello list, I tried to use crackerjack to run some regression test on >RHEL and Fedora, however, I found there were some bugs stopping me >compiling through the testcases, I wrote some workarounds and would like >to send these patches to the list soon. > >Since I found this list is so quiet, please let me know if there still >are maintainers or developers in this list. > >Thanks, >Caspar >-- >Quality Assurance Associate (Kernel) in >Red Hat Software (Beijing) Co., R&D Branch > >TEL: +86-10-62608150 >WEB: http://www.redhat.com/ > >------------------------------------------------------------------------------ >_______________________________________________ >Crackerjack-devel mailing list >Cra...@li... >https://lists.sourceforge.net/lists/listinfo/crackerjack-devel > Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
|
From: <his...@hi...> - 2010-12-14 00:30:48
|
Casper, Thanks for patches. I will apply them and upload new source. Hashimoto >Hi all, here are some patches to fix compiling issue: > >1. fixing header issue(missing header/non-existed header/not included >header path, etc); >2. fixing syntax error; >3. fixing a __set_errno error. >4. fixing "Never use <bits/byteswap.h> directly; include <byteswap.h> >instead." error message. > >Patches are tested under RHEL6@x86_64, note that some more issues >exists: the following syscalls are not existed @ x86_64: fadvise64_64 >fcntl64 setfsgid setfsuid getcpu sgetmask vm86, also there are some >other non-existed syscalls on other platforms, I will put the >workarounds together and submit a patch. > >Thanks, >Caspar >-- >Quality Assurance Associate (Kernel) in >Red Hat Software (Beijing) Co., R&D Branch > >TEL: +86-10-62608150 >WEB: http://www.redhat.com/ > >------------------------------------------------------------------------------ >_______________________________________________ >Crackerjack-devel mailing list >Cra...@li... >https://lists.sourceforge.net/lists/listinfo/crackerjack-devel > Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
|
From: Caspar Z. <cz...@re...> - 2010-12-09 18:58:10
|
-- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-09 18:57:32
|
-- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-09 18:56:50
|
-- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-09 18:56:19
|
-- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-09 18:53:50
|
Hi all, here are some patches to fix compiling issue: 1. fixing header issue(missing header/non-existed header/not included header path, etc); 2. fixing syntax error; 3. fixing a __set_errno error. 4. fixing "Never use <bits/byteswap.h> directly; include <byteswap.h> instead." error message. Patches are tested under RHEL6@x86_64, note that some more issues exists: the following syscalls are not existed @ x86_64: fadvise64_64 fcntl64 setfsgid setfsuid getcpu sgetmask vm86, also there are some other non-existed syscalls on other platforms, I will put the workarounds together and submit a patch. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: Caspar Z. <cz...@re...> - 2010-12-09 18:36:57
|
Hello list, I tried to use crackerjack to run some regression test on RHEL and Fedora, however, I found there were some bugs stopping me compiling through the testcases, I wrote some workarounds and would like to send these patches to the list soon. Since I found this list is so quiet, please let me know if there still are maintainers or developers in this list. Thanks, Caspar -- Quality Assurance Associate (Kernel) in Red Hat Software (Beijing) Co., R&D Branch TEL: +86-10-62608150 WEB: http://www.redhat.com/ |
|
From: <his...@hi...> - 2010-08-25 05:01:04
|
CrackerJack Members, Long time no e-mail on this mailing list. As I wrote a long time ago, Red Hat and we agreed following 3 things. (1) Red Hat will refer our test site in their migration document. http://ossipedia.ipa.go.jp/crackerjack/index.html (2) Red Hat will release that document with RHEL 6(Next Release) (3) CrackerJack team will clear all bugs remained. I am not sure when RHEL 6 will be released, but It must be in this year. And we will have next forum in Seoul in November. I have checked the latest result. http://ossipedia.ipa.go.jp/crackerjack/index.html The test version is still 3.0 so that following result may not reflect the latest status. The result between RHEL5 and 2.6.35 based on test case V3.0 is Incompatible(no fix) link rename renameat linkat Maybe bugs kill waitid pselect6(Fixed) sysfs(Fixed in 3.1) old_mmap(obsoled:will be removed in 3.2) Could you check the result above(kill and waitid) and start to fix them ? ^^^^^^^^^^^^^ If they are already fixed, please let me know. I will release 3.2 in soon including all fixes. I hope our work almost done and finishing in soon. Regards, Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
|
From: 胡昌军 <hu...@cs...> - 2010-04-06 03:20:40
|
crackerJack Chinese Members,
please fix it about you! Thanks for your best works!
Changjun hu
-----邮件原件-----
发件人: his...@hi... [mailto:his...@hi...]
发送时间: 2010年4月6日 9:58
收件人: his...@hi...
抄送: 胡昌军; ヒホ蓆ヤ・; 王绪刚; cra...@li...
主题: Re[2]: [Crackerjack-devel] crackerjack status
CrackerJack Members,
I would like to let you know about our approaching to Red Hat.
We have visited Red Hat in Boston early March.
We had discussed how Red Hat can use our result of Project.
We agreed on items below.
(1) Red Hat will refer our test site in their migration document.
http://ossipedia.ipa.go.jp/crackerjack/index.html
(2) Red Hat will release that document with RHEL 6(Next Release)
(3) CrackerJack team will clear all bugs remained.
I think this is a greate success of our project.
Thank you for your collaboration!!
We need to fix bugs, I have checked the latest result.
The result between RHEL5 and 2.6.32 is
Incompatible(no fix)
Link (K)
Rename (K)
renameat (K)
linkat (K)
Maybe bugs
Kill (csip)
Waited (csip)
pselect6 (J)
sysfs (K)
old_mmap (J)
Could you check the result above and start to fix them ?
Regards,
Hisashi Hashimoto
Board of Director, the Linux Foundation,
Senior Engineer
Open Source Software Promotion Center
Enterprise Business Planning
Hitachi, Ltd., Software Division
Tel : +81-45-862-8470, Fax : +81-45-862-8471
his...@hi...
|
|
From: <his...@hi...> - 2010-04-06 02:30:19
|
CrackerJack Members, I would like to let you know about our approaching to Red Hat. We have visited Red Hat in Boston early March. We had discussed how Red Hat can use our result of Project. We agreed on items below. (1) Red Hat will refer our test site in their migration document. http://ossipedia.ipa.go.jp/crackerjack/index.html (2) Red Hat will release that document with RHEL 6(Next Release) (3) CrackerJack team will clear all bugs remained. I think this is a greate success of our project. Thank you for your collaboration!! We need to fix bugs, I have checked the latest result. The result between RHEL5 and 2.6.32 is Incompatible(no fix) link rename renameat linkat Maybe bugs kill waitid pselect6 sysfs old_mmap Could you check the result above and start to fix them ? Regards, Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
|
From: <his...@hi...> - 2010-01-21 03:56:29
|
Hi, CrackerJack Developers, I am planning to release 3.2 end of February. I want to include source code of Framework and bug-fixed test cases. Could you let me know your status of fixing ? As for Japan, I have to say that I am straggling heavy bug., sigh,.... Thanks. Hashimoto >Hi : > > > >Xiaoyu and kongHao, Recently ,what process is there about the Crackerjack¨s testcases which you are in charge of developing or fixing ? > >・團、迅蟷・徭crackerjack3.1窟下朔・除栖crackerjack霞編喘箭蝕窟賜bugs俐鹸嗤焚担序婢宅・ > >萩指鹸・謹仍・ > >Hu changjun > > Hisashi Hashimoto Board of Director, the Linux Foundation, Senior Engineer Open Source Software Promotion Center Enterprise Business Planning Hitachi, Ltd., Software Division Tel : +81-45-862-8470, Fax : +81-45-862-8471 his...@hi... |
5 messages has been excluded from this view by a project administrator.
