Project

General

Profile

Actions
Copy link

Bug #4621

closed

failed pjd chown/00.t 124

Added by Sage Weil about 11 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
Urgent
Assignee:
Greg Farnum
Category:
-
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

2013-04-02T09:04:34.029 INFO:teuthology.task.workunit.client.0.out:../pjd-fstest-20090130-RC-open24/tests/chown/00.t (Wstat: 0 Tests: 171 Failed: 1)
2013-04-02T09:04:34.029 INFO:teuthology.task.workunit.client.0.out: Failed test: 124

ubuntu@teuthology:/a/sage-2013-04-02_08:46:45-fs-wip-4619-testing-basic/8534

full logs

Actions
Copy link
 #1

Updated by Ian Colle about 11 years ago

  • Assignee set to Greg Farnum
Actions
Copy link
 #2

Updated by Greg Farnum about 11 years ago

Well, it's always an adventure to figure out which one is busted, but it looks to be an lchown on a symlink failing. Perhaps it's related to #4601?
Unless pjd thinks that lchmod isn't supported, in which case this is just a time check failing; but I don't think we're that lucky.

Actions
Copy link
 #3

Updated by Greg Farnum about 11 years ago

Sorry, not an lchown, just a symlink create.

Actions
Copy link
 #4

Updated by Greg Farnum about 11 years ago

  • Status changed from New to Rejected

Okay, all symlink attempts that made it to the MDS were successes, and I can't find any failed ceph-fuse symlink/ll_symlink calls either. Umm...

Aha! It only ran 171 tests which means it isn't doing the lchmod tests, and that means it did fail on a time comparison. Screw you pjd time consistency and network clocks!

(Made a separate bug #4630 for lchown not being tested under pjd.)

Actions
Copy link

Also available in: Atom PDF